
Curate
- 74 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
Curate is an agent skill that adds developer-authored YAML annotations to the gauntlet knowledge base for tribal knowledge code cannot show.
About
Curate is an agent skill from Claude Night Market for solo builders maintaining a gauntlet-style knowledge base around a complex module tree. When code cannot explain why a rule exists—org history, failure modes, or ‘never touch this’ boundaries—you run curate to interview the author (or yourself), distill a concept plus rationale, and emit a YAML annotation file under `.gauntlet/annotations/<slug>.yaml` that future agent challenges automatically include. It is lightweight documentation workflow, not a linter: you still need a real module target and honest context. Use during active build when onboarding your future self, before handoff, or when friction-detector surfaces repeated mistakes that need a human ‘why’ on record. Skip when the answer already lives in README or ADRs and duplicating would confuse retrieval. Standard model hint keeps cost predictable for many small annotations across a growing agent repo.
- 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
Curate by the numbers
- 74 all-time installs (skills.sh)
- Ranked #711 of 1,879 Documentation skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill curateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 74 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Capture tribal knowledge—why a module works the way it does—and save YAML annotations into the gauntlet knowledge base for future agent challenges.
Who is it for?
Best when you're extending night-market gauntlet workflows and 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 you get
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
By the numbers
- Six documented steps from module pick through confirm saved for future challenges
Files
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
Exit Criteria
- [ ] A YAML file exists at
.gauntlet/annotations/<slug>.yaml
after the skill completes, where <slug> is derived from the annotated module and concept
- [ ] The YAML file contains at minimum a
conceptfield (key
insight or rule) and a why field (rationale/history/context)
- [ ] Confirmation message states the annotation will be included
in future challenges, indicating it is on the discovery path for gauntlet:extract
- [ ] Annotation does not duplicate an existing entry under the
same slug (checked before saving)
Related skills
How it compares
Use instead of freeform markdown notes when gauntlet expects YAML annotations with slug paths for challenge-time retrieval.
FAQ
Who is curate for?
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.