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

Poq Writing Style

ASecurity

Use when drafting or polishing a Public Opinion Quarterly (POQ) manuscript so it reads for a public-opinion and survey-methodology audience and fits the type caps (Original Article ≤ 6,500 words of text and notes; Research Note < 3,000; Polls in Context ≤ 2,500). POQ word counts cover text and notes but exclude figures, tables, references, and appendices. Tightens prose and format; it does not invent content.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Poq Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: poq-writing-style
description: Use when drafting or polishing a Public Opinion Quarterly (POQ) manuscript so it reads for a public-opinion and survey-methodology audience and fits the type caps (Original Article ≤ 6,500 words of text and notes; Research Note < 3,000; Polls in Context ≤ 2,500). POQ word counts cover text and notes but exclude figures, tables, references, and appendices. Tightens prose and format; it does not invent content.
---

# Writing Style (poq-writing-style)

A POQ paper must be readable by both substantive opinion scholars and survey methodologists, and
disciplined to the cap for its type. The word count covers **text and notes** but **excludes figures,
tables, references, and appendices** — so the AAPOR disclosure appendix and exhibits do not count
against you. This skill is about reaching the POQ audience and respecting format — not 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 abstract (confirm the current requirement — 待核实 on exact cap)
- Aligning citations and format before submission

## Reach the POQ audience

1. **Front-load the contribution.** By the end of the introduction the reader knows the question, the
   data, the finding, and whether the contribution is to **opinion theory, current opinion, or survey
   validity**. Do not bury the "so what."
2. **Name the methodological move plainly.** State the survey design and the error source you address;
   POQ readers expect to see coverage/nonresponse/wording/mode/weighting handled, not glossed.
3. **Define jargon on first use.** A communication scholar should follow a methods paper and vice
   versa; spell out acronyms (AAPOR, TSE, RR, DEFF, AMCE, MRP) on first appearance.
4. **Argument-first prose.** Lead with claims; use design-based evidence to support them. Avoid "the
   data show…" without saying what they show and why it matters.

## Format & front matter

- **Citations**: keep one consistent reference style (manage with Zotero/BibTeX); references excluded
  from the word count.
- **Disclosure**: ensure the **"Appendix A: Disclosure Elements"** is present and referenced (see
  `poq-survey-design-and-measurement`); it does not count toward the cap.
- **Anonymize**: POQ is **double-blind** — no author names/affiliations/acknowledgments in the
  manuscript, no obvious self-references, strip identifying file metadata.
- **Data Availability Statement**: plan the DAS for the endmatter (see `poq-transparency-and-data-policy`).

## Fit the type cap (text + notes; excludes figures, tables, references, appendices)

- Move detailed methods, full specifications, and extended robustness to **appendices** (excluded).
- Cut throat-clearing and literature dumps; engage the debate, not every paper (see
  `poq-literature-positioning`).
- Tighten footnotes — they **count** toward the limit (notes are in the cap).
- Prefer one decisive trend figure to three redundant tables.

## Anti-patterns

- An intro that never states whether the contribution is to opinion or to survey methods
- Burying the methodological move (how error was handled) deep in the paper
- Padding a Research Note (< 3,000) or Polls in Context (≤ 2,500) toward Article length
- Acknowledgments or self-references that break double-blind anonymity
- Putting disclosable methods in long footnotes (which count) instead of Appendix A (which does not)

## Output format

```
【Contribution stated by end of intro?】opinion / current-opinion / survey-validity [Y/N]
【Methodological move named?】error source + design plain? [Y/N]
【Abstract】present + within current requirement (待核实)
【Word count】Article ≤6,500 / Note <3,000 / Polls ≤2,500 (text + notes)?
【Anonymized + DAS planned + Appendix A referenced】[Y/N]
【Next】poq-transparency-and-data-policy
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — reference managers and writing tooling
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — type caps, what the word count includes, double-blind anonymity

Attribution

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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".

1066601 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.

651 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 →