← ClaudeAtlas

fill-icmje-coilisted

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.
Aperivue/medsci-skills · ★ 145 · Data & Documents · score 79
Install: claude install-skill Aperivue/medsci-skills
# Fill-ICMJE-COI Skill 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. ## Why This Skill Exists 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. ## Core Principles (Do Not Violate) 1. **Never author SDT XML from scratch.** Only replace existing strings in an already-populated seed. Creating Content Controls programmatically is fragile and Word-version-dependent. 2. **Never ship a real