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

Amr Writing Style

ASecurity

Use when polishing the prose and structure of an Academy of Management Review (AMR) manuscript to AOM house style and an argument-driven voice. Late-stage polish; it does NOT build theory or check logic — do those first with amr-theory-development and amr-data-analysis.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amr Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: amr-writing-style
description: Use when polishing the prose and structure of an Academy of Management Review (AMR) manuscript to AOM house style and an argument-driven voice. Late-stage polish; it does NOT build theory or check logic — do those first with amr-theory-development and amr-data-analysis.
---

# Writing Style: AOM House Style, Argument-Driven Prose (amr-writing-style)

## When to trigger

- The theory and contribution are settled; now the prose needs polish
- The draft reads like a literature review or an essay, not a built argument
- Sections are present but the manuscript does not "flow" toward the contribution
- You are unsure of AMR's structural conventions

## AMR's structure (durable form)

AMR conceptual articles follow a recognizable arc. Verify exact requirements on the current
AOM author page, but the durable shape is:

1. **Introduction — the theoretical puzzle.** Open with the tension, not a definition or a
   dictionary opening. State the puzzle, the conversation, and your move within the first
   two pages. Tell the reader what theory cannot currently do and that this paper fixes it.
2. **Theoretical development.** Constructs defined → assumptions → relationships +
   mechanisms → propositions (each earned by argument). This is the body and the bulk.
3. **The conceptual model / figure** integrated where it clarifies the argument.
4. **Discussion.** Contribution (what's new, differentiated), boundary conditions, and
   implications for theory, future research, and practice.

There is **no methods, results, or data section** — AMR is theory-only. The reasoning *is*
the contribution, so make the *Why* vivid (Whetten, AMR 1989, DOI 10.5465/amr.1989.4308371);
define constructs precisely and consistently (Suddaby, AMR 2010, DOI 10.5465/amr.2010.0419).
Exemplar to study for narrative: Oliver's "Strategic Responses to Institutional Processes"
(AMR 1991, DOI 10.5465/amr.1991.4279002) — puzzle → typology → propositions → implications,
no methods, no results.

## Voice and prose discipline

- **Argument, not survey.** Every paragraph should advance the theory. If a paragraph only
  reports what others found, it is review filler — cut or repurpose it to set up your move.
- **Define before you use.** A construct's first appearance carries its definition; use the
  exact same label every time afterward. Terminological drift reads as conceptual fuzziness.
- **Signpost the logic.** "Because... it follows that..."; "This implies..."; "We therefore
  propose..." Make the inferential moves visible — at AMR the prose *is* the proof.
- **Propositions in the text** are set off and numbered, each immediately following the
  argument that earns it.
- **Precision over flourish.** AMR prizes conceptual precision. Avoid vague intensifiers
  ("very important," "highly significant") and metaphors that do no theoretical work.
- **No hypothesis vocabulary.** Never write "we hypothesize," "H1," "results show," "we
  find," or "supported / not supported." AMR uses **propositions** because nothing is tested;
  that vocabulary is AMJ's and reads immediately as wrong-journal to AMR editors.
- **AOM/APA style mechanics.** **APA-style** author–date in-text citations; full reference
  list per the Academy of Management (APA-derived) style guide; double-spaced manuscript.
  (APA edition UNVERIFIED — confirm in the style guide; see `resources/official-source-map.md`.)
  Verify current length and abstract limits before submitting (also UNVERIFIED here).
  Submission-stage facts such as AMR's current editor, no-fee policy, and ScholarOne link
  belong in `amr-submission` and `resources/official-source-map.md`, not in prose edits.

## Self-edit passes

- **Puzzle pass**: is the tension on page 1–2, or buried?
- **Survey pass**: highlight every sentence that only reports prior work; if it does not set up your move, cut it.
- **Definition pass**: is every construct defined once and labeled consistently?
- **Inference pass**: can a skeptical reader follow each step from premise to proposition?
- **So-what pass**: does the discussion differentiate the contribution, not restate it?

## Checklist

- [ ] Introduction states the puzzle and the move within ~2 pages
- [ ] No methods/results/data section exists
- [ ] Every paragraph advances the argument; no review-essay filler
- [ ] Constructs defined on first use; labels consistent throughout
- [ ] Inferential connectives make the logic explicit
- [ ] Propositions are numbered and follow their arguments
- [ ] Discussion differentiates the contribution and states implications
- [ ] AOM author-date citations and reference style applied (verify current guide)

## Anti-patterns

- A literature review masquerading as theory: paragraphs of "X found... Y found..."
- A dictionary or epigraph opening that delays the puzzle
- Construct labels that drift (same idea, three names)
- Buried propositions the reader must hunt for
- Empty intensifiers and decorative metaphor substituting for precise claims
- A discussion that summarizes the paper instead of stating what is newly thinkable

## Output format

```
【Puzzle on page 1–2?】yes / fix
【Review-essay filler】[paragraphs to cut/repurpose]
【Construct-label consistency】ok / drift at: ...
【Logic signposting】explicit / add at: ...
【AOM style】citations + references conform (verify)
【Next step】amr-submission
```

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 →