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 Contribution Framing

ASecurity

Use when turning results into an explicit theoretical contribution for an Academy of Management Journal (AMJ) manuscript — the "what new theory do we learn?" statement and the discussion section. Frames the contribution and implications; it does not build the original theory (amj-theory-development) or run the analysis (amj-data-analysis).

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amj Contribution Framing?

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

Security grade badge for Amj Contribution Framing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-amj-contribution-framing/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-amj-contribution-framing)

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

Download with Pro
Files
SKILL.md
---
name: amj-contribution-framing
description: Use when turning results into an explicit theoretical contribution for an Academy of Management Journal (AMJ) manuscript — the "what new theory do we learn?" statement and the discussion section. Frames the contribution and implications; it does not build the original theory (amj-theory-development) or run the analysis (amj-data-analysis).
---

# Contribution Framing & Discussion (amj-contribution-framing)

## When to trigger

- Results are in but the "so what for theory" is vague or missing
- The discussion restates findings instead of advancing the theory
- A reviewer says the contribution is "incremental," "descriptive," or "unclear"
- You can describe what you found but not what the field now knows that it did not before
- The practical-implications paragraph is generic ("managers should pay attention to X")

## The contribution question AMJ asks

AMJ evaluates every paper on **three criteria**: a strong empirical contribution, a meaningful **theoretical** contribution, and **practical relevance**. The empirical contribution must be paired with a theoretical one: *what do we now understand about the theory that we did not before?* — and the discussion must also speak to why it matters for management practice. A clear, defensible theoretical answer is essential; strong results with no theoretical advance read as a technical report, not an AMJ paper. AMJ's *From the Editors* tradition frames this as the "so what?" and "who cares?" tests.

## Types of theoretical contribution (claim the right one)

| Contribution type            | What it does                                                       |
|------------------------------|--------------------------------------------------------------------|
| Reveal a new mechanism       | Explains *why* an established effect occurs                         |
| Establish a boundary         | Shows *when* an effect holds, weakens, or reverses                  |
| Adjudicate competing theories| Shows which of two rival predictions holds, and why                |
| Integrate / bridge           | Connects two literatures into a more general account                |
| Challenge an assumption      | Overturns a taken-for-granted premise (problematization)           |
| Introduce/refine a construct | Conceptualizes and validates a new construct that earns its keep   |

State explicitly which type(s) you claim; do not gesture vaguely at "contributing to the literature."

## Writing the discussion

A strong AMJ discussion typically:

1. **Restates the core finding** in theoretical terms (one short paragraph, no number-dump).
2. **Theoretical implications** — for each, name the literature, state what changes, and how (this is the heart of the section).
3. **Practical implications** — a genuine AMJ criterion, not an afterthought: specific to the phenomenon and grounded in the findings, never boilerplate. (Practical relevance is one of AMJ's three formal acceptance criteria, but it complements rather than substitutes for the theoretical contribution.)
4. **Limitations** — honest, but framed as boundary conditions and future directions, not as fatal flaws.
5. **Future research** — concrete questions the study opens, tied to the mechanism/boundary.

Match the discussion to the front end: the contributions you claim here must be the ones you promised in the introduction. A reviewer will check that the intro's promise and the discussion's delivery line up.

## The contribution statement (intro and discussion)

Draft 2–4 explicit contribution sentences and place a version in the introduction and the discussion. Each should be of the form: "We contribute to [literature] by showing [mechanism/boundary/integration], which advances [theory] because [reason]."

## Checklist

- [ ] The theoretical contribution type is named (mechanism/boundary/adjudication/integration/assumption/construct)
- [ ] 2–4 explicit contribution sentences, consistent between intro and discussion
- [ ] Discussion advances theory, not just restates results
- [ ] Practical implications are specific to the phenomenon and the findings
- [ ] Limitations framed as boundary conditions + future directions, not fatal flaws
- [ ] Future research questions follow from the mechanism/boundary, not generic
- [ ] Intro's promised contribution = discussion's delivered contribution

## Anti-patterns

- **Restating results as "contribution"**: "We found A affects B" is a finding, not a contribution.
- **Incremental framing**: "We extend prior work to a new setting" with no theoretical change.
- **Over-claiming**: asserting a paradigm shift the single study cannot support.
- **Boilerplate practical implications**: "managers should be aware of X" untethered from the data.
- **Intro/discussion mismatch**: promising one contribution, delivering another.
- **Limitations as confession**: listing flaws without converting them into boundary conditions.

## Output format

```
【Contribution type(s)】mechanism / boundary / adjudication / integration / assumption / construct
【Contribution sentences】1–4, intro + discussion aligned
【Theoretical implications】per literature: what changes and why ...
【Practical implications】specific, grounded ...
【Limitations → boundaries】...
【Future research】concrete, mechanism-tied ...
【Intro↔discussion consistency】yes/no
【Next step】amj-tables-figures, then amj-writing-style
```

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 →