submission-disclosures

Installation
SKILL.md

/submission-disclosures — The Submission-Time Disclosure Block

Draft the four statements journals now require (or strongly expect) at submission, in one pass: AI-use disclosure, CRediT contributor roles, conflict-of-interest, and data availability. Journals tightened AI-use policies through 2025–2026; an undisclosed-AI finding at a top journal is now a research-integrity problem, not a formatting one — so the statement should be drafted deliberately, not improvised in the submission portal at midnight.

This skill is about the author's disclosures TO the journal. It is unrelated to /disclosure-check, which screens restricted-data outputs for statistical-disclosure risk (small cells, PII). Same word, different worlds.

When to use

  • Preparing a submission or resubmission package and the portal asks for AI-use / COI / data-availability statements.
  • A revise-and-resubmit at a journal that adopted an AI policy since the original submission.
  • A coauthor asks "do we need to say we used Claude/Copilot/ChatGPT on this?"

Phases

Phase 1 — Resolve the journal's actual policy

  1. If a journal short-name is given, read its profile in journal-profiles.md (top-5 econ + AEA-imprint policy notes + poli-sci top-3).
  2. Verify the current policy on the journal's own site (WebSearch/WebFetch: " artificial intelligence policy authors", the journal's submission guidelines page). Policies moved fast in 2025–2026; a cached or remembered policy is not good enough for a submission. Record the URL and retrieval date in the output.
  3. If no explicit AI policy exists, default to the strictest common denominator (disclose tools, scope of use, and human responsibility) — over-disclosure is free; under-disclosure is not.
Installs
15
GitHub Stars
1.6K
First Seen
Jun 14, 2026
submission-disclosures — pedrohcgs/claude-code-my-workflow