Manuscript collab
CriticMarkup collaboration for research Markdown: teach agents to attribute comments (@Claude/@Cursor/@Codex/@ChatGPT), address human review comments, and export Word for coauthors after snapshotting and stripping agent notes. Day-to-day router for comment/address/share Word (does not replace manuscript-markdown for convert-only / Zotero-field / install jobs). Use when the user says "/manuscript-collab", asks to leave agent comments, address CriticMarkup review feedback, or share DOCX without Claude/Cursor comments. Convert engine is upstream manuscript-markdown CLI (required for export); extension optional. Does not draft scientific prose (use manuscript-writing).From its SKILL.md
npx -y skills add dahliasan/researchskills --skill manuscript-collabAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.7 KB, as published. Nobody here has run it
/manuscript-collab — CriticMarkup collab router
Router for comment / address / export. Storage is CriticMarkup in the .md
file (not Markdown Collab <!--mc:-->). DOCX conversion stays in
manuscript-markdown + upstream CLI.
Day-to-day: use this skill for coauthor notes and share packs. You still need
the Manuscript Markdown CLI installed; invoke /manuscript-markdown for
import, install/doctor, live Zotero field wiring, or pandoc compare.
Details: reference.md
Step 0 — Detect mode
| Signal | Mode |
|---|---|
“leave a note”, “review this md”, /manuscript-collab review | comment / review |
| “address comments”, “fix review feedback” | address |
“export for coauthors”, “share Word without agent comments”, /manuscript-collab export | export |
| “install CLI” / doctor for share-export | export install gate |
Mode: comment / review
Agents must attribute CriticMarkup comments with an allowlisted name:
{>>@Claude | note<<}
{>>@Cursor | note<<}
{>>@Codex | note<<}
{>>@ChatGPT | note<<}
Prefer @Name. Optional timestamp: {>>@Claude (2026-07-21 14:00) | note<<}.
Review Mode: open agent comments on passages; do not edit prose unless asked.
Never-visible agent-only notes may use HTML <!-- … --> (invisible in Word).
Mode: address
- Find CriticMarkup
{>>…<<}whose author is not on the agent allowlist (human comments such as@Ada Lee). - Edit surrounding prose as requested.
- Append a reply:
{>>@Claude | …<<}(or your acting agent name) after the human comment. Do not delete or edit the human comment body. Do not claim the thread is resolved (humans resolve).
Mode: export
Requires manuscript-markdown on PATH. Extension is optional.
From the researchskills repo root (or with absolute script paths):
bash skills/manuscript-collab/scripts/export_for_collaborators.sh \
path/to/paper.md path/to/share.docx --force
Optional: --archive-dir DIR, --ensure-cli (download official binary to ~/bin).
Pipeline:
- Snapshot full
.md(agent comments kept) → archive - Strip agent comments (+ paired
{==…==}wrappers → bare text) manuscript-markdown→ DOCX
Live Zotero cites + human comments: cites inside {++} / {--} stay
literal [@citekey] in Word. If the user wants live Zotero fields, accept
additions and drop deletions on an export-only copy (keep {>>} / {==});
do not rewrite the track-change source MD unless asked. Details:
skills/manuscript-markdown/references/zotero-fields.md.
Do not fall back to pandoc. If CLI missing, stop and point to
skills/manuscript-markdown/references/install.md or --ensure-cli.
Composes with
manuscript-markdown— raw MD↔DOCX / install doctor / Zotero fieldsmanuscript-writing— prose draft/revise (not this skill)zotero— library sync for citekeys / bib enrichment before export