manage-refs

Featured

Cross-cutting reference manager for medical manuscripts. Single entry point for citation-key validation, journal-CSL pandoc rendering, manuscript ↔ DOCX cross-reference QC, marker conversion (``[N]`` ↔ ``[@key]``), and native Zotero CWYW field-code injection. Replaces the inline reference-handling that previously lived in ``/write-paper`` Phase 7.6 and is reused by ``/revise``, ``/peer-review``, ``/sync-submission``, and any skill that produces a journal submission. Audit-only verification stays in ``/verify-refs`` — this skill writes (renders, injects, converts); that skill only reads.

Data & Documents 223 stars 55 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
78
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Manage-Refs Skill > **Canonical source (issue #16).** This SKILL.md is the single canonical > reference for the reference-*workflow* (validate keys → render CSL → convert > markers → QC cross-references → inject Zotero CWYW). Audit-only bib > verification is owned by `skills/verify-refs/SKILL.md`. Any user-scope rule or > external note about reference handling should point here (workflow) or to > verify-refs (audit) rather than restating the "how", to prevent drift. You are routing reference-handling work for a medical manuscript. The user is somewhere in the lifecycle — drafting, building a circulation DOCX, swapping CSL after a journal rejection, fixing a cross-reference defect surfaced by QC, or wiring up live Zotero field codes for a co-author Word workflow. Pick the right tool from the decision table; do not invent a parallel pipeline. ## Why This Skill Exists Reference handling spans every late-stage skill: `/write-paper` builds the first DOCX, `/revise` rebuilds it after each reviewer round, `/peer-review` emits a critique that quotes references back, `/sync-submission` packages the final tarball, `/find-journal` informs CSL swaps on rejection cascade, and `/verify-refs` audits the bibliography. Until 2026-05-01 these scripts lived under `skills/write-paper/scripts/`, which made `/revise` and `/sync-submission` silently depend on a sibling skill — a layering inversion that broke when `/write-paper` was loaded into a non-research project. Moving the lifecycle tool...

Details

Author
Aperivue
Repository
Aperivue/medsci-skills
Created
3 months ago
Last Updated
yesterday
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

paper-skill

End-to-end, Chinese-first academic research and publication workflow for reading papers, literature reviews, research framing, manuscript planning and writing, Chinese-English translation, LaTeX, figures, citation verification, reporting-guideline checks, journal selection, peer review, rebuttals, revisions, and submission packages. Use for SCI, IEEE, Nature-family, IJCAI, TRO, theses, systematic reviews, clinical/observational/animal studies, and any task where claims, evidence, references, manuscript files, or journal requirements must be checked rather than invented.

69 Updated 1 weeks ago
cLin-c
DevOps & Infrastructure Listed

citation-integrity

Verify that a manuscript's references are real, correctly attached, un-retracted, and honestly cited — the pre-submission citation-integrity pass. Use when the user wants citations/references checked, verified, or audited ("check my citations", "verify my references", "are these citations real", "did I cite anything retracted", "integrity pass before I submit"), whether or not they use the render pipeline.

7 Updated 5 days ago
Shalice-in-AIland
Code & Development Listed

docs-dry-refactor

Operationalises spec/project/mkdocs-structure/ §Snippet inclusion (DRY). Detects paragraph duplication across MkDocs pages and, with per-snippet user approval, extracts duplicates into `mkdocs-include-markdown-plugin` includes pointing at a canonical source (preferring a live source file over a dedicated per-language _snippets/ folder). Three operations: `audit` (read-only ranked findings), `propose` (surface canonical source, markers, include directives for a target snippet ID, await approval), `apply` (write markers, replace consumer blocks, verify via `mkdocs build --strict`). Invoke when the user asks to dedupe, DRY-refactor, extract snippets, or factor out duplicated MkDocs content; also handles equivalent German-language requests. Don't use for non-MkDocs markdown trees, single-file snippet authoring, prose linting (`prose-vale-curator`), structural scaffolding (`mkdocs-structure-apply`), or drift detection (`docs-freshness-checker`). Supports resume on re-invocation per `spec/claude/resumable-work/`.

0 Updated today
nolte