Skill Claude CodeCodex
A skill for organising an Obsidian vault, a local collection of linked Markdown notes, into a structured knowledge wiki. It uses four stages: scan, ingest, curate, and lint.
Skill Claude CodeCodex
A coordinator for organizing an Obsidian vault, which is a folder of linked Markdown notes, by first checking its structure and then arranging the notes.
Skill Claude CodeCodex
A skill for keeping the structure of an Obsidian knowledge base up to date. It regenerates marked sections such as the home page tree, directory lists, and index pages.
Skill Claude CodeCodex
Use when building or refreshing the RagKit index for a project knowledge-base/ (e.g. after distill added or updated knowledge points). Trigger /ragkit:embed. Querying instead uses ragkit:query; index health uses ragkit:status.
Skill Claude CodeCodex
Use when measuring or tuning RagKit retrieval accuracy — runs the golden evalset, reports recall@k and MRR per bucket. Trigger /ragkit:eval. Run before or after any retrieval-param change to keep a baseline.
Skill Claude CodeCodex
Use when retrieving from a project knowledge-base/ — multi-channel RAG recall (vector plus lexical plus metadata, RRF-fused) returning locate-pointer cards; multi-round and multi-angle querying allowed. Trigger /ragkit:query, or called by name by workflows like specode. Building or refreshing the index instead uses…
Skill Claude CodeCodex
Use when checking RagKit index health — doc and chunk counts, backend resolution, staleness and drift between knowledge-base/ and index. Trigger /ragkit:status. Rebuilding after drift uses ragkit:embed.
Skill Claude CodeCodex
Overview of the ragkit plugin and how to use it — knowledge-base multi-channel retrieval and its four skills. On Kimi Code this is loaded at session start via the manifest's sessionStart.skill; on hosts with a SessionStart hook the same advisory is injected by the hook instead.
Skill Claude CodeCodex
Use when resuming an existing spec by slug — the /specode:continue entry that reads the fixed docs, reports a progress brief (inferred phase + checkbox progress), then stops and waits for the user; it never auto-resumes. Trigger /specode:continue .
Skill Claude CodeCodex
Use when distilling a finished specode spec into atomic, locate-oriented markdown knowledge points — writes cases/ + navigation/ + MEMORY.md into the project's own /knowledge-base/ (md-only, no auto-injection), optionally copied to an Obsidian vault. Trigger ONLY /specode:distill , never auto-run by the main specode…
Skill Claude CodeCodex
Use when running a spec's execution tail — presents the 执行方式 selector, dispatches the chosen engine (task-swarm / superpowers / specode-native TDD), then runs acceptance and the distill prompt. Trigger /specode:execute manually at any time once tasks.md exists, or invoked by name (specode:execute) via the Skill tool…
Skill Claude CodeCodex
Use when running specode's requirements phase — project analysis + code location + clarification, then writing requirements.md. Produces / /requirements.md (with the projectroot frontmatter contract) plus the location pointers handed to the design phase. Invoked by name (specode:intake) via the Skill tool by the…
Skill Claude CodeCodex
Use when listing all specs under the specs root — the /specode:list entry that shows every spec slug with its inferred phase, for looking up slugs or an overview; it does not resume. Trigger /specode:list.
Skill Claude CodeCodex
Use when creating a new spec-driven workflow — the /specode:spec entry that walks requirements → design → tasks → 执行方式 → execute → acceptance, autonomously calling superpowers skills for the heavy lifting with a first-class specode-native fallback, and filing 4 fixed artifacts (requirements.md / design.md / tasks.md /…
Skill Claude CodeCodex
Overview of the specode plugin and how to activate it — the spec-driven workflow, its five commands, and when to enter spec mode. On Kimi Code this is loaded at session start via the manifest's sessionStart.skill; on hosts with a SessionStart hook the same advisory is injected by the hook instead.
Skill Claude CodeCodex
Use when driving the task-swarm multi-agent orchestrator standalone — read a requirement or design doc, generate a pipeline.yml, then run the fork → review → validate loop to finish a multi-task implementation. Trigger /task-swarm:swarm, or when specode delegates its execution phase here; input a requirements doc or a…