mcpbeat

Curate

athola/curate

Adds developer-authored annotations to the gauntlet knowledge base. Use when capturing tribal knowledge or rationale not visible in code.

314 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
324
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/athola/claude-night-market --skill curate

The instruction itself

4 sections, as written by the author

Curate Knowledge

Add developer-authored annotations to the knowledge base.

When NOT To Use

  • Knowledge derivable from the code itself (use gauntlet:extract)
  • The DSA problem bank (use gauntlet:gauntlet-curate)

Steps

  • Identify the module to annotate
  • Ask for the concept (key insight or rule)
  • Ask for the why (rationale, history, context)
  • Generate YAML annotation file
  • Save to .gauntlet/annotations/<slug>.yaml
  • 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 concept field (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)

How to use it

Copy the folder

Take athola/curate from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.