template-manuscript-cross-references
Audit or author registry-driven manuscript cross-refs — labels.yaml, [[FIG:]], [[THMREF:]], [[VAR:]] tokens. USE WHEN fixing figure/equation/theorem numbering, orphan registry keys, hard-coded "Theorem 7.3" in prose, or [[MISSING:]] injection failures — even for Pandoc projects that also use a YAML registry.
Best use case
template-manuscript-cross-references is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Audit or author registry-driven manuscript cross-refs — labels.yaml, [[FIG:]], [[THMREF:]], [[VAR:]] tokens. USE WHEN fixing figure/equation/theorem numbering, orphan registry keys, hard-coded "Theorem 7.3" in prose, or [[MISSING:]] injection failures — even for Pandoc projects that also use a YAML registry.
Teams using template-manuscript-cross-references should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/manuscript-cross-references/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How template-manuscript-cross-references Compares
| Feature / Agent | template-manuscript-cross-references | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Audit or author registry-driven manuscript cross-refs — labels.yaml, [[FIG:]], [[THMREF:]], [[VAR:]] tokens. USE WHEN fixing figure/equation/theorem numbering, orphan registry keys, hard-coded "Theorem 7.3" in prose, or [[MISSING:]] injection failures — even for Pandoc projects that also use a YAML registry.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Manuscript cross-references (registry tokens) For Pandoc-crossref `@fig:` / `[@key]` exemplars, see [`docs/guides/manuscript-semantics.md`](../../guides/manuscript-semantics.md). This skill is for **YAML registry + inline tokens**. ## Natural invoke - "Audit [[FIG:]] tokens in actinf_policy_entanglement_lean manuscript" - "Hard-coded section numbers in prose — tokenize them" - "labels.yaml has orphan keys" ## Inputs to confirm - **Scope** — `projects/<name>/manuscript/` path or project name. - **Style** — confirm registry/token vs pure Pandoc-crossref (do not mix styles in repairs). ## Workflow 1. **Registry truth** — `refs/labels.yaml` (figures, equations, sections, theorems) and `refs/citations.yaml` or hybrid `references.bib`. Every token label must exist; every `[@citekey]` must resolve. 2. **No hard-coded numbers** — prefer `[[THMREF:…]]`, `[[SECREF:…]]`, `[[FIGREF:…]]`, `[[EQREF:…]]` over "Theorem 7.3", "§8", "Figure 2" in body prose. 3. **Captions** — YAML-stored captions may not expand `[[…]]` unless renderer documents second pass. 4. **Sync** — subsection headings and `labels.yaml` section/theorem numbers aligned; grep for stale numbers after renumbering. 5. **Bibliography** — if `99_*` uses `[[CITELIST:all]]`, do not hand-maintain a parallel list. 6. **Report** — missing/orphan/duplicate keys; hard-coded numbers to tokenize; concrete edits (file + snippet). ## Verification commands ```bash uv run python -m infrastructure.validation.cli markdown projects/<name>/manuscript/ # Project-local validator when present: uv run python scripts/validate_manuscript.py ``` ## When NOT to use - **Full manuscript scaffold** → [manuscript-creation](../manuscript-creation/SKILL.md) - **Triple-check every factual claim** → [manuscript-claim-verification](../manuscript-claim-verification/SKILL.md) ## References - [`docs/rules/manuscript_style.md`](../../rules/manuscript_style.md) - Project-local `manuscript/refs/README.md` when present