# Submission Disclosures

Generate the submission-time disclosure block for a manuscript, the AI-use disclosure...

- Repository: https://github.com/pedrohcgs/claude-code-my-workflow (1676 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-09-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add pedrohcgs/claude-code-my-workflow --skill submission-disclosures -g -a claude-code -y`
Codex: `npx skills add pedrohcgs/claude-code-my-workflow --skill submission-disclosures -g -a codex -y`
Cursor: `npx skills add pedrohcgs/claude-code-my-workflow --skill submission-disclosures -g -a cursor -y`
Gemini CLI: `npx skills add pedrohcgs/claude-code-my-workflow --skill submission-disclosures -g -a gemini-cli -y`

## Description

Generate the submission-time disclosure block for a manuscript, the AI-use disclosure statement matched to the target journal's policy, CRediT author-contribution roles, conflict-of-interest statement, and data-availability statement. Use when the user says "AI disclosure", "disclosure statement", "do I need to disclose Claude", "CRediT roles", "conflict of interest statement", "data availability statement", or is preparing a submission package. NOT statistical-disclosure screening of restricted-data outputs, that is /disclosure-check.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /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`](../disclosure-check/SKILL.md), 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`](../../references/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`: "<journal> 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.

### Phase 2, Inventory what was actually used

The rest: https://github.com/pedrohcgs/claude-code-my-workflow/blob/HEAD/.claude/skills/submission-disclosures/SKILL.md