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 Theory Development

ASecurity

Use when the theoretical argument and hypotheses are the bottleneck for an Academy of Management Journal (AMJ) manuscript — building a mechanism and deriving testable hypotheses a priori. Constructs the theory; it does not run the analysis (amj-data-analysis) or write the final contribution paragraph (amj-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amj Theory Development?

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

Security grade badge for Amj Theory Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-amj-theory-development/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-amj-theory-development)

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

Download with Pro
Files
SKILL.md
---
name: amj-theory-development
description: Use when the theoretical argument and hypotheses are the bottleneck for an Academy of Management Journal (AMJ) manuscript — building a mechanism and deriving testable hypotheses a priori. Constructs the theory; it does not run the analysis (amj-data-analysis) or write the final contribution paragraph (amj-contribution-framing).
---

# Theory Development & Hypotheses (amj-theory-development)

## When to trigger

- Hypotheses read as bald predictions ("A is positively related to B") with no mechanism
- You have results and are tempted to write hypotheses around them (HARKing risk)
- The argument leans on one borrowed citation rather than a developed logic
- Mediators/moderators are present in the data but not theorized
- A reviewer says "the theory is thin," "the logic is underdeveloped," or "why would this be true?"

## The AMJ theory bar

AMJ does not publish atheoretical work — its mission is "to publish empirical research that tests, extends, or builds management theory." Every hypothesis must be **derived from an articulated theoretical mechanism**, written *before* the results are known. The argument should make a reader feel they understand *why* the effect occurs and *under what conditions* it strengthens or reverses.

For **theory-building** (typically qualitative) papers, AMJ does *not* expect a priori hypotheses; it expects a grounded model with emergent propositions. Eisenhardt and Graebner's AMJ guidance on building theory from cases is the canonical exemplar for how rich data become crisp constructs and propositions — do not force such a study into a hypothetico-deductive template.

## Building a hypothesis (the mechanism chain)

For each hypothesis, write the explicit chain — do not skip steps:

1. **Antecedent** — the predictor and why it matters in this context.
2. **Mechanism** — the theoretical process linking antecedent to outcome (e.g., social exchange, signaling, attention allocation, identity threat, resource dependence). Name the theory and the process verb (motivates, signals, depletes, legitimates).
3. **Outcome** — the dependent construct, defined at a stated level of analysis.
4. **Direction & form** — sign, and whether linear, curvilinear, or threshold.
5. **Boundary** — the moderator(s) and the theoretical reason the mechanism is stronger/weaker.

State the level of analysis explicitly (individual, team, firm) and keep the theory at the level where the mechanism operates; flag cross-level mediation as such.

## Mediation and moderation done right

- **Mediation**: theorize the *process* construct before testing it; do not infer the mechanism from a significant indirect effect alone. An indirect effect is evidence *for* a theorized mechanism, not a substitute for the theory.
- **Moderation**: give a substantive reason the slope changes — "it depends on" is not a theory until you say *why* it depends.
- **Curvilinear**: justify the turning point theoretically (two opposing forces), not just by a significant squared term.

## Hypothesis hygiene

- Number hypotheses and keep them to a defensible set (typically a focal effect plus a mechanism and one or two boundaries). Avoid a "kitchen sink" of ten weakly motivated predictions.
- Each hypothesis must be falsifiable and tied to a specific test you will run.
- Competing/alternative theoretical explanations should be named and addressed, not ignored.
- A figure of the theoretical model (boxes and arrows) should map one-to-one to the hypotheses.

## Checklist

- [ ] Every hypothesis has an explicit mechanism, not just a predicted sign
- [ ] The driving theory is named and its process clearly invoked (not a one-line citation)
- [ ] Level of analysis is stated and consistent across argument and design
- [ ] Mediators/moderators are theorized a priori with substantive reasons
- [ ] Hypotheses were derived before analyzing the data (no HARKing)
- [ ] A theoretical-model figure matches the hypotheses exactly
- [ ] At least one rival explanation is named and engaged

## Anti-patterns

- **HARKing**: hypothesizing after results are known; reviewers detect it when every hypothesis is supported and none is surprising.
- **Bald predictions**: "We hypothesize A is positively related to B" with no *why*.
- **Borrowed theory**: invoking a famous theory by name without using its actual logic.
- **Mechanism by mediation**: claiming a process exists only because the indirect effect is significant.
- **Kitchen-sink hypotheses**: many predictions, each thinly argued, that no single theory ties together.
- **Boundary without reason**: a moderator with no theoretical account of why the effect should differ.

## Output format

```
【Focal theory】... (process verb: ...)
【H1 (focal effect)】antecedent → mechanism → outcome; direction/form; level
【H2 (mechanism/mediation)】...
【H3+ (boundary/moderation)】... reason the slope changes
【Rival explanation addressed】...
【HARKing check】hypotheses fixed before analysis? yes/no
【Model figure】matches hypotheses one-to-one? yes/no
【Next step】amj-literature-positioning, then amj-methods
```

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 →