knowledge-base

Installation
SKILL.md

Codex compatibility note:

  • Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. When a workflow step or another skill names a skill, read that file in full yourself (every line, with no line limit; in parts only when output is cut off): a skill whose implicit invocation is off is never loaded for you. Author .claude/**; mirrors are generated.
  • Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
  • Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
  • Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
  • Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.

Quick Summary

Goal: Keep a project's subject knowledge in small packs the assistant is pointed at exactly when a prompt, a starting skill or a starting helper agent needs them — and let a team add, change, import and ask about that knowledge without writing code, never writing anything the person has not confirmed.

Workflow:

  1. Resolve the mode from the request: list, add, update, delete, review, ask, import or check (see Modes).
  2. Draft — for every write, build the pack or change as a file under tmp/knowledge-base/drafts/.
  3. Enhance — run $prompt-enhance --op=enhance on the draft as an agent guide (its agent-guide branch), passing the preservation contract in references/pack-format.md → Concise, agent-readable writing. Then run the CLI WITHOUT --apply: it validates and writes nothing.
  4. Confirm — show the person the enhanced draft, its size before → after, and every finding, and ask with the host question tool. No answer, no write.
  5. Apply — rerun with --apply only after an explicit yes. The CLI saves the pack and regenerates the project index and reader list in one operation (the framework plane changes only through build).
  6. Report — what changed, where, and any warning left.
Installs
2
GitHub Stars
3
First Seen
13 days ago