Source Tutorial Spec Agent Skill
| Use when a `source-tutorial` workspace has ingested sources and needs a grounded tutorial contract before structure planning.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill source-tutorial-specWhat comes with it
1 315 bytes besides the instructionThe instruction itself
7 sections, as written by the authorSource Tutorial Spec
Builds the C2 tutorial contract from the ingested source corpus, not from a bare topic prompt.
Inputs
sources/index.jsonlsources/provenance.jsonlGOAL.mdDECISIONS.md
Output
output/TUTORIAL_SPEC.md
Contract
The spec must include:
## Audience## Prerequisites## Learning objectives## Non-goals## Source scope## Running example policy## Delivery shape
It should also embed machine-readable structured data for downstream deterministic planning.
Script boundary
scripts/run.py should:
- read the ingested source bundle
- derive a grounded tutorial scope
- write the markdown spec and structured seed block
Keep phrase extraction, concept selection, and source matching in shared tutorial tooling, not in the thin skill wrapper.
Acceptance
output/TUTORIAL_SPEC.mdexists- the required sections are present
- source families are named explicitly
- running example policy is concrete or explicitly omitted
Non-goals
- concept DAG construction
- module sequencing
- tutorial prose writing
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take willoscar/source-tutorial-spec from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.