Agent skill · Data & Analytics

spq-research-design

Use when defending the research design of a Social Psychology Quarterly (SPQ) manuscript — laboratory and survey experiments (group processes, status), survey and secondary-data analysis (social structure and personality), or observation/ethnography and interviews (symbolic interaction). SPQ judges each tradition on its own terms but always asks how the design captures the link between structure and the individual. Strengthens the design; it does not write code.

brycew6m4,252★ · +31/wk · 3 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill spq-research-design --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 6 KB
Bundled scripts: none
Path: Social-Psychology-Quarterly-Skills/skills/spq-research-design/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Research Design (spq-research-design) SPQ accepts experiments, surveys, and observational/interpretive work, but is demanding about each. The design must credibly connect the social-psychological argument (`spq-theory-building`) to evidence about the **structure–individual link**. This skill is tradition-aware: pick the section that matches your work and defend it against the strongest alternative explanation. ## When to trigger - Specifying an experimental setting, a survey/measurement plan, or a fieldwork/interview design - A reviewer questioned causal claims, construct validity, case/site selection, or a confound - Justifying why your design adjudicates the rival account from `spq-literature-positioning` - Deciding how the design operationalizes the social-psychological mechanism ## Experimental (group processes, status, exchange — the lab tradition) - **Standardized experimental settings.** State the setting (e.g., status/expectation-states paradigm, exchange networks) and how the manipulation realizes the theoretical construct. - **Manipulation / standardized-setting checks**; randomization; attention checks; attrition. - **Inference**: pre-specify primary outcomes; correct

What's inside
Steps it walks through
  1. When to trigger
  2. Experimental (group processes, status, exchange — the lab tradition)
  3. Survey / secondary-data (social structure and personality)
  4. Observational / interpretive (symbolic interaction)
  5. The adjudication test (SPQ-specific)
  6. Design stress ledger
  7. Execution bridge (StatsPAI / Stata MCP)
  8. Anti-patterns
  9. Output format
  10. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the spq-research-design skill do?

Use when defending the research design of a Social Psychology Quarterly (SPQ) manuscript — laboratory and survey experiments (group processes, status), survey and secondary-data analysis (social structure and personality), or observation/ethnography and interviews (symbolic interaction). SPQ judges each tradition on its own terms but always asks how the design captures the link between structure and the individual. Strengthens the design; it does not write code.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill spq-research-design --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going