Tutorial Context Pack Agent Skill
| Use when module planning and source coverage are done and the run needs writer-ready per-module packs.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill tutorial-context-packWhat comes with it
1 683 bytes besides the instructionThe instruction itself
7 sections, as written by the authorTutorial Context Pack
Combines module structure, source coverage, and source snippets into one deterministic JSONL pack per module.
Inputs
outline/module_plan.ymloutline/source_coverage.jsonlsources/provenance.jsonl
Output
outline/tutorial_context_packs.jsonl
Contract
Each pack must include:
module_idtitleobjectivecore_conceptsexercise_seedsource_snippets
Script boundary
scripts/run.py should:
- read the current module plan and coverage file
- select source snippets per module
- write one stable pack per module
Keep snippet ranking and pack synthesis in shared tutorial tooling rather than in the thin wrapper script.
Acceptance
- one pack per module
- every pack has
module_idandobjective - every pack includes actual source-backed snippets
Non-goals
- final tutorial prose
- PDF/slides delivery
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/tutorial-context-pack 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.