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 Methods

ASecurity

Use when the research design and method are the bottleneck for an Academy of Management Journal (AMJ) manuscript — matching design (archival, survey, experiment, multi-method, field) and level of analysis to the theoretical question. Designs the study; it does not run the estimation or validity checks (amj-data-analysis).

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Amj Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: amj-methods
description: Use when the research design and method are the bottleneck for an Academy of Management Journal (AMJ) manuscript — matching design (archival, survey, experiment, multi-method, field) and level of analysis to the theoretical question. Designs the study; it does not run the estimation or validity checks (amj-data-analysis).
---

# Research Design & Methods (amj-methods)

## When to trigger

- The design may not match the theory's level, timing, or causal claim
- Data are single-source, single-wave, and self-reported (common-method bias risk)
- The theory is causal but the design is cross-sectional/correlational
- Constructs lack established, validated measures
- A reviewer says "the design cannot test this hypothesis" or "endogeneity is unaddressed"

## Match the design to the question

AMJ explicitly welcomes **all empirical methods** — qualitative, quantitative, field, laboratory, meta-analytic, and mixed. The bar is *fit and rigor*, not a single preferred method, and qualitative designs are held to an equally demanding standard (the Eisenhardt multiple-case approach and the Gioia methodology for grounded qualitative rigor are the field's reference points).

| Theoretical claim                          | Design that earns it                                     |
|--------------------------------------------|----------------------------------------------------------|
| Causal effect of a manipulable cause       | Experiment (lab/field/online), or natural experiment     |
| Process unfolding over time                | Multi-wave panel; longitudinal/lagged design             |
| Firm/strategy outcomes from archival cause | Panel archival with fixed effects + endogeneity strategy |
| Cross-level mechanism (e.g., team→indiv.)  | Multilevel/nested data with HLM-appropriate structure    |
| Rich, novel, or contested phenomenon       | Qualitative or multi-method (often paired with a study 2)|

A two-study design (e.g., field study for generalizability + experiment for causal mechanism) is a common AMJ strength — it answers both internal and external validity.

## Designing against the threats AMJ cares about

- **Common-method bias (CMB)**: separate sources for predictor and outcome; temporal separation across waves; objective/archival outcomes where possible. Procedural remedies beat statistical fixes (the Podsakoff et al. guidance is the standard reference). Plan this *before* collecting data.
- **Endogeneity (archival)**: anticipate omitted variables, reverse causality, and selection. Plan an identification strategy (instrument, natural experiment, panel fixed effects, difference-in-differences, Heckman/2SLS, propensity matching) and the assumptions each requires.
- **Measurement**: use validated multi-item scales; pilot new measures; plan a CFA. State the level at which each construct is measured and how cross-level data are aggregated (with justification: ICC, r_wg, aggregation theory).
- **Sampling and power**: justify the sampling frame, response rate, and statistical power for the focal and interaction effects (interactions need more power).

## Level-of-analysis discipline

State the level for theory, measurement, and analysis, and keep them aligned. If theory is at the team level but data are individual, justify aggregation; if effects are cross-level, the analysis must model the nesting (do not run OLS on nested data).

## Checklist

- [ ] Design can actually test each hypothesis (causal claims have causal leverage)
- [ ] CMB addressed by procedural design (separate sources/time), not just a post-hoc test
- [ ] Endogeneity strategy specified for archival/observational causal claims
- [ ] Constructs use validated measures; new measures piloted; CFA planned
- [ ] Level of analysis consistent across theory, measurement, and analysis; aggregation justified
- [ ] Sampling frame, response rate, and power (including for interactions) justified
- [ ] Where feasible, a second study triangulates the causal mechanism

## Anti-patterns

- **Cross-sectional causal claims**: "X causes Y" from one-wave correlational data.
- **CMB as afterthought**: relying solely on a Harman single-factor test instead of designed separation.
- **Ignored endogeneity**: archival "effect" with an obviously endogenous regressor and no strategy.
- **Mismatched levels**: theorizing at the team level, testing with disaggregated individual data via OLS.
- **Unvalidated home-grown scales** with no evidence of reliability or construct validity.
- **Underpowered interactions** presented as null "boundary conditions."

## Output format

```
【Design】experiment / panel-archival / multilevel survey / qualitative / multi-method
【Hypothesis-design fit】each H testable? notes ...
【CMB plan】procedural remedies ...
【Endogeneity strategy】(if archival) instrument / NE / FE / DiD / matching ...
【Measures】validated? new (piloted)? CFA planned?
【Levels】theory / measurement / analysis aligned? aggregation justification ...
【Power & sampling】frame, N, power for interactions ...
【Next step】amj-data-analysis
```

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 →