knowledge-curation
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.
npx skills add a5c-ai/babysitter --skill knowledge-curation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- After completing work, BEFORE PR creation (reflect mode) - When recovering from context loss (recovery priming) ## Knowledge Categories | Category | File | Content | |----------|------|---------| | Critical Rules | facts.jsonl | MUST FOLLOW constraints | | Gotchas | gotchas.jsonl | Common pitfalls | | Patterns | patterns.jsonl | Codebase best practices | | Decisions | decisions.jsonl | Architectural choices with rationale | | Anti-Patterns | anti-patterns.jsonl | What NOT to do | | Codebase Facts | codebase-facts.jsonl | Structural information | | API Behaviors | api-behaviors.jsonl | Undocumented quirks | ## Process ### Prime Mode 1. Load knowledge base files for work type 2. Surface MUST FOLLOW rules first 3. Present GOTCHAS and PATTERNS 4. Load relevant DECISIONS ### Reflect Mode 1. Extract patterns from completed work 2. Identify gotchas from review failures 3. Record architectural decisions with rationale 4. Persist to .beads/knowledge/ ## Tool Use Invoke via babysitter process: `methodologies/metaswarm/metaswarm-knowledge-cycle`
- Knowledge Categories
- Process
- Prime Mode
- Reflect Mode
- Tool Use
What does the knowledge-curation skill do?
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill knowledge-curation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.