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 Literature Positioning

ASecurity

Use when the front end of an Academy of Management Journal (AMJ) manuscript needs to engage the right literatures and stake a clear position in an ongoing theoretical conversation. Positions the paper among theories; it does not derive the hypotheses (amj-theory-development) or write the contribution paragraph (amj-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill amj-literature-positioning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Amj Literature Positioning?

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

Security grade badge for Amj Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-amj-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-amj-literature-positioning)

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

Download with Pro
Files
SKILL.md
---
name: amj-literature-positioning
description: Use when the front end of an Academy of Management Journal (AMJ) manuscript needs to engage the right literatures and stake a clear position in an ongoing theoretical conversation. Positions the paper among theories; it does not derive the hypotheses (amj-theory-development) or write the contribution paragraph (amj-contribution-framing).
---

# Literature Positioning (amj-literature-positioning)

## When to trigger

- The introduction reads as "no one has studied X" (gap-spotting) rather than joining a debate
- The literature review is an annotated list of prior findings, not an argument
- Canonical theoretical works in the focal domain are missing or cited only in passing
- You are unsure which conversation the paper enters and which scholars are the audience
- A reviewer says "I don't see how this advances the literature" or "this misreads prior work"

## The positioning move AMJ rewards

AMJ papers join an **ongoing theoretical conversation** and change it. The front end should name the conversation, show the unresolved tension or contradiction in it, and signal how this study resolves or extends it. "Gap-spotting" — pointing to an empty cell in a table of prior studies — is treated as a weak motivation; AMJ wants a *problematization*: surfacing and challenging an assumption the literature has taken for granted (Alvesson & Sandberg's problematization argument is the standard reference for this move). AMJ's *From the Editors* editorials repeatedly press the "so what?" and "who cares?" tests — your positioning must make the contribution matter to the broad management readership, not only a niche.

## Three legitimate motivating moves

1. **Tension between theories** — two literatures predict opposite things; your study adjudicates.
2. **Boundary/contingency** — an established effect should not hold (or should reverse) under a condition the literature has overlooked, for a theoretical reason.
3. **Problematization** — an assumption underlying a literature is questionable; relaxing it changes predictions.

A bare "gap" (no study has done X) is *not* on this list unless you supply the theoretical reason the gap matters.

## Engaging the literatures

- Identify the **focal literature** (the conversation you join) and any **supporting literatures** (the lens or mechanism you import). Keep them distinct.
- Cite the canonical theoretical works that define the focal construct/theory, plus recent papers that show the conversation is live — favor AMJ and its AOM sister journals (AMR for the theory side, AMD for emerging phenomena) and, where the conversation spans them, ASQ and SMJ.
- Review *to build your argument*, not to catalog: each cited stream should end with the tension your study addresses.
- Place the paper relative to the closest 2–3 prior studies and say precisely how yours differs in mechanism, level, boundary, or design — not merely in context.

## Front-end structure

A typical AMJ introduction: (1) hook the phenomenon, (2) name the conversation and the tension, (3) state the research question, (4) preview the theoretical approach and study, (5) state the intended contribution. The literature review/theory section then develops the streams in the order the hypotheses need them.

## Checklist

- [ ] The introduction names a specific theoretical conversation, not an empty cell
- [ ] Motivation is a tension, boundary, or problematization — not bare gap-spotting
- [ ] Canonical theoretical works defining the focal construct are cited and used
- [ ] Recent AMJ/AMR/ASQ/SMJ papers establish the conversation is current
- [ ] Closest 2–3 prior studies are named with a precise statement of how this paper differs
- [ ] Each literature stream ends pointing at the tension this study resolves
- [ ] The intended audience (division/scholars) is clear from the framing

## Anti-patterns

- **Gap-spotting**: "No prior work has examined X in Y" as the sole motivation.
- **Citation dump**: long lists of "(Author, year; Author, year)" with no argumentative thread.
- **Misreading prior work**: mischaracterizing a cited study (reviewers are often its authors).
- **Context-only novelty**: claiming contribution because the setting is new, not the mechanism.
- **Burying the focal theory**: the lens you actually use appears only in the methods.
- **Ignoring the obvious rival literature**: a reviewer's first move is to name the stream you skipped.

## Output format

```
【Focal conversation】the literature/theory you join ...
【Motivating move】tension / boundary / problematization (state it)
【Supporting literatures】lens or mechanism imported ...
【Canonical works engaged】[...]
【Closest prior studies】[...] — how this paper differs: ...
【Audience】division / scholars ...
【Next step】amj-methods (match design to the question)
```

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 →