source-citations

To build a centralized citation registry for instrument sources, this skill extracts stable source keys from a master library and validates them against curated per-repo references. It ensures provenance attribution remains accurate by enforcing registry validation during generation.

Generating SOURCES.md and TECHNIQUES.md from curated citations involves mapping validated registry keys to per-repo reference files. The skill automates this by reading YAML frontmatter and manifest data to produce structured provenance documentation.

Registry validation prevents fake instrument citations by enforcing that every cited source key exists within the centralized master library. It also checks that each citation's rationale is present before allowing per-repo reference generation to proceed.

Yes, you can use YAML frontmatter to support cross-runtime deployment for instrument repos. The skill implements CLI tooling and frontmatter requirements designed to integrate citation manifests with per-repo pipelines across different runtimes.

Auditing provenance across multiple files in a repository is best handled by maintaining a centralized citation registry alongside per-repo SOURCES.md and TECHNIQUES.md files. This structured approach enforces consistent attribution tracking and prevents unregistered sources.

Instrument repo validation fails when generating SOURCES.md if cited source keys do not exist in the centralized registry or if the rationale for a citation is missing. The governance mechanism requires both conditions to pass successfully.