← ClaudeAtlas

_template_reference_firstlisted

Internal template for creating or refactoring a skill into the repository's reference-first shape. **Trigger**: reference-first template, blueprint skill, create a reusable skill, refactor a script-heavy skill. **Use when**: you need a lean `SKILL.md`, explicit `references/`, machine-readable `assets/`, and a minimal deterministic `run.py`.
WILLOSCAR/research-units-pipeline-skills · ★ 510 · Data & Documents · score 81
Install: claude install-skill WILLOSCAR/research-units-pipeline-skills
# Reference-First Skill Template ## Why this exists This package is the default starting point for new or refactored skills in this repo. It demonstrates the intended split of responsibilities: - `SKILL.md` routes the workflow - `references/` holds method, judgment, and exemplars - `assets/` holds machine-readable contracts - `scripts/` handles deterministic execution only Use it as a shape to copy and customize, not as a domain-specific skill. ## Inputs - the job the skill should encode - the expected inputs and outputs for that job - acceptance criteria and failure conditions - any domain packs, schemas, or existing artifacts that must be reused ## Outputs - a lean `SKILL.md` - `references/overview.md` - `references/examples_good.md` - `references/examples_bad.md` - `assets/schema.json` - `scripts/run.py` ## Workflow 1. Define the job and its boundary - write down the trigger, intended outcome, and explicit non-goals - separate reusable behavior from one-off project context 2. Write `SKILL.md` as a router - keep only the activation rule, inputs, outputs, workflow, block conditions, and resource routing - do not copy large judgment rules, domain essays, or sentence banks into this file 3. Move reusable thinking into `references/` - put domain knowledge, decision rubrics, and method notes in `references/overview.md` - if the skill can emit reader-facing text, include both `references/examples_good.md` and `references/examples_bad.md` - keep reference files one hop