Agent skill · Content & Marketing

e1

E1-Quantitative Analysis Guide with Code Generation & Sensitivity Analysis VS-Enhanced with Full 5-Phase process: Avoids obvious analyses, explores innovative methodologies Expanded to include qualitative analysis (thematic, grounded theory, content, narrative) Absorbed E4 (Analysis Code Generator) and E5 (Sensitivity Analysis - Primary Study) capabilities Use when: selecting statistical/qualitative methods, interpreting results, checking assumptions, generating code, sensitivity analysis thematic analysis, grounded theory, content analysis, narrative analysis, NVivo, ATLAS.ti, coding, quali

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeNOASSERTION
Install
npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill e1 --agent claude-code

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

Facts
Files in the skill folder: 1
SKILL.md size: 36 KB
Bundled scripts: none
Version: 12.0.1
Path: skills/25-HosungYou-Diverga/skills/e1/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 3,244
Language: Stata
Read our review of the source →

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

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill provides a comprehensive guide for both quantitative and qualitative analysis, applying a VS-Research 5-Phase process to recommend diverse methodologies beyond routine tests. It includes phases for context collection, method identification, long-tail sampling, execution guidance, and suitability verification, with explicit procedures, checks, and code templates for quantitative analysis. It also adds qualitative analysis support (thematic analysis, grounded theory, content, narrative) and ties in software tools (NVivo, ATLAS.ti, MAXQDA, Dedoose) and coding practices. It absorbs capabilities related to generating analysis code and conducting sensitivity analyses, and references programming in R, Python, SPSS syntax, and relevant workflows.

How it works

  • Phase 0 collects mandatory context data before applying methods (research_question, independent_variable, dependent_variable, design; optional controls, sample size, target journal).
  • Phase 1 identifies the modal analysis method commonly used for the design and then prompts to confirm optimality and consider alternatives.
  • Phase 2 presents three direction levels (A, B, C) with increasing methodological novelty and aligns method suggestions to journal type or research aims.
  • Phase 3 selects a low-typicality method based on statistical fit, research question alignment, feasibility, and contribution potential.
  • Phase 4 provides execution guidance: describe primary method, assumptions, power analysis, and provide or reference code blocks for R or Python; includes effect size calculations and reporting format.
  • Phase 5 verifies suitability, ensuring the chosen method is justified and robust, with quality checks and assumption procedures.
  • The skill also covers qualitative analysis methods (Thematic Analysis, Grounded Theory) with structured phases for coding, theme development, and reporting, plus software options and coding approaches.

When to use it

Use when selecting statistical/qualitative methods, interpreting results, checking assumptions, generating code, and conducting sensitivity analysis. Triggers include statistical tests (ANOVA, regression, t-test, power analysis) and qualitative workflows (thematic analysis, grounded theory, content, narrative).

What it can touch

Affects methods and tools for quantitative analysis including R code, Python code, SPSS syntax, and accompanying code blocks. It references software and coding workflows, and provides templates for analysis code and reporting.

Caveats

Prerequisites must approve with diverga_check_prerequisites("e1"); if not approved, it prompts for missing checkpoints. The skill version is 12.0.1 and uses Claude-code as the declared tool. It emphasizes not overpromising outcomes and sticks to stated procedures and checks.

From the SKILL.md

## ⛔ Prerequisites (v8.2 — MCP Enforcement) `diverga_check_prerequisites("e1")` → must return `approved: true` If not approved → AskUserQuestion for each missing checkpoint (see `.claude/references/checkpoint-templates.md`) ### Checkpoints During Execution - 🟠 CP_ANALYSIS_PLAN → `diverga_mark_checkpoint("CP_ANALYSIS_PLAN", decision, rationale)` ### Fallback (MCP unavailable) Read `.research/decis

More from Auto-Empirical-Research-Skills
All skills →
About this skill
What does the e1 skill do?

E1-Quantitative Analysis Guide with Code Generation & Sensitivity Analysis VS-Enhanced with Full 5-Phase process: Avoids obvious analyses, explores innovative methodologies Expanded to include qualitative analysis (thematic, grounded theory, content, narrative) Absorbed E4 (Analysis Code Generator) and E5 (Sensitivity Analysis - Primary Study) capabilities Use when: selecting statistical/qualitative methods, interpreting results, checking assumptions, generating code, sensitivity analysis thematic analysis, grounded theory, content analysis, narrative analysis, NVivo, ATLAS.ti, coding, quali

How do I install it?

Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill e1 --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/Auto-Empirical-Research-Skills, a repository with 3,244 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