mcpbeat

Concept Graph

willoscar/concept-graph

| Use when an approved tutorial spec exists and the run needs a deterministic prerequisite graph before module planning.

669 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 concept-graph

What comes with it

1 359 bytes besides the instruction
scripts/run.py

The instruction itself

7 sections, as written by the author

Concept Graph

Materializes the tutorial spec's structured concept inventory into outline/concept_graph.yml.

Input

  • output/TUTORIAL_SPEC.md

Output

  • outline/concept_graph.yml

Contract

The graph must contain:

  • nodes: {id, title, summary, source_ids, objective_refs}
  • edges: {from, to} meaning prerequisite order

Script boundary

scripts/run.py should:

  • load structured spec data
  • emit stable node ids and prerequisite edges
  • fail if the result would be cyclic or empty

Do not duplicate spec-parsing heuristics in multiple places; keep them in shared tutorial tooling.

Acceptance

  • outline/concept_graph.yml exists
  • all nodes have stable ids
  • the graph is a DAG

Non-goals

  • module clustering
  • exercise generation
  • tutorial prose

How to use it

Copy the folder

Take willoscar/concept-graph 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.