Module Source Coverage

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass, no license.

.claude/skills

Audit 0.4.1 · source sha 81994516a430 · 14 Oct 2026Report an issue or request a re-scan

• PublisherWILLOSCAR GitHub userOwner of the repository this skill is read from
• Source folderWILLOSCAR/research-units-pipeline-skills/.codex/skills/module-source-coverageThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict81994516a430A new audit runs when the source changes
• Repository statusNot archivedLast push 9 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

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

---
name: module-source-coverage
description: "Use when a tutorial module plan exists and the run needs an auditable module-to-source grounding file before prose."
---

# Module Source Coverage

## Triggers & routing

- **Trigger**: module coverage, source coverage, tutorial grounding, 模块覆盖, 来源覆盖.
- **Use when**: `source-tutorial` 的 C2,已有 `outline/module_plan.yml`,需要确认每个模块都能回指到 sources。
- **Skip if**: module plan 或 source ingest 不完整。
- **Network**: none.
- **Guardrail**: 只做 grounding audit,不写教程正文。


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 module record must include:
- `module_id`
- `module_title`
- `source_ids` and/or explicit `gaps`

Plus exactly one corpus-reconciliation record (`record_type: corpus_reconciliation`,
no `module_id`) listing `ingested_source_ids`, `attributed_source_ids`, and
`unused_source_ids`, with an explicit `gaps` entry whenever a source was ingested
but used by no module. A per-module audit alone cannot surface a source that
contributed to zero modules, so this record keeps an unused source explicit
instead of silently dropped.

## 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
- append the corpus-reconciliation record so unused ingested sources are flagged

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
- exactly one `corpus_reconciliation` record accounts for every ingested source
- missing grounding is explicit instead of silent

## Non-goals

- context pack assembly
- tutorial prose

Excerpt, first 1,880 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/WILLOSCAR/research-units-pipeline-skills
git -C research-units-pipeline-skills checkout 81994516a430

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 81994516a430

Questions about Module Source Coverage

• github.com/WILLOSCAR/research-units-pipeline-skills/tree/main/.c — the audited source at commit 81994516a430 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology