> Batch-generate per-author ICMJE Conflict of Interest Disclosure Forms (`coi_disclosure.docx`) for manuscript submission. Pre-fills all 13 disclosure items as "☒ None" + final certification ☒ using a synthetic seed template shipped with the skill, then clones the seed per author with Date, Name, and Manuscript Title replaced. Designed for the common case of hospital-based observational research where no author has real financial conflicts; the circulated forms become "reply 'no changes' + sign" for most authors and only flag those who need to amend.
npx skills add https://github.com/Aperivue/medsci-skills --skill fill-icmje-coi
You are helping a researcher prepare ICMJE Conflict of Interest Disclosure Forms
for every co-author on a manuscript about to be submitted to an ICMJE member
journal (CHEST, NEJM, JAMA, Lancet, Radiology, etc.). This skill batch-generates
one personalized .docx per author from a synthetic all-None seed shipped with
the skill, avoiding 10–20 minutes of repetitive Word clicking per author.
The official ICMJE coi_disclosure.docx puts every field inside Word Content
Controls (Structured Document Tags, a.k.a. SDTs). Naive python-docx
manipulation of cell.text silently ignores SDT content, so the straightforward
programmatic approach does not work. The historical workaround was to open the
template in Word and manually fill each author's form (21 authors × 13
checkboxes × 2 clicks = ~500 clicks). This skill replaces that by operating
directly on word/document.xml inside the docx zip and doing literal-string
replacement — but that requires the target strings to already exist in the
seed, so the skill ships a pre-filled synthetic seed.
Precedent: a multi-author cohort manuscript submission — 6 authors
auto-filled in ~5 seconds from the synthetic seed with zero Word clicks.
already-populated seed. Creating Content Controls programmatically is
fragile and Word-version-dependent.
directory contains icmje_coi_seed_synthetic.docx with all PII scrubbed
(synthetic name, title, date; metadata reset to ICMJE / Anonymous).
Real-person seeds leak PII through both document.xml and docProps.
script only replaces Date/Name/Title. If any author has a real disclosure,
they must edit in Word manually — the skill's purpose is the common
all-None case.
13 × "None" in document.xml. The script runs this check implicitly by
preserving the seed structure; a post-generation grep is cheap insurance.
Skip this skill when:
in Word; this skill does not help)
guidelines first
Ask the user (or extract from conversation):
[(1, "Author One"), (2, "Author Two"), ...]submission/{journal}/icmje_forms/Present the intake back to the user for confirmation (Gate 1 — user approval)
before generating anything. Explicitly name which authors will get all-None
forms and remind that anyone with a real disclosure must instead fill their own
form in Word.
Invoke the script with the synthetic seed that ships with this skill:
python3 ${SKILL_DIR}/scripts/fill_icmje_coi.py \
--seed ${SKILL_DIR}/templates/icmje_coi_seed_synthetic.docx \
--seed-name "Placeholder Author" \
--seed-title "Placeholder Manuscript Title" \
--seed-date "January 1, 2000" \
--new-title "{exact manuscript title}" \
--new-date "{submission date}" \
--out-dir {out_dir} \
--authors '[[1,"Author One"],[2,"Author Two"],...]'
The script exits nonzero if any seed string is not found, preventing silent
failures.
For each generated docx, confirm:
Placeholder Author, Placeholder Manuscript Title, January 1, 2000)Verification one-liner:
for f in {out_dir}/*.docx; do
python3 -c "
import zipfile, sys
xml = zipfile.ZipFile('$f').read('word/document.xml').decode()
assert xml.count('☒') == 14, 'bad ☒ count'
assert xml.count('None') == 13, 'bad None count'
assert 'Placeholder' not in xml, 'seed leak'
print('✓ $f')
"
done
Present verification results to user (Gate 2 — user review) before handing
off files.
Provide the user with circulation copy to send with each personalized form (write it in the co-authors' preferred language — Korean is common for Korean co-authors):
> Please review the attached ICMJE COI form.
> - If the contents are correct, sign and reply with a PDF.
> - If a change is needed, edit/check the relevant item, sign, and reply.
> - If there are no changes at all, reply "no changes" and return the signed PDF separately.
All 6–21 authors can be emailed in one gws gmail draft batch (**Gate 3 — user
approves batch send** before actually dispatching).
If the user wants a custom seed (e.g., different default wording, pre-filled
items 2/3 with a common grant), generate it once as follows:
templates/icmje_coi_seed_synthetic.docx in Word{project}/submission/{journal}/ or alocal private seeds directory (outside this repo)
--seed /path/to/custom.docx to the script along with the new seedvalues for --seed-name, --seed-title, --seed-date
Do NOT commit custom seeds that contain real author names to the public
medsci-skills repo. Keep them in private per-project directories or a
local private seeds directory (outside this repo).
The shipped templates/icmje_coi_seed_synthetic.docx was derived from the
official ICMJE coi_disclosure.docx through the following steps:
https://www.icmje.org/downloads/coi_disclosure.docx)January 1, 2000Placeholder AuthorPlaceholder Manuscript TitledocProps/core.xml metadata: creator=ICMJE, lastModifiedBy=Anonymous, dates=2000-01-01docProps/app.xml Company/Manager fieldsNo real author's disclosure data is embedded. The file is safe to redistribute.
verbatim from the manuscript's title page or the user's author list.
seed unchanged. If the user asks whether the script "handled the
disclosures," the honest answer is "it cloned the seed's ☒ None entries;
no author-specific disclosure reasoning happened."
the seed must be pre-filled with all-None ☒ + text.
altering the seed structure, stop and escalate to the user; Word-generated
SDT XML is the ground truth.
promote a custom seed, verify by unzip -p seed.docx docProps/core.xml that
no real names remain in metadata before committing.
| Skill | Relationship |
|---|---|
| write-paper | Completes the manuscript whose title is used as input |
| find-journal | Identifies whether the target journal requires ICMJE form |
| add-journal | Journal profile records whether ICMJE form is required |
| revise | After revision, updated title may require re-generating forms |
BMJ ICMJE derivative, etc.) — only the canonical ICMJE form
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
Take aperivue/fill-icmje-coi from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.