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 Workflow

ASecurity

Use when deciding which smj-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Strategic Management Journal (SMJ) manuscript. Routes — it does not replace — the specialized skills.

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-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Smj Workflow?

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

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

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

Download with Pro
Files
SKILL.md
---
name: smj-workflow
description: Use when deciding which smj-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Strategic Management Journal (SMJ) manuscript. Routes — it does not replace — the specialized skills.
---

# Strategic Management Journal Workflow (smj-workflow)

## Overview

This is the router. It does not do the work of any specialized skill — it tells you **which smj-* skill to use right now** given where your manuscript stands.

Default assumption: unless you say otherwise, the target is the **Strategic Management Journal (SMJ)** — the flagship strategy journal published by Wiley for the Strategic Management Society (SMS), founded 1980 and led by four **Co-Editors** (verify the current roster on the SMS masthead; as of 2026 it includes Benner, Ethiraj, and Gaba). SMJ wants a clear contribution to **strategy theory** (firm performance, competitive advantage) backed by rigorous, identification-aware empirics. It is highly selective (third-party estimates ~7% acceptance — UNVERIFIED), uses **double-blind** review, and requires **two abstracts** (research summary + managerial summary, ≤125 words each), **five keywords**, and **APA** references within a ~40-page budget. Generic "management" framing and unaddressed endogeneity are the two fastest paths to rejection. If the paper's engine is entrepreneurship or internationalization, the SMS siblings **SEJ** or **GSJ** may fit better than SMJ.

## When to trigger

- "What should I do next?" on an SMJ-targeted paper
- You have a draft and need to find the binding constraint
- You keep bouncing between theory, methods, and writing without a plan
- You received SMJ reviewer comments and need to switch into revision mode

## Routing table

| Current symptom                                                        | Next skill                  |
|------------------------------------------------------------------------|-----------------------------|
| Idea is vague; unsure it is a *strategy* question (performance / advantage) | `smj-topic-selection`       |
| Hypotheses are atheoretical or read as "predictions," not theory       | `smj-theory-development`    |
| Lit review is a list; no positioning against the strategy conversation | `smj-literature-positioning`|
| Design unclear: sample, unit of analysis, measures, identification     | `smj-methods`               |
| Performance regression with no endogeneity / reverse-causality fix     | `smj-data-analysis`         |
| Reviewers may ask "so what for strategy?"; contribution is thin        | `smj-contribution-framing`  |
| Too many tables; exhibits not self-contained; no path/effect figure    | `smj-tables-figures`        |
| Prose is jargon-heavy, hedged, or buries the argument                  | `smj-writing-style`         |
| Ready to submit; need preflight (dual abstracts, 5 keywords, APA, format) | `smj-submission`            |
| Want to understand the review timeline / action-editor process         | `smj-review-process`        |
| Received an R&R; need a response strategy and letter                    | `smj-rebuttal`              |

## Default order

1. `smj-topic-selection` — lock the strategy question (performance / competitive advantage)
2. `smj-theory-development` — build the theoretical mechanism and hypotheses
3. `smj-literature-positioning` — position against the live strategy conversation
4. `smj-methods` — sample, unit of analysis, measures, identification design
5. `smj-data-analysis` — estimate, and explicitly defeat endogeneity / selection / reverse causality
6. `smj-contribution-framing` — sharpen the contribution to strategy theory
7. `smj-tables-figures` — finalize self-contained exhibits
8. `smj-writing-style` — full-draft polish (do this late)
9. `smj-submission` — preflight (dual abstracts, 5 keywords, APA, page budget, anonymization)
10. `smj-review-process` — understand what happens after submission (Co-Editor screen → action editor)
11. `smj-rebuttal` — after the R&R decision

> `smj-writing-style` is a **late-stage polish**. Do not polish prose while the identification strategy or the theoretical contribution is still unsettled.

## Decision heuristics

- "I have data but no strategy story" → `smj-topic-selection`
- "My hypotheses are just signed correlations" → `smj-theory-development`
- "My intro never names whose conversation I'm joining" → `smj-literature-positioning`
- "My DV is firm performance and my X is a strategic choice" → `smj-data-analysis` (selection into the choice is the #1 threat)
- "A reviewer could say 'this is management, not strategy'" → `smj-contribution-framing`
- "I have nine tables" → `smj-tables-figures`
- "I submit tomorrow" → `smj-submission`
- "I got a Major Revision" → `smj-review-process` then `smj-rebuttal`

## Differences vs. AMJ / ASQ / AMR stacks

If the paper's center of gravity is general organizational behavior, HRM, or micro-OB, the [Academy of Management Journal](https://github.com/brycewang-stanford/amj-skills) stack fits better. If the contribution is purely conceptual with no data, use an [AMR](https://github.com/brycewang-stanford/amr-skills) theory-only stack. SMJ's distinctive bar: the dependent construct should connect to **firm performance or competitive advantage**, and the empirics must survive an **endogeneity** interrogation.

## Anti-patterns

- **Do not** skip `smj-theory-development` and jump to estimation — SMJ reviewers read theory first.
- **Do not** let `smj-tables-figures` polish exhibits before the identification strategy holds.
- **Do not** let `smj-rebuttal` draft a response letter before you have actually revised the manuscript.
- **Do not** treat this as a generic management workflow; every stage must reconnect to strategy.
- **Do not** forget SMJ's dual-abstract / 5-keyword / APA requirements until submission day, or route an SEJ/GSJ-shaped paper to SMJ.

## Templates & resources

- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SMJ scope, Co-Editors, dual-abstract/keyword/reference rules, and the SMS journal family
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — strategy data sources and analysis packages across the pipeline

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 →