Individual skill

orgsci-data-analysis

Use when analyzing and reporting results for an Organization Science manuscript across its eclectic methods — establishing trustworthiness for qualitative work, the right estimator for quantitative/multilevel data, transparency for simulation/formal models, and mechanism-supported inference where causal identification is impossible. Executes and reports the analysis; it does not design the study (orgsci-methods) or frame the contribution (orgsci-contribution-framing).

Organization-Science-Skills/skills/orgsci-data-analysis/SKILL.md

Read pinned source

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,405
Repository last updated
Sep 27, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Data Analysis & Transparency (orgsci-data-analysis)

## When to trigger

- Data are collected (or a model built) and it is time to analyze and report
- A reviewer says "the analysis does not support the inference"
- You are unsure how to demonstrate rigor for qualitative, computational, or formal work
- Your estimator may not match your design (nested, time-to-event, latent constructs)

## Rigor is method-specific — report what your design demands

Because Organization Science is methodologically eclectic, "rigor" looks different by method. Report the standard that fits, transparently.

- **Qualitative / inductive.** Validity becomes **trustworthiness**: a data structure (first-order codes → second-order themes → aggregate dimensions), an audit trail, and representative quotations so the path from raw data to constructs is traceable; state case-selection logic, saturation, and how disconfirming evidence was handled.
Back to top