Best for
- Manuscript accepted for submission to an ICMJE member journal
- 3+ co-authors with no real financial conflicts
- Editorial Manager / submission portal requires per-author ICMJE disclosure docx
Aperivue/medsci-skills/skills/fill-icmje-coi/SKILL.md
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" f
Decision brief
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…
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/Aperivue/medsci-skills --skill "skills/fill-icmje-coi"Inspect the Agent Skill "fill-icmje-coi" from https://github.com/Aperivue/medsci-skills/blob/048afbc14a235058a220a63daec517851145c445/skills/fill-icmje-coi/SKILL.md at commit 048afbc14a235058a220a63daec517851145c445. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Ask the user (or extract from conversation): 1. Manuscript title (exact, as it will appear on title page) 2. Submission date (e.g., "April 20, 2026") 3. Author list — ordered, one name per slot: [(1, "Author One"), (2, "Author Two"), ...] 4. Output directory — typically submissi…
Invoke the script with the synthetic seed that ships with this skill:
For each generated docx, confirm: - ☒ count = 14 (13 disclosure items + 1 final certification) - "None" count = 13 - Correct name appears after "Your Name:" - Correct title appears after "Manuscript Title:" - No leakage of seed placeholder strings (Placeholder Author, Placeholde…
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):
The official ICMJE coidisclosure.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 worka…
Permission review
The documentation asks the agent to run terminal commands or scripts.
Invoke the script with the synthetic seed that ships with this skill:The documentation asks the agent to run terminal commands or scripts.
python3 ${SKILL_DIR}/scripts/fill_icmje_coi.py \The documentation asks the agent to create, modify, or delete local files.
Save as a new file under `{project}/submission/{journal}/` or aEvidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 273 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.
Effect: a full author roster auto-fills in seconds from the synthetic seed, with zero Word clicks.
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.Skip this skill when:
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 a
local private seeds directory (outside this repo)--seed /path/to/custom.docx to the script along with the new seed
values for --seed-name, --seed-title, --seed-dateDo 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.
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 |
Frequently asked questions
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…
The source record exposes this install command: npx skills add https://github.com/Aperivue/medsci-skills --skill "skills/fill-icmje-coi". Inspect the command and pinned source before running it.
Static rules flagged exec-script, write-files in the source; the page lists the matching lines and excerpts.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
wanshuiyin/Auto-claude-code-research-in-sleep
Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.