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

Jama Writing Style

ASecurity

Use when tightening prose and removing spin from a JAMA manuscript to match the journal's clinical house style and the AMA Manual of Style. Polishes language and framing; it does NOT change the analysis or the reported numbers.

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

Works with

cli

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jama Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jama-writing-style
description: Use when tightening prose and removing spin from a JAMA manuscript to match the journal's clinical house style and the AMA Manual of Style. Polishes language and framing; it does NOT change the analysis or the reported numbers.
---

# Writing Style & House Style (jama-writing-style)

## When to trigger

- Prose is verbose, hedged, or jargon-heavy for a general clinician audience
- The Conclusions overstate the data ("spin")
- Observational findings are written with causal verbs
- Late-stage polish before submission, after design/stats/exhibits are settled

## House-style essentials (AMA Manual of Style)

- JAMA follows the **AMA Manual of Style**. Conform numbers, units, abbreviations, statistical notation, and reference format to it — verify current rules in the manual / author instructions.
- **SI units** with conventional units as needed; define every abbreviation at first use; avoid undefined acronyms.
- **Person-first, non-stigmatizing language** (e.g., "patients with diabetes," not "diabetics"); report and justify race/ethnicity and sex/gender per current JAMA guidance.
- Exact p-values (P = .04, not P < .05); leading zeros omitted for p-values per AMA convention; estimates always paired with 95% CIs.
- Active voice and short sentences where possible; the IMRaD structure (Introduction, Methods, Results, Discussion).

## Avoiding "spin"

Spin is language that makes results sound better than the data support. JAMA reviewers and editors actively police it.

| Spin pattern                                            | Fix                                                       |
|---------------------------------------------------------|-----------------------------------------------------------|
| Null primary outcome, upbeat conclusion                 | State the primary result plainly; do not pivot to secondaries |
| Secondary/post hoc outcome framed as main finding       | Foreground the pre-specified primary outcome              |
| "Trend toward significance" for a non-significant result | Report the estimate + CI; avoid the phrase                |
| Causal verbs ("reduced," "caused") for observational data | Use associational verbs ("was associated with")           |
| "Safe and well tolerated" beyond what harms data show   | Report harms quantitatively; calibrate the claim          |
| Over-generalizing beyond the studied population         | Bound the conclusion to the sample/setting                |

## Discussion structure JAMA expects

1. Brief statement of the principal findings (tied to the primary outcome).
2. Comparison with prior evidence; how this study adds.
3. Possible mechanisms / explanations (without overreach).
4. **Limitations** — candid, specific (bias, generalizability, power, missing data).
5. Conclusions and clinical relevance, proportionate to the evidence.

## Checklist

- [ ] Abstract, Results, and Conclusions agree numerically and in tone
- [ ] Conclusion is bounded by the primary outcome; no spin
- [ ] Observational findings use associational language
- [ ] Harms reported quantitatively before any "safe/tolerated" claim
- [ ] Abbreviations defined at first use; SI units; AMA statistical notation
- [ ] Person-first, non-stigmatizing language; race/sex reported per guidance
- [ ] A specific, candid Limitations paragraph is present
- [ ] Reference format follows AMA style (verify current rules)

## Anti-patterns

- Spin: a positive-sounding conclusion over a null primary outcome
- Causal language for an observational association
- "Trend toward significance" / "marginally significant"
- Burying limitations or making them generic ("as with all studies…")
- Jargon and undefined acronyms that exclude a general clinician reader
- Tone in the abstract that the body does not support

## Output format

```
【Spin found】none / instances: ...
【Causal-vs-associational language correct】yes / fixes: ...
【Harms calibrated】yes / no
【Limitations specific】yes / no
【AMA style conformance】numbers/units/abbrev/refs: ...
【Next skill】jama-cover-letter
```

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 →