Use when deciding whether a project clears the Sociological Methods & Research (SMR) bar — a genuine methodological contribution (develop, evaluate, or critically assess a method), not an application dressed as method. Screens fit and scope; does not derive properties or design simulations.
Scanned 9/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill smr-topic-selection --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Smr Topic Selection?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-smr-topic-selection)More formats (shields.io, HTML) on the badges page.
---
name: smr-topic-selection
description: Use when deciding whether a project clears the Sociological Methods & Research (SMR) bar — a genuine methodological contribution (develop, evaluate, or critically assess a method), not an application dressed as method. Screens fit and scope; does not derive properties or design simulations.
---
# SMR Topic Selection
Use this first. SMR's single hardest gate is the difference between **a paper about a method** and
**a paper that uses a method**. Most desk rejections at this venue are scope failures: a competent
applied analysis with no methodological payoff for other researchers.
## The three SMR contribution modes
A submission must clearly be one (or more) of these — name yours before drafting:
- **Develop**: a new estimator, design, diagnostic, identification result, or computational tool that
did not exist or could not be used before. The deliverable is a *method other people can adopt*.
- **Evaluate**: a systematic Monte Carlo or analytical comparison that tells the field *when an
existing method works, fails, or should be replaced* — the "often trusted but never properly tested"
paper. The deliverable is *evidence that changes practice*.
- **Critically assess**: a rigorous critique that exposes a hidden assumption, a common misuse, or a
misconception, and gives a corrected procedure. The deliverable is *a fix, not just a complaint*.
If you cannot place the paper in one mode in a single sentence, it is not yet an SMR paper.
## The application test (the desk-reject filter)
Ask: **could this finding appear in a substantive sociology journal (ASR/AJS) instead?** If the
contribution is the substantive result and the method is the vehicle, send it there. SMR wants the
*method* to be the result and the substantive case to be the *illustration*. Diagnostic questions:
- Strip the dataset. Is there anything left for a methods reader to take away? If no → application.
- Would a researcher in a *different* substantive field benefit? SMR methods should travel.
- Is the comparison set other *methods*, or other *findings*? Methods papers compare methods.
## Scope map for SMR
| Project shape | SMR verdict | Why |
|---|---|---|
| New estimator/diagnostic with derivation + simulation + illustration | In scope | Canonical "develop" paper |
| Monte Carlo evaluation of a widely-used method's failure modes | In scope | Canonical "evaluate" paper |
| Critique exposing a misused assumption + corrected procedure | In scope | Canonical "assess" paper |
| Strong substantive finding using a standard method | Out of scope | Belongs in ASR/AJS |
| New method with no real-data illustration | Repair first | SMR expects substantive relevance |
| Software/package note with no methodological novelty | Out of scope (or a software journal) | No method contribution |
## Sibling-journal routing (do not waste a submission)
- *Sociological Methodology* (ASA annual): longer, often more exploratory or programmatic methods
pieces — a different cadence and editorial model. Confirm fit before assuming overlap.
- *Psychological Methods* (APA): psychology-facing measurement/statistics audience.
- *Political Analysis*: political-science methods. SMR is the **SAGE quantitative-sociology-methods**
venue; if your audience is sociologists and social scientists broadly, SMR fits.
## Checklist
- [ ] The contribution mode (develop / evaluate / assess) is named in one sentence.
- [ ] The "what problem does it solve vs. existing methods" sentence is written.
- [ ] The application test is passed: stripping the dataset leaves a method takeaway.
- [ ] The method travels beyond one substantive field.
- [ ] A real-data illustration is planned, not just a simulation.
- [ ] The right sibling journal has been ruled out deliberately.
## Anti-patterns
- **Application in methods clothing**: the real contribution is the substantive finding; reviewers
redirect it to a substantive journal.
- **Method with no users**: an estimator so narrow no one outside the example would run it.
- **Simulation-only novelty**: a new method shown only in Monte Carlo, with no demonstration that it
changes a real substantive conclusion.
- **"Yet another fit index" without a failure case**: a variant whose advantage over the incumbent is
never demonstrated where the incumbent breaks.
## Output format
```text
[SMR fit] in scope / repair first / out of scope
[Contribution mode] develop / evaluate / critically assess
[Problem solved vs. existing methods] <one sentence>
[Application-test result] pass / fail (where it leaks to a substantive finding)
[Next SMR skill] smr-method-contribution
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!