Curate
Capture tribal knowledge—why a module works the way it does—and save YAML annotations into the gauntlet knowledge base for future agent challenges.
Overview
Curate is an agent skill most often used in Build → docs (also Validate → scope, Operate → iterate) that adds developer-authored YAML annotations to the gauntlet knowledge base for tribal knowledge code cannot show.
Install
npx skills add https://github.com/athola/claude-night-market --skill curateWhat is this skill?
- Six-step flow: pick module, concept, why, generate YAML, save under `.gauntlet/annotations/<slug>.yaml`, confirm inclusi
- Explicit focus on tribal knowledge and historical rationale invisible to static analysis
- Structured YAML annotation format for gauntlet knowledge base merges
- Interactive prompts for concept and why before file generation
- Complements code review by documenting intent, not behavior alone
- Six documented steps from module pick through confirm saved for future challenges
Adoption & trust: 1 installs on skills.sh; 304 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
Critical module rationale lives only in people’s heads, so agents and future you misread code and repeat wrong fixes during gauntlet challenges.
Who is it for?
Indie builders extending night-market gauntlet workflows who need fast, structured capture of non-obvious module rules.
Skip if: Bulk API reference generation, auto-mining secrets from git history, or repos without a `.gauntlet/annotations` convention.
When should I use this skill?
Use when capturing tribal knowledge or rationale not visible in code.
What do I get? / Deliverables
A saved `.gauntlet/annotations/<slug>.yaml` file encodes concept and why so upcoming challenges retrieve the annotation automatically.
- `.gauntlet/annotations/<slug>.yaml` with concept and why fields
- Confirmation that the annotation will load in future challenges
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build → docs is the canonical shelf because you author annotations while the system is taking shape, before launch distribution needs dominate. Docs subphase fits developer-authored rationale that is not inferable from code alone and feeds `.gauntlet/annotations` for later retrieval.
Where it fits
After shipping a quirky auth module, curate saves why refresh tokens bypass cache so agents stop ‘fixing’ it.
During scope freeze, annotate boundary modules so prototype agents do not expand into deprecated packages.
Post-incident, record the real root-cause policy in YAML so the next gauntlet challenge enforces the workaround.
How it compares
Use instead of freeform markdown notes when gauntlet expects YAML annotations with slug paths for challenge-time retrieval.
Common Questions / FAQ
Who is curate for?
Solo developers using Claude Night Market gauntlet who want to encode why modules behave a certain way, not only what the code does.
When should I use curate?
During build documentation sprints, validate scoping when module boundaries are fuzzy, or operate iterate passes after incidents—whenever tribal knowledge should persist for the next agent challenge.
Is curate safe to install?
It writes YAML under `.gauntlet/annotations/`; review the Security Audits panel on this Prism page and avoid storing credentials or customer data in annotation rationale.
SKILL.md
READMESKILL.md - Curate
# Curate Knowledge Add developer-authored annotations to the knowledge base. ## Steps 1. Identify the module to annotate 2. Ask for the concept (key insight or rule) 3. Ask for the why (rationale, history, context) 4. Generate YAML annotation file 5. Save to `.gauntlet/annotations/<slug>.yaml` 6. Confirm saved and will be included in future challenges