mcpbeat

Module Planner

willoscar/module-planner

| Use when a tutorial concept DAG exists and the run needs an ordered teaching plan with objectives and outputs.

749 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 module-planner

What comes with it

1 629 bytes besides the instruction
scripts/run.py

The instruction itself

7 sections, as written by the author

Module Planner

Turns the concept graph into the teachable module sequence used by later tutorial stages.

Input

  • outline/concept_graph.yml

Output

  • outline/module_plan.yml

Contract

The module plan must define:

  • ordered modules
  • id, title
  • objectives
  • concepts
  • outputs
  • running_example_steps

Script boundary

scripts/run.py should:

  • topologically order concepts
  • cluster them into coherent modules
  • attach measurable objectives and concrete outputs

Keep graph traversal and clustering heuristics in shared tutorial tooling, not in the wrapper script.

Acceptance

  • outline/module_plan.yml exists
  • every concept node is covered by at least one module
  • every module has objectives and outputs

Non-goals

  • source grounding audit
  • exercise writing
  • tutorial drafting

How to use it

Copy the folder

Take willoscar/module-planner 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.