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

Jm Theory Development

ASecurity

Use when building the conceptual logic for a Journal of Marketing (JM) manuscript — grounding theory in a real-world marketing phenomenon, deriving predictions, and accommodating an empirics-first route. Builds the argument; it does not select the question (jm-topic-selection) or run the analysis (jm-data-analysis).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jm Theory Development?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jm-theory-development
description: Use when building the conceptual logic for a Journal of Marketing (JM) manuscript — grounding theory in a real-world marketing phenomenon, deriving predictions, and accommodating an empirics-first route. Builds the argument; it does not select the question (jm-topic-selection) or run the analysis (jm-data-analysis).
---

# Theory Development, Phenomenon-First (jm-theory-development)

## When to trigger

- The phenomenon and question are set; you need a defensible conceptual argument
- Reviewers will ask "why does this happen?" and "what is the mechanism?"
- You have a strong empirical pattern but no organizing logic (empirics-first)
- You are tempted to bolt a generic theory onto a marketing finding

## JM's theory stance: serve the substantive question

Unlike theory-first flagships, JM does not reward theoretical machinery for its own sake. Its bar is **substantive insight into a real marketing question**. Theory in a JM paper earns its place by **explaining a consequential marketing phenomenon** and yielding predictions that, when tested, change how managers, policy makers, or society understand the market. The new editorial "Big Ideas" platform explicitly pushes back on complexity that crowds out topic importance (待核实 — editorial paywalled), so build the *minimum sufficient* conceptual structure that makes the phenomenon intelligible and the predictions sharp.

## Two legitimate routes into JM

1. **Theory-first**: a clear mechanism generates predictions, then data test them. Standard, accepted.
2. **Empirics-first**: a robust, surprising real-world pattern leads, and the conceptual account is developed to explain *why* it occurs. JM actively solicits empirics-first work (dedicated special issue and editorials) grounded in real-world phenomena. This is encouraged here in a way that is unusual among top journals — but the pattern must still be explained, not merely reported.

Decide which route you are on and signal it honestly; do not disguise an empirics-first paper as theory-first (a HARKing risk).

## Build the conceptual logic

- **Anchor in the phenomenon**: state the marketing fact the theory must explain (e.g., why a pricing, advertising, channel, or brand move produces an unexpected market response).
- **Specify the mechanism**: the process linking marketing action/condition to the consequential outcome. Name boundary conditions (when it holds, when it reverses).
- **Derive predictions** at the level you can measure (consumer, segment, brand, firm, market) and that map to outcomes managers/policy makers care about.
- **Moderation/mediation**: predict the *process* and the *contingencies*, not just a main effect, so the substantive story is mechanism-rich.
- **Managerial logic**: carry the implication through — if the mechanism holds, what should a decision maker do differently?

## Checklist

- [ ] The phenomenon the theory must explain is stated explicitly
- [ ] Route declared (theory-first vs. empirics-first) and handled honestly
- [ ] Mechanism named, with boundary conditions
- [ ] Predictions at a measurable level, tied to consequential outcomes
- [ ] Moderators/mediators predicted, not just a main effect
- [ ] Managerial/policy/societal implication of the mechanism articulated
- [ ] Conceptual structure is as simple as the substantive insight allows

## Anti-patterns

- **Theory theater**: elaborate framework that adds no substantive insight.
- **HARKing**: presenting post-hoc explanations of an empirics-first pattern as a priori theory.
- **Main-effect-only logic**: no mechanism, no contingencies.
- **Borrowed-theory veneer**: a generic psychological/economic theory pasted on without fit to the marketing phenomenon.
- **Mechanism with no managerial consequence**: process that no decision maker can act on.

## Output format

```
【Phenomenon to explain】[...]
【Route】theory-first / empirics-first (declared honestly)
【Mechanism】[...]; boundary conditions: [...]
【Predictions】H1...Hk at level [...] → outcome [...]
【Process / contingencies】mediators: [...]; moderators: [...]
【Managerial logic】if mechanism holds → decision maker should [...]
【Next step】jm-literature-positioning
```

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 →