Source Adaptation
Use this when turning an upstream prompt, workflow, rubric, benchmark, guide, or docs set into a reusable skill.
Goal
Preserve the source's useful intent while rewriting the runtime shape for this repository, the Agent Skills format, and the selected execution shape.
Adaptation Checklist
Use the rows that affect runtime behavior, maintenance, or legal/attribution handling. Do not fill every row mechanically for trivial sources.
| Decision | Record |
|---|---|
| source intent | what behavior the source is trying to cause |
| local target | what the generated skill should cause in this repo or agent environment |
| fidelity boundary | what must stay equivalent to the source |
| local replacement | what should be rewritten to match local conventions |
| omitted material | what was not carried forward and why |
| provenance | source URL/path, version or commit when available, trust tier, confidence, and usage constraints |
| rights and attribution | license, notice, attribution, or excerpt limits that affect bundled files |
Rewrite Rules
- Do not copy the source's section structure unless that structure improves runtime behavior.
- Convert narrative instructions into decisions, checklists, examples, or output contracts.
- Replace source-specific tool names, paths, severity labels, or provider assumptions with local equivalents unless fidelity requires them.
- Keep provenance, rights notes, source versions, and fidelity tradeoffs in
SOURCES.md. - Keep only instructions that help the agent decide, do, or verify the task at runtime.
- If preserving benchmark or comparison behavior, state the invariant criteria and avoid tuning to expected answers.
Precision Check
Before authoring, answer:
- Which existing local rule should replace a source rule?
- Which source rule is too broad, stale, provider-specific, or non-runtime?
- Which added instruction prevents a concrete mistake that existing guidance does not cover?
- Which source detail belongs in
SOURCES.md,SPEC.md, or a focused reference instead ofSKILL.md?
If these answers are weak, tighten an existing file instead of adding new guidance.