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

Amj Writing Style

ASecurity

Use for full-manuscript prose polish of an Academy of Management Journal (AMJ) manuscript — front-loading the argument, active voice, structure, and AOM house style. Polishes language and structure; it does not create the theoretical contribution (amj-contribution-framing) or fix the analysis (amj-data-analysis).

1,052 stars
0 votes
0 copies
1 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 amj-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Amj Writing Style?

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

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

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

Download with Pro
Files
SKILL.md
---
name: amj-writing-style
description: Use for full-manuscript prose polish of an Academy of Management Journal (AMJ) manuscript — front-loading the argument, active voice, structure, and AOM house style. Polishes language and structure; it does not create the theoretical contribution (amj-contribution-framing) or fix the analysis (amj-data-analysis).
---

# Writing Style (amj-writing-style)

## When to trigger

- The argument is buried under jargon, hedging, or passive constructions
- The introduction does not make the contribution clear in its first page
- Section logic wanders; the reader cannot follow the theory → method → results → discussion arc
- Sentences are long and nominalized; the "actor doing the action" is hidden
- This is late-stage polish *after* the theory, design, and contribution are settled

## The AMJ prose standard

AMJ values prose that is **rigorous yet readable**: the theoretical argument should be visible to a reader from another division. Front-load the point — say what you argue, then support it. Write in the active voice with human/organizational actors as subjects. Hedge precisely (state what the data show), not defensively (avoid stacking "may possibly suggest"). AMJ's *From the Editors* (FTE) series has devoted whole editorials to storytelling and crafting the introduction — the journal genuinely rewards a paper that "tells a story," so treat narrative arc as a substantive standard, not decoration.

## Structure to enforce

Standard full structure: **Introduction → Theory & Hypotheses → Methods → Results → Discussion**. Each section earns its place:

- **Introduction**: phenomenon hook → conversation/tension → question → approach → contribution, on the first 1–2 pages.
- **Theory & Hypotheses**: each subsection builds toward a numbered hypothesis with an explicit mechanism.
- **Methods**: enough detail to replicate; sample, measures, analysis, validity.
- **Results**: report tests in hypothesis order; interpret, do not just narrate the tables.
- **Discussion**: theoretical implications first, then practical, limitations, future research.

## Sentence- and paragraph-level moves

- **Topic sentences**: every paragraph opens with its claim; the rest supports it.
- **Active voice**: "We theorize that…" / "Leaders allocate attention…" not "It is theorized that…".
- **De-nominalize**: "managers decide" beats "managerial decision-making occurs."
- **Define constructs once**, then use the term consistently — no synonym drift.
- **Signpost**: connect sections explicitly ("Having established X, we now…").
- **Cut hedging stacks**: one calibrated qualifier, not three.
- **Consistent terminology** for each construct, hypothesis label, and variable across text, tables, and figures.

## House style (verify against the current AOM Style Guide)

- Follow AOM/APA-style conventions for citations, headings, and references as specified in the current AMJ Style Guide for Authors.
- US spelling and AOM heading hierarchy; consistent tense (past tense for what you did/found, present for established theory).
- The full manuscript main body must fit the **40-page maximum** (text + references + appendices; tables/figures excluded), **double-spaced, Times New Roman 12-pt, 1-inch margins** — so trimming targets prose, not just exhibits, and a bloated reference list eats into your page budget.

## Checklist

- [ ] Contribution is clear within the first page of the introduction
- [ ] Active voice and concrete actors dominate; passive used only deliberately
- [ ] Every paragraph has a claim-first topic sentence
- [ ] Construct terms are defined once and used consistently everywhere
- [ ] Sections are signposted; the theory→method→results→discussion arc is followed
- [ ] Hedging is calibrated, not stacked
- [ ] Citations/headings/references conform to the current AMJ Style Guide
- [ ] Main body ≤ 40 pages (refs + appendices count; tables/figures do not); 12-pt TNR, double-spaced

## Anti-patterns

- **Buried lede**: the contribution surfaces only in the discussion.
- **Passive fog**: "it was found that" hiding who did what.
- **Jargon walls**: dense theoretical terms with no plain-language anchor.
- **Synonym drift**: calling the same construct three different names.
- **Defensive hedging**: "may potentially possibly suggest" instead of a precise claim.
- **Tense chaos**: switching between past and present for the same event.

## Output format

```
【Intro clarity】contribution visible on page 1? yes/no
【Voice】active-voice dominant? flagged passives: [...]
【Topic sentences】claim-first throughout? exceptions: [...]
【Terminology】construct names consistent? drift: [...]
【Structure/signposting】arc intact? gaps: [...]
【House style】AOM/APA citations & headings: pass/fix
【Length】main body vs. 40-page limit (refs+appendices incl.): ok/trim
【Next step】amj-submission
```

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', ...

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