Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Apsr Writing Style

ASecurity

Use when drafting or polishing an American Political Science Review (APSR) manuscript so it reads for the whole discipline, follows the APSA Style Manual, and fits the word caps (most Articles < 11,000 words; Research Notes < 7,000; abstract <= 150 words). Tightens prose and format; it does not invent content.

1,052 stars
0 votes
0 copies
0 views
Added 6/4/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill apsr-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Apsr Writing Style?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Apsr Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-apsr-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-apsr-writing-style)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: apsr-writing-style
description: Use when drafting or polishing an American Political Science Review (APSR) manuscript so it reads for the whole discipline, follows the APSA Style Manual, and fits the word caps (most Articles < 11,000 words; Research Notes < 7,000; abstract <= 150 words). Tightens prose and format; it does not invent content.
---

# Writing Style (apsr-writing-style)

An APSR paper must be readable by a political scientist outside its subfield, formatted to the **APSA
Style Manual for Political Science**, and disciplined to the word cap. This skill is about reaching the
discipline and respecting the format — not about generating claims.

## When to trigger

- Drafting the introduction, framing the contribution, or final polish
- Over the word cap and needing to cut without losing the argument
- Writing the **≤ 150-word abstract**
- Aligning citations/headings/format to APSA style before submission

## Reach the whole discipline

1. **Front-load the contribution.** By the end of the introduction the reader knows the question, the
   argument, the evidence, and why it matters to political science broadly. Don't make a generalist
   dig for the "so what."
2. **Minimize subfield jargon** or define it on first use; an IR reader should follow an Americanist
   paper. Spell out acronyms.
3. **Argument-first prose.** Lead with claims; use evidence to support them. Avoid "the data show…"
   without saying what they show and why it matters.
4. **Signpost.** Clear section structure so a reader can navigate the argument.

## Format to APSA style

- **Citations**: author-date per the APSA Style Manual; keep one consistent style (manage with
  Zotero/BibTeX). References excluded from the word count.
- **Front page**: include the **word count**; corresponding author has an **ORCID iD**.
- **Anonymize**: APSR is **double-anonymous** — no author names/affiliations/acknowledgments in the
  manuscript, no obvious self-references ("as we showed in…"), strip identifying file metadata.
- **Abstract**: **≤ 150 words**, stating question, approach, and finding.

## Fit the word cap (counts include tables/figures/footnotes; excludes references + appendices)

- Move balance tables, full specs, and extended robustness to the **online appendix**.
- Cut throat-clearing and literature dumps; engage the debate, not every paper (see
  `apsr-literature-positioning`).
- Tighten footnotes — they count toward the limit.
- Prefer one decisive figure to three redundant tables.

## Anti-patterns

- A subfield-insider intro that never states general significance
- Burying the contribution in the middle of the paper
- An abstract over 150 words or one that hides the finding
- Mixed citation styles; acknowledgments or self-references that break anonymity
- Padding a Research Note toward Article length

## Output format

```
【Contribution stated by end of intro?】[Y/N]
【Reads past the subfield?】jargon defined / acronyms spelled? [Y/N]
【Abstract】word count (≤150)
【Word count】articles <11,000 / notes <7,000 (incl. tables/figures/footnotes)?
【APSA style + anonymized + ORCID】[Y/N]
【Next】apsr-transparency-and-data-policy
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — word/abstract caps, APSA Style Manual, ORCID, anonymity

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693161 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →