create_jinx
Write a new .jinx file from inputs (name, description, inputs spec as
Skill for using the KnowledgeIndex registry to discover which directories\
$ npx -y skills add NPC-Worldwide/npcpy --skill knowledge_index_skill --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/knowledge_index_skillContext preview
The summary Claude sees to decide when to auto-load this skill.
Skill for using the KnowledgeIndex registry to discover which directories\
name: knowledge_index_skill description: "Skill for using the KnowledgeIndex registry to discover which directories\ \ contain `.knowledge.yaml` files without walking the filesystem.\nKnowledgeIndex\ \ is a lightweight SQLite cache. It maps directory paths to file metadata (mtime,\ \ memory_count, link_count). The database path is caller-provided \u2014 npcpy does\ \ not hardcode a default.\nKey operations: - Upsert a directory after writing to\ \ its YAML:\n `upsert_directory(db_path, directory, memory_count, link_count)`\n\ - List known directories: `get_known_directories(db_path, min_mtime=None)` - Full\ \ rescan of a tree: `scan_root(db_path, root, max_depth=5)` - Remove a stale directory:\ \ `remove_directory(db_path, directory)`\nTypical flow: 1. Call `scan_root(db_path,\ \ root=\"/home/user/projects\", max_depth=5)`\n to populate the index with every\ \ `.knowledge.yaml` found.\n2. Query `get_known_directories(db_path)` to get a list\ \ of directories\n with memory/link counts.\n3. For each directory of interest,\ \ instantiate `KnowledgeStore(directory)`\n and call `load()` or `build_context()`.\n\ \nThe index is a cache, not the source of truth. If a `.knowledge.yaml` is deleted\ \ or modified outside the app, re-run `scan_root` to refresh."
Skill for using the KnowledgeIndex registry to discover which directories contain `.knowledge.yaml` files without walking the filesystem. KnowledgeIndex is a lightweight SQLite cache. It maps directory paths to file metadata (mtime, memory_count, link_count). The database path is caller-provided — npcpy does not hardcode a default. Key operations: - Upsert a directory after writing to its YAML: `upsert_directory(db_path, directory, memory_count, link_count)`
Typical flow: 1. Call `scan_root(db_path, root="/home/user/projects", max_depth=5)` to populate the index with every `.knowledge.yaml` found. 2. Query `get_known_directories(db_path)` to get a list of directories with memory/link counts. 3. For each directory of interest, instantiate `KnowledgeStore(directory)` and call `load()` or `build_context()`.
The index is a cache, not the source of truth. If a `.knowledge.yaml` is deleted or modified outside the app, re-run `scan_root` to refresh.
/run_jinx jinx_ref=knowledge_index_skill input_values={"name": "root_or_directory", "description": "Root to scan or specific directory to upsert/remove"}npcpy is a library that provides key primitives for research and development with multimodal language models, agentic AI, and knowledge graphs.
Write a new .jinx file from inputs (name, description, inputs spec as
Skill for searching and evolving the SQLite-backed Knowledge Graph.\
Skill for population-based Knowledge Graph evolution via Sememolution.\
Skill for working with local .knowledge.yaml files via KnowledgeStore.\
Render the provided prompt template with Jinja context and send it to
Execute a jinx by name (already loaded on the team) or by filesystem