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

Ajs Research Design

ASecurity

Use when defending the research design of an American Journal of Sociology (AJS) manuscript on its own methodological terms — quantitative, comparative-historical, ethnographic, network, or formal. AJS judges each kind of work by the standards of its tradition; the design must support the theoretical claim. Defends the design; it does not run the analysis.

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

Security Analysis

A100/100

Scanned 6/4/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Ajs Research Design?

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

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

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

Download with Pro
Files
SKILL.md
---
name: ajs-research-design
description: Use when defending the research design of an American Journal of Sociology (AJS) manuscript on its own methodological terms — quantitative, comparative-historical, ethnographic, network, or formal. AJS judges each kind of work by the standards of its tradition; the design must support the theoretical claim. Defends the design; it does not run the analysis.
---

# Research Design (ajs-research-design)

AJS is method-pluralist: it publishes leading quantitative, **comparative-historical**, ethnographic,
network, and formal work, and it judges each by the standards of *its own tradition*. The job here is
to make the design defensible to a generalist, possibly cross-method, double-blind reviewer — and to
show the design actually supports the theoretical claim from `ajs-theory-building`.

## When to trigger

- Choosing or justifying the design before data collection or analysis
- A reader questioned identification, case selection, sampling, or evidentiary warrant
- Aligning the design with the mechanism and observable implications
- Mixed-methods work that must defend each component on its own terms

## Defend the design (by tradition)

### Quantitative / observational
- State the **estimand** and the **identifying assumptions** plainly; AJS rewards honesty over false
  precision. Where the design is descriptive or associational, say so and theorize accordingly.
- Justify sample, measurement, and model; pre-empt confounding and selection.

### Comparative-historical
- Make **case selection** and the **comparative logic** explicit (most-similar / most-different,
  typical / deviant, scope of the comparison).
- Keep a clear **evidentiary trail** from primary sources to claims; treat sequence and conjuncture as
  evidence, not decoration.

### Ethnographic / interview
- Describe **access, site/case selection, duration, and positionality**; justify why this case bears
  the theoretical weight.
- Make the **link from fieldnotes/transcripts to claims** legible (without exposing informants).

### Network / computational
- Justify **boundary specification, tie definition, and missingness**; match the model (e.g., ERGM,
  SAOM) to the relational question.

### Formal
- Tie assumptions to the substantive setting; specify what empirical patterns would corroborate or
  challenge the model.

## Match design to claim

The single most common AJS reviewer objection: **the design cannot bear the theoretical claim.** Walk
the chain: claim → mechanism → observable implication → the design's leverage on it. If a step is
weak, tighten the claim or strengthen the design — do not overclaim.

## Anti-patterns

- Borrowing a quantitative identification template for work that is interpretive or comparative
- Case selection that quietly guarantees the result (selecting on the outcome without acknowledging it)
- Ethnography that asserts representativeness it cannot support
- Overclaiming causality from an associational design
- A design that tests something adjacent to, but not, the stated theoretical claim

## Output format

```
【Tradition】quantitative / comparative-historical / ethnographic / network / formal / mixed
【Claim it must support】from theory-building
【Design leverage】how this design bears on the claim
【Key assumptions / threats】identification, selection, access, boundary, etc.
【Evidentiary trail】sources → claims is legible? [Y/N]
【Verdict】supports the claim / needs tightening / overclaims (fix)
【Next】ajs-data-analysis
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — design and method tooling by tradition
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — AJS method-pluralism and reviewer-matching policy

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 →