io-writing-style
Use when drafting or polishing an International Organization (IO) manuscript so it reads for international-relations scholars across paradigms, fits the word caps (Research Article <= 14,000; Research Note <= 8,000; Essay <= 10,000, including tables, figures, and notes but excluding the bibliography), and meets IO format conventions (double-blind, third-person self-citation, short author-date footnotes, separate abstract/word-count/acknowledgments). Tightens prose and format; it does not invent content.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-writing-style --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Writing Style (io-writing-style) An IO paper must be readable by an international-relations scholar from a different tradition, framed around a **generalizable IR theory**, and disciplined to the word cap. This skill is about reaching the IR field and respecting IO's format — not about generating claims. ## When to trigger - Drafting the introduction, framing the IR contribution, or final polish - Over the word cap and needing to cut without losing the argument - Preparing the **abstract, word count, and acknowledgments** (submitted **separately** from the manuscript) - Aligning citations/footnotes/format to IO conventions before submission ## Reach the IR field (across paradigms) 1. **Front-load the IR contribution.** By the end of the introduction the reader knows the international question, the theory, the evidence, and why it matters for international politics. Don't make a reader from another tradition dig for the "so what." 2. **Speak across rationalist / constructivist / IPE / security divides.** Define paradigm-specific jargon on first use; a security scholar should follow an IPE paper and vice versa. Spell out IGO and dataset acronyms. 3. **Argument-first prose.** Lead w
- When to trigger
- Reach the IR field (across paradigms)
- Format to IO conventions
- Fit the word cap (counts include tables/figures/notes; exclude the bibliography)
- The IO introduction, paragraph by paragraph (a working template)
- Prose register for a methodologically plural IR audience
- Anti-patterns
- Output format
- Supplementary resources
What does the io-writing-style skill do?
Use when drafting or polishing an International Organization (IO) manuscript so it reads for international-relations scholars across paradigms, fits the word caps (Research Article <= 14,000; Research Note <= 8,000; Essay <= 10,000, including tables, figures, and notes but excluding the bibliography), and meets IO format conventions (double-blind, third-person self-citation, short author-date footnotes, separate abstract/word-count/acknowledgments). Tightens prose and format; it does not invent content.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill io-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.