Agent skill · Design & Presentation

jpart-research-design

Use when defending the research design of a Journal of Public Administration Research and Theory (JPART) manuscript — survey/lab/field experiments on public employees and citizens, causal observational designs, multilevel structures, or mixed methods. JPART has moved strongly toward experimental and causal identification. Strengthens the design; it does not write code.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-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: 8 KB
Bundled scripts: none
Path: Journal-of-Public-Administration-Research-and-Theory-Skills/skills/jpart-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 (jpart-research-design) JPART has moved toward **experimental and causal** identification, and reviewers expect the design to connect the theory (`jpart-theory-building`) to evidence credibly. This skill is mode-aware: pick the section that matches your work and defend it against the strongest alternative explanation a public-management reviewer will raise. ## When to trigger - Specifying identification, an experiment, sampling, or measurement - A reviewer questioned causal claims, common-method bias, endogeneity, or external validity - Preparing a **pre-analysis plan** / preregistration (JPART accepts blinded pre-reg reports) - Justifying why the design adjudicates the rival account from `jpart-literature-positioning` ## Design-choice gate Start by matching the theoretical claim to the minimum credible design. Do not choose the design by data availability alone. | Claim type | Minimum design burden | Common downgrade | |------------|-----------------------|------------------| | "X causes Y in public organizations" | Identification strategy with an estimand, assignment/variation story, and falsification or sensitivity evidence | Reframe as association or theory-bu

What's inside
Steps it walks through
  1. When to trigger
  2. Design-choice gate
  3. Experiments (the modern JPART workhorse)
  4. Observational / causal
  5. Multilevel / organizational
  6. Mixed methods
  7. The adjudication test (JPART-specific)
  8. Reviewer stress tests
  9. Execution bridge (StatsPAI / Stata MCP)
  10. Anti-patterns
  11. Output format
  12. Supplementary resources
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jpart-research-design skill do?

Use when defending the research design of a Journal of Public Administration Research and Theory (JPART) manuscript — survey/lab/field experiments on public employees and citizens, causal observational designs, multilevel structures, or mixed methods. JPART has moved strongly toward experimental and causal identification. Strengthens the design; it does not write code.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jpart-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