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

Joc Writing Style

ASecurity

Use when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35 pages including references/tables/figures/endnotes; abstract <= 150 words). Tightens prose and format; it does not invent content.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Joc Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: joc-writing-style
description: Use when drafting or polishing a Journal of Communication (JoC) manuscript so it reads for the whole field, follows APA 7th edition, and fits the limits (main document <= 35 pages including references/tables/figures/endnotes; abstract <= 150 words). Tightens prose and format; it does not invent content.
---

# Writing Style (joc-writing-style)

A JoC paper must be readable by a communication researcher outside its subfield, formatted to **APA
7th edition**, and disciplined to the **35-page** main-document limit and **150-word** abstract. This
skill is about reaching the field and respecting the format — not about generating claims.

## When to trigger

- Drafting the introduction, framing the contribution, or final polish
- Over the page limit and needing to cut without losing the argument
- Writing the **≤ 150-word abstract**
- Aligning citations/headings/format to APA 7th edition before submission

## Reach the whole field

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 communication broadly. Don't make a generalist dig for
   the "so what."
2. **Minimize subfield jargon** or define it on first use; a health-comm reader should follow a
   computational-comm 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 APA-style headings so a reader can navigate the argument.

## Format to APA 7th edition

- **Citations**: author-date per **APA 7th edition**; keep one consistent style (manage with
  Zotero/BibTeX). References are part of the 35-page count.
- **Manuscript**: **Word (.docx)** (not PDF); **12-pt Times New Roman, double-spaced, 1.0-inch margins**.
- **Anonymize**: JoC is **double-anonymous** — no author names/affiliations/acknowledgments in the main
  document **or supplemental materials**; write **self-citations in the third person**; strip file metadata.
- **Abstract**: **≤ 150 words**, stating question, approach, and finding.

## Fit the page limit (35 pages include abstract, text, references, tables, figures, endnotes)

- Move full specs, robustness grids, and codebooks to the **supplemental materials**.
- Cut throat-clearing and literature dumps; engage the debate, not every paper (see
  `joc-literature-positioning`).
- Tighten endnotes — they count toward the limit.
- Prefer one decisive figure to three redundant tables.
- For a **JoC Forum** piece, hold to **3,000–6,000 words**.

## 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; first-person self-references that break anonymity
- Submitting a PDF when JoC requires Word (.docx)

## Output format

```
【Contribution stated by end of intro?】[Y/N]
【Reads past the subfield?】jargon defined / acronyms spelled? [Y/N]
【Abstract】word count (≤150)
【Length】article ≤ 35 pages (incl. refs/tables/figures/endnotes) / Forum 3,000–6,000 words?
【APA 7th + Word .docx + anonymized + third-person self-cites】[Y/N]
【Next】joc-open-science-and-transparency
```

## Supplementary resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — page/abstract caps, APA 7th edition, Word format, 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".

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 →