Defame1297
229c7a4ab9
Step 5 now records a Research doc: path per entry in references/sources.md, pointing to the upstream plugin-level research file the slug was drawn from. Updates the sources.md template to include the new required field, formalise comma-separated Contributing files, and document the (none) convention. 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.