mcpbeat

Module Source Coverage

willoscar/module-source-coverage

| Use when a tutorial module plan exists and the run needs an auditable module-to-source grounding file before prose.

698 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-source-coverage

What comes with it

1 445 bytes besides the instruction
scripts/run.py

The instruction itself

7 sections, as written by the author

Module Source Coverage

Builds outline/source_coverage.jsonl, one coverage record per module.

Inputs

  • outline/module_plan.yml
  • sources/index.jsonl
  • sources/provenance.jsonl

Output

  • outline/source_coverage.jsonl

Contract

Each record must include:

  • module_id
  • module_title
  • source_ids and/or explicit gaps

Script boundary

scripts/run.py should:

  • score module-to-source relevance
  • choose a small source set per module
  • record explicit grounding gaps when coverage is weak

Keep text matching and snippet scoring in shared tutorial tooling, not in the wrapper.

Acceptance

  • outline/source_coverage.jsonl exists
  • every module appears exactly once
  • missing grounding is explicit instead of silent

Non-goals

  • context pack assembly
  • tutorial prose

How to use it

Copy the folder

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