Skip to content
Skills Library
AI & agents · Building & coding

knowledge-graph-memory

/knowledge-graph-memory

Store facts as entities and relationships when questions depend on connections rather than similarity. Use when retrieval must answer who relates to what rather than find similar text.

Repository
AI-SKILLS ↗
Licence
MIT
Last repository change
05.09.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 05.09.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Store facts as entities and relationships when questions depend on connections rather than similarity. Use when retrieval must answer who relates to what rather than find similar text.

Original author description

Store facts as entities and relationships when questions depend on connections rather than similarity. Use when retrieval must answer who relates to what rather than find similar text.

How it works

  1. Method
  2. Boundaries
Original SKILL.md headings · 38 lines, 252 words
SKILL.md preview
---
name: knowledge-graph-memory
description: Store facts as entities and relationships when questions depend on connections rather than similarity. Use when retrieval must answer who relates to what rather than find similar text.
---

# Knowledge graph memory

Vector retrieval finds text that resembles the query. Some questions are
not about resemblance at all: who reports to whom, which service depends
on which, what changed between these two things. Those are graph
questions, and similarity search answers them badly.

## Method

1. **Use a graph when relationships are the query.** Traversal,
   dependency, and connection questions belong here; similarity and
   passage retrieval do not.
2. **Define the entity and relationship types deliberately.** A schema
   with a handful of clear types is queryable; an open extraction
   producing hundreds of relation names is not.
3. **Resolve entities carefully.** The same person or service named
   three ways becomes three nodes, and entity resolution is where graph
   quality is won or lost (see deduplication-queries).
4. **Keep provenance on every edge.** Which document asserted this
   relationship and when, since graphs built by extraction contain
   errors that must be traceable.
5. **Combine graph with text retrieval.** Traverse to find the relevant
   entities, then retrieve their supporting passages for the model to
   read (see hybrid-search).
6. **Update relationships as sources change.** A stale edge is more
   misleading than stale prose because it reads as structured fact (see
   rag-freshness).
7. **Bound traversal depth.** Deep queries return large subgraphs that
   exceed context and rarely improve the answer.

## Boundaries

Graphs cost extraction and maintenance that a text index does not, and
automated extraction is error-prone. They answer structural questions
and are poor at nuance that lives in prose. A small corpus rarely
justifies the construction effort.

Versions

The database has no other skills named knowledge-graph-memory.

Database snapshot: 13.11.2026 · package version 47b29d01cba7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cortex-navigate-knowledge
    Navigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what…
  • 100knowledge-graph-creation
    Build structured knowledge graphs from unstructured text by extracting entities, mapping relationships, generating graph triples, and visualizing the result. Use when the user requests knowledge graph creation or provides relevant inputs for this workflow.
  • 100knowledge-graph-enhanced-rag-graphrag
    Use this skill when extracting entities and relationships to build structured knowledge graphs that augment semantic RAG retrieval.
  • 100remember
    Write-side memory: stores decisions, patterns, and outcomes in the MCP memory knowledge graph as entities with typed observations and relations. Use when something worth persisting across sessions was just learned or decided. To search or read existing memory, invoke memory; to…
  • 90graph-traversal
    Walk the gutt knowledge graph's relationships to answer what a summary can't — how things connect, what depends on or blocks what, and whether a fact still holds. The deep rung of memory search (rung 3): it runs after a first pass has surfaced the relevant entities, never as the…
  • 95ori-memory
    Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.