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

Spq Research Design

ASecurity

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.

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

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill spq-research-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spq Research Design?

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

Security grade badge for Spq Research Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-spq-research-design/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-spq-research-design)

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

Download with Pro
Files
SKILL.md
---
name: spq-research-design
description: 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.
---

# 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 for multiple comparisons; power/MDE; appropriate
  models for nested (group/dyad) data.
- **Generalization**: be explicit about what a lab effect does and does not license about real settings.

## Survey / secondary-data (social structure and personality)
- **Measurement first.** Validate the social-psychological constructs (identity salience, mastery,
  status, sentiment); report reliability; show results aren't an artifact of a scaling choice.
- **Structural variables** measured and theorized, not just controls — the structure–individual link is
  the point.
- **Inference for complex designs**: survey weights/clustering for GSS/PSID-type data; multilevel models
  for individuals nested in contexts; sensitivity to unobserved confounding for any causal claim.

## Observational / interpretive (symbolic interaction)
- **Site / case selection** justified by analytic logic (what is this a case *of*?), not convenience.
- **Evidence and disconfirmation**: state what observations would have **challenged** the analytic claim;
  document how interaction, accounts, or fieldnotes support it.
- **Reflexivity and access**: position of the researcher, consent, and how meaning is interpreted.

## The adjudication test (SPQ-specific)

For the **single strongest rival explanation**, write one sentence: *"If the rival were true rather than
my argument, the data would look like ___; instead they look like ___."* For experiments this is the
manipulation contrast; for surveys, the confound ruled out; for interpretive work, the alternative
reading. If you cannot, the design does not yet identify the contribution.

## Anti-patterns

- A lab effect over-generalized to real-world structure with no caveat
- Treating structural variables as nuisance controls rather than theorized causes
- Convenience site selection dressed up as theory-driven
- "Causal" language on a cross-sectional survey that only supports association
- A design that cannot distinguish your social-psychological mechanism from the leading alternative

## Output format

```
【Tradition】experiment / survey-SSP / observation-interpretive
【Estimand or analytic claim】what is identified/shown about the structure–individual link
【Key assumption(s)】and how each is defended
【Rival ruled out】the adjudication sentence
【Measurement / setting validity】constructs validated or setting standardized? [Y/N]
【Robustness/sensitivity】planned checks
【Next】spq-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — experimental, survey, measurement, and CAQDAS tooling by tradition
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — SPQ scope and methods breadth

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 →