knowledge_graph_skill
"Skill for searching and evolving the SQLite-backed Knowledge Graph.\
pinned to #631aad0updated 3 months ago
Ask your AI client: “install skills/knowledge-graph-skill”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/knowledge-graph-skillmetahub onboarded this repo on the author's behalf.
If you own github.com/NPC-Worldwide/npcpy on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
1,424
Last commit
3 months ago
Latest release
published
- #agents
- #ai
- #llm
- #mcp
- #mcp-client
- #mcp-server
- #ollama
- #perplexity
- #python
- #sql
- #yaml
About this skill
Pulled from SKILL.md at publish time.
Skill for searching and evolving the SQLite-backed Knowledge Graph. Use this when you need structured fact/concept/link search across one or more teams, NPCs, or directory scopes. The Knowledge Graph (KG) is stored in the application's database (not YAML). It is scoped by (teamname, npcname, directorypath). Facts and concepts carry generation numbers and origin tags. Search methods (choose the right one): 1. Keyword search — fast substring match over fact statements. kgsearchfacts(engineor_kg, "keyword") → List[str]
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.631aad0· 3 months ago
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
4 passed1 warningDescription qualitywarn
9 words · 69 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
38,856 chars · 16 sections · 47 code blocks
Tags / topics declared
11 total — agents, ai, llm, mcp, mcp-client, mcp-server (+5)
README has usage / example sections
found: Example · Example · Installation
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent631aad0warn3 months ago
Contents
Skill for searching and evolving the SQLite-backed Knowledge Graph. Use this when you need structured fact/concept/link search across one or more teams, NPCs, or directory scopes. The Knowledge Graph (KG) is stored in the application's database (not YAML). It is scoped by (team_name, npc_name, directory_path). Facts and concepts carry generation numbers and origin tags. Search methods (choose the right one):
-
Keyword search — fast substring match over fact statements.
kg_search_facts(engine_or_kg, "keyword")→ List[str] -
Embedding search — semantic cosine similarity via vector embeddings.
kg_embedding_search(engine_or_kg, query="...", embedding_model="nomic-embed-text", embedding_provider="ollama", similarity_threshold=0.6, max_results=20)→ List[dict] with 'content', 'type', 'score' -
Link search — graph traversal (BFS/DFS) starting from keyword-matched seeds.
kg_link_search(engine_or_kg, query="...", max_depth=2, breadth_per_step=5, strategy="bfs", max_results=20)→ List[dict] with 'content', 'type', 'depth', 'path', 'score' -
Hybrid search — combines keyword + embedding + link, boosting results found by multiple methods.
kg_hybrid_search(engine_or_kg, query="...", mode="all", max_depth=2, similarity_threshold=0.6, max_results=20)→ List[dict] with 'content', 'type', 'score', 'source'
Graph evolution (use sparingly, usually in background): - kg_initial(content, model, provider) — build a new KG from text - kg_evolve_incremental(existing_kg, new_content_text, ...) — add content - kg_sleep_process(existing_kg, model, provider) — prune/deepen/consolidate - kg_dream_process(existing_kg, model, provider, num_seeds) — speculative synthesis
When a user asks a question that spans facts, concepts, and their relationships, prefer hybrid search. For pure semantic similarity without graph structure, use embedding search. For exploring connected neighborhoods, use link search with BFS.
Inputs
name(default:'search_method')description(default:'keyword | embedding | link | hybrid')name(default:'query')description(default:"The user's query or topic to search")name(default:'scope_team')description(default:'Team name to scope the search (optional)')name(default:'scope_npc')description(default:'NPC name to scope the search (optional)')name(default:'scope_directory')description(default:'Directory path to scope the search (optional)')
Steps
instruct→instruct.py
Usage
/run_jinx jinx_ref=knowledge_graph_skill input_values={"name": "scope_directory", "description": "Directory path to scope the search (optional)"}
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/knowledge-graph-skill