SkillsAdd

smithery/willoscar

citation-anchoring

Regression-check citation anchoring (citations stay in the same subsection) to prevent “polish drift” that breaks claim→evidence alignment.

Installation

$ npx skills add smithery/willoscar --skill citation-anchoring
View on skills.sh ↗ Website ↗

Also in this package

Other skills from smithery/willoscar · top by installs.

npx skills add smithery/willoscar
writer-selfloop 0 writer-context-pack 0 workspace-init 0 unit-planner 0 unit-executor 0 transition-weaver 0 terminology-normalizer 0 taxonomy-builder 0 table-schema 0 table-filler 0

Browse all from smithery/willoscar

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,154 B
  • docs SUMMARY.md 519 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Citation Anchoring (regression)

Triggers & routing

  • Trigger: citation anchoring, citation drift, regression, cite stability, 引用锚定, 引用漂移.
  • Use when: after editing/polishing, you want to confirm citations did not migrate across ### subsections.

Purpose: prevent a common failure mode: polishing rewrites text and accidentally moves citation markers into a different ### subsection, breaking claim→evidence alignment.

Inputs

  • output/DRAFT.md
  • output/citation_anchors.prepolish.jsonl (baseline; created by draft-polisher on first run)

Outputs

  • output/CITATIONANCHORINGREPORT.md (PASS/FAIL + drift examples)

Baseline policy

  • draft-polisher captures a baseline once per run: output/citation_anchors.prepolish.jsonl.
  • Subsequent polish runs should keep per-H3 citation sets stable.

Workflow (analysis-only)

Role:

  • Auditor: only checks and reports; does not edit.

Steps:

  1. Load the baseline anchors.
  2. Parse the current output/DRAFT.md into ### subsections and extract citation keys per subsection.
  3. Compare current sets to baseline sets:
  • keys added/removed within a subsection
  • keys that migrated across subsections
  1. Write output/CITATIONANCHORINGREPORT.md:
  • - Status: PASS only if no drift is detected
  • otherwise, - Status: FAIL with a short diff table + examples

Notes

If you intentionally restructure across subsections:

  • delete output/citation_anchors.prepolish.jsonl and regenerate a new baseline (then treat that as the new regression anchor).

Troubleshooting

Issue: baseline anchor file is missing

Fix:

  • Run draft-polisher once to generate output/citation_anchors.prepolish.jsonl, then rerun the anchoring check.

Issue: citations intentionally moved across subsections

Fix:

  • Delete output/citation_anchors.prepolish.jsonl and regenerate a new baseline (then treat that as the new regression anchor).