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

Smj Theory Development

ASecurity

Use when building the theoretical mechanism and hypotheses for a Strategic Management Journal (SMJ) manuscript. Constructs the argument and develops hypotheses; it does not position the literature or run estimation.

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsgogitperformance

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Smj Theory Development?

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

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

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

Download with Pro
Files
SKILL.md
---
name: smj-theory-development
description: Use when building the theoretical mechanism and hypotheses for a Strategic Management Journal (SMJ) manuscript. Constructs the argument and develops hypotheses; it does not position the literature or run estimation.
---

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

## When to trigger

- Your hypotheses read as signed predictions ("X is positively related to Y") with no logical engine
- The theory section restates prior findings instead of building a new argument
- A moderator is added but you cannot explain *why* it changes the effect
- The mechanism connecting strategic choice to performance is implicit or hand-waved

## What SMJ means by "theory"

SMJ wants a **causal logic**: a chain of premises that explains *why* a strategic choice or condition produces a performance/advantage consequence, anchored in a recognized strategy perspective. A hypothesis without a stated mechanism is a correlation in disguise. The reviewers expect you to show the logical steps, not just the conclusion.

## Choosing and combining lenses

| Lens                          | Core engine                                            | Typical use |
|-------------------------------|--------------------------------------------------------|-------------|
| Resource-based / capabilities | Heterogeneous, hard-to-imitate resources earn rents (Wernerfelt, 1984, SMJ) | Why advantage persists |
| Dynamic capabilities          | Sensing/seizing/reconfiguring under change (Teece, Pisano & Shuen, 1997, SMJ) | Adaptation, renewal |
| Transaction cost economics    | Governance minimizes contracting hazards               | Make-vs-buy, alliances, scope |
| Agency / governance           | Incentive misalignment shapes strategic choice         | Boards, ownership, M&A |
| Competitive dynamics          | Action–response, awareness–motivation–capability       | Rivalry, market entry |
| Behavioral theory of the firm | Aspirations, search, attention                         | Risk taking, R&D search |
| Real options                  | Sequential investment under uncertainty                | Entry, staging, divestiture |
| Institutional / nonmarket     | Legitimacy and regulatory environment shape advantage  | CSR, political strategy |

Borrowing a lens is fine; **extending or qualifying** it is what earns a contribution. State which lens you build on and exactly where you depart from it.

> Anchor RBV with **Wernerfelt (1984), SMJ** when you want an SMJ-internal reference. Barney's much-cited 1991 RBV statement appeared in *Journal of Management*, **not** SMJ — do not list it as an SMJ landmark.

SMJ is a **theory-develop-and/or-test** journal: unlike AMR, it does not publish purely conceptual papers, so your theory must set up implications that are evaluable (testable, or otherwise assessable for qualitative/formal work).

## Building the argument (mechanism-first)

1. **Establish the baseline relationship.** State the focal X → Y and the strategy logic for its sign.
2. **Specify the mechanism.** Name the mediating process (e.g., reduced imitation, lower coordination cost, shifted aspirations). The mechanism is the contribution's spine.
3. **Develop moderators as theory, not robustness.** A moderator hypothesis must explain how the boundary condition *strengthens or reverses the mechanism* — not merely "the effect is bigger for big firms."
4. **Surface and address the tension.** SMJ rewards arguments that resolve a real tension or counter-prediction (e.g., a resource that both enables and constrains).
5. **State the counterfactual and scope conditions.** Where does the logic hold, and where does it break?

## Hypothesis craft

- Each H states direction *and* carries a one-line mechanism in the surrounding text.
- Order hypotheses so the baseline (H1) precedes mediation/moderation (H2, H3…).
- Avoid "kitchen-sink" hypothesizing; 2–4 tightly linked hypotheses beat seven loose ones.
- If you theorize a mediator, plan a mechanism test in `smj-data-analysis` (mediation alone is weak evidence).

## Checklist

- [ ] Every hypothesis is preceded by an explicit causal mechanism
- [ ] You name the lens you extend and the specific gap/tension you resolve
- [ ] Moderators are theorized (why the mechanism shifts), not bolted on
- [ ] A counter-argument / competing prediction is acknowledged and addressed
- [ ] Scope and boundary conditions are stated
- [ ] The argument predicts something a reader could not already infer from prior work

## Anti-patterns

- "X is positively associated with Y" with no mechanism — the most common SMJ theory weakness
- Hypothesis salad: many predictions, no integrating logic
- Re-deriving an established result and calling it theory
- A moderator with no theoretical reason for changing the effect
- Mechanism claimed in theory but never tested empirically
- Using a strategy lens as decoration while the real argument is generic

## Output format

```
【Lens】RBV | dynamic capabilities | TCE | agency | competitive dynamics | BTOF | real options | institutional
【Gap/tension resolved】...
【Mechanism (one sentence)】X affects Y because ...
【Hypotheses】H1 (baseline) / H2 (mediation) / H3 (moderation) — each with its mechanism
【Boundary conditions】...
【Empirical implication】mechanism test needed → flag for smj-data-analysis
【Next step】smj-literature-positioning
```

## Templates & resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SMJ scope and verified landmark strategy-theory papers (Wernerfelt 1984; Teece, Pisano & Shuen 1997)

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 →