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 Methods

ASecurity

Use when choosing and defending the research design for a Journal of Marketing (JM) manuscript — matching a "big tent" method (experiment, field study, survey, secondary data, qualitative) to a substantive marketing question, with field realism and identification in mind. Designs the study; it does not run the estimation (jm-data-analysis) or frame the contribution (jm-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jm Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: jm-methods
description: Use when choosing and defending the research design for a Journal of Marketing (JM) manuscript — matching a "big tent" method (experiment, field study, survey, secondary data, qualitative) to a substantive marketing question, with field realism and identification in mind. Designs the study; it does not run the estimation (jm-data-analysis) or frame the contribution (jm-contribution-framing).
---

# Research Design, Big-Tent (jm-methods)

## When to trigger

- The question is set and you must choose a design that can actually answer it
- A reviewer will ask whether the method supports a *causal* or *managerial* claim
- You are deciding between a clean lab experiment and a messier but realer field study
- You have secondary (scanner/CRM/financial) data and need an identification strategy

## JM's "big tent" — let the question pick the method

JM is methodologically pluralistic: it welcomes **primary data** (experiments, field studies, surveys, interviews, observational data) and **secondary data**, and champions **empirics-first** research grounded in real-world phenomena. No single method is privileged. The design rule at JM is therefore: choose the method that most credibly answers a **substantive** question and supports a **managerially relevant** claim — not the most sophisticated technique. Work centered on mathematical/statistical methods for their own sake is out of scope (route to Marketing Science / JMR); methods here are **servants** of the substantive insight.

## Match design to claim

| Substantive claim / data situation                          | Design                                                      |
|-------------------------------------------------------------|-------------------------------------------------------------|
| Causal effect of a marketing action on consumer response    | Randomized experiment (lab or online panel)                 |
| Causal effect *in a real market* with realism/external validity | Randomized **field experiment** with a firm/platform     |
| Process / mechanism (why an effect occurs)                  | Experiment with mediation + moderation-of-process designs   |
| Preferences, trade-offs, willingness-to-pay                 | Survey / choice-based conjoint / discrete-choice experiment |
| Market-level dynamics from observational data               | Panel with FE; DiD / event study; synthetic control; IV     |
| Customer-base behavior (CLV, churn, response)               | Longitudinal CRM/transaction modeling                       |
| Meaning, emergent constructs, theory-building from practice | Qualitative (interviews, ethnography, archival text)        |

Combine methods (multi-study or mixed) when one design cannot establish both *internal validity* (the effect is real) and *external/managerial validity* (it matters in the market).

## Field realism and managerial validity

JM prizes evidence that travels to real decisions. Strengthen the design by: securing a **field setting or firm partner** where feasible; choosing **outcomes managers act on** (sales, CLV, conversion, welfare) over proxy attitudes alone; sampling a population the claim should generalize to; and documenting the real-world stimulus, market, and time frame so a practitioner recognizes the setting.

## Design for transparency up front

JM requires a replication packet at conditional acceptance and **encourages preregistration**. Build this in now: preregister experiments (you will later supply anonymized links and an attestation), version-control analysis scripts, and log sample-construction and exclusion rules as you go — not retroactively.

## Checklist

- [ ] Method chosen to fit the substantive claim, not for sophistication
- [ ] Internal validity (randomization/identification) addressed
- [ ] External/managerial validity (field realism, actionable outcomes) addressed
- [ ] Multi-study / mixed design where one method cannot do both
- [ ] Outcomes managers/policy makers care about are measured
- [ ] Preregistration planned (experiments); scripts and exclusion rules logged
- [ ] Power/sample-size justified a priori for experiments

## Anti-patterns

- **Method-driven paper**: a clever estimator in search of a question (out of scope at JM).
- **Lab-only causal claim** asserted to hold in the market with no field/external evidence.
- **Endogenous treatment** in secondary data with no identification strategy.
- **Attitude proxies** standing in for outcomes managers actually move.
- **Retrofitted transparency**: no preregistration, exclusions documented after the fact.

## Output format

```
【Substantive claim】[...]
【Design】experiment / field experiment / survey-conjoint / panel-DiD / qualitative / mixed
【Internal validity】randomization / identification: [...]
【External & managerial validity】field realism, actionable outcomes: [...]
【Multi-study plan】[...]
【Transparency】preregistration + script/exclusion logging: [...]
【Next step】jm-data-analysis
```

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 →