_template_reference_first

Solid

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`.

Data & Documents 498 stars 39 forks Updated today

Install

View on GitHub

Quality Score: 81/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
0
Description 5%
100

Skill Content

# 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...

Details

Author
WILLOSCAR
Repository
WILLOSCAR/research-units-pipeline-skills
Created
7 months ago
Last Updated
today
Language
Python
License
None

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

skill-authoring

Methodology for authoring scaffolding-compatible skills: frontmatter contract, body structure, validation. TRIGGER when: running /create-skill, writing or reviewing a SKILL.md file, or deciding if a procedure deserves its own skill. SKIP: distilling a conversation into candidates (use distill); 3-tier memory writes (use agent-memory).

15 Updated 2 weeks ago
komluk
API & Backend Listed

skill-authoring-patterns

The Apple/Swift-and-this-catalog layer for authoring or reviewing a SKILL.md, on top of superpowers:writing-skills. Use when writing or CR-ing a skill for this repo, wording a description so it routes precisely, splitting a skill into references/, or choosing granularity and naming. Adds: precision-router descriptions with framework API names, the Common-Mistakes + Review-Checklist bookends, two-tier references/, the Rationale/Deviation convention, evidence-based multi-reviewer CR. Does NOT cover general skill discipline (TDD-for-skills, when-not-to-create, token budgets) → superpowers:writing-skills.

0 Updated 2 weeks ago
wei18
Code & Development Solid

skill-creator

Use when creating a new skill from scratch, modifying an existing skill, or optimizing a skill's triggering description. Guides intent capture, structure, writing patterns, and progressive-disclosure organization so skills reliably trigger and stay maintainable. Trigger on phrases like "turn this into a skill", "write a skill for X", "improve this skill", "my skill isn't triggering".

47 Updated yesterday
Kanevry