Defame1297
ca73a63c72
Adds a sources provenance step to the skill creation workflow so the chain from research output to skill content is traceable. Closes #4. - New scaffold template `assets/templates/references/sources.md` mirroring the research skill's sources.md format (slug → URL, description, contributing files, status) - `source_keys` commented-out optional field added to the SKILL.md template, mirroring how research topic files link back to sources - New Step 5 in the creation workflow: populate references/sources.md from research input (attributing contributing skill files) or delete it if no research was provided; add source_keys to SKILL.md and any references/*.md files Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
references/
Additional documentation agents load on demand. Files here extend SKILL.md without bloating its core context.
When to add a reference file
Move content here when SKILL.md is approaching 500 lines, or when a topic is only relevant in specific circumstances (error handling, edge cases, domain-specific sub-procedures).
How to reference from SKILL.md
Load conditionally — tell the agent exactly when to read each file:
If the API returns a non-200 status, read `references/api-errors.md`.
Avoid generic "see references/ for details" — the agent loads context on demand, so give it a precise trigger condition.
File conventions
- One topic per file — focused files mean less unnecessary context loaded
- Kebab-case filenames (e.g.
api-errors.md,output-formats.md) - Keep files under 200 lines where possible
If no reference files are needed
Delete this README and the references/ directory entirely.