mcpbeat

Source Tutorial Spec

willoscar/source-tutorial-spec

| Use when a `source-tutorial` workspace has ingested sources and needs a grounded tutorial contract before structure planning.

728 tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
496
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill source-tutorial-spec

What comes with it

1 315 bytes besides the instruction
scripts/run.py

The instruction itself

7 sections, as written by the author

Source Tutorial Spec

Builds the C2 tutorial contract from the ingested source corpus, not from a bare topic prompt.

Inputs

  • sources/index.jsonl
  • sources/provenance.jsonl
  • GOAL.md
  • DECISIONS.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.md exists
  • 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

How to use it

Copy the folder

Take willoscar/source-tutorial-spec from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.