humrel-data-analysis
Use when executing and reporting the analysis for a Human Relations (HR) manuscript — qualitative coding and data-to-theory construction, critical interpretation, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see humrel-methods).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-data-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Data Analysis & Evidence (humrel-data-analysis) ## When to trigger - You have data but the path from data to theory is opaque - Qualitative: quotes are decorative, not evidentiary; coding is undocumented - Critical: the interpretation reads as assertion rather than disciplined reading of the material - Quantitative: main results exist but theorizing stops at the coefficient - A reviewer asks "how did you get from your data to these constructs?" ## The HR bar: make the inference auditable, then theorize beyond it HR judges each tradition on its own terms, but every branch must satisfy the same demand: a reader should be able to *see how the evidence became theory*, and the analysis must yield the "unique and substantive theoretical contribution" the journal screens for. The relational, social nature of work should remain visible in the analysis — not abstracted away into variables or quotations stripped of context. ## Branch A — Qualitative analysis (the data-to-theory ladder) - **Transparent coding.** Document first-order codes (informant terms), second-order themes (your constructs), and aggregate dimensions — a Gioia-style data structure — or an equivalent (Eisenhardt cross-cas
- When to trigger
- The HR bar: make the inference auditable, then theorize beyond it
- Branch A — Qualitative analysis (the data-to-theory ladder)
- Branch B — Critical analysis
- Branch C — Quantitative analysis
- Either branch — the "so what" of the evidence
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Anti-patterns
- Output format
What does the humrel-data-analysis skill do?
Use when executing and reporting the analysis for a Human Relations (HR) manuscript — qualitative coding and data-to-theory construction, critical interpretation, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see humrel-methods).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill humrel-data-analysis --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.