Individual skill
orgstud-data-analysis
Use when executing and reporting the analysis for an Organization Studies (OS) manuscript — qualitative coding and the data-to-theory ladder, process analysis, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see orgstud-methods).
Organization-Studies-Skills/skills/orgstud-data-analysis/SKILL.md
Source commit 932eb23331721b16e967c59f093781be1928b498
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,404
- Repository last updated
- Sep 27, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- academic-writing Repository topic
- agent-skills Repository topic
- journal Repository topic
- academic-research Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- awesome-list Repository topic
- claude Repository topic
- claude-code Repository topic
- economics Repository topic
- engineering Derived category
- design Derived category
- operations Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,552 bytes
Read excerpt
# Data Analysis & Evidence (orgstud-data-analysis)
## When to trigger
- You have data but the path from raw material to theory is opaque
- Qualitative: your quotes are decorative, not evidentiary; the coding is undocumented
- Process: you have events but no visible analytic structure turning them into a model
- Quantitative: main results exist but robustness and alternative explanations are thin
- A reviewer asks "how did you get from your data to these constructs?"
## OS expects readers to *see* how data became theory
OS's interpretive, European tradition makes **analytic transparency** a first-class criterion — qualitative rigor is judged on its own terms, not against a quantitative yardstick. The reader must be able to *audit the inference* from raw data to theoretical claim. Make the analytic ladder visible.
