Skip to content
cccskills
FreePublished on GitHub

asq-data-analysis

Use when executing and reporting the analysis for an Administrative Science Quarterly (ASQ) manuscript — qualitative coding and data-to-theory construction, or quantitative estimation and robustness. Makes the evidence-to-theory link transparent; it does not design the study (see asq-methods).

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md5.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Data Analysis & Evidence (asq-data-analysis)

When to trigger

  • You have data but the path from data to theory is opaque
  • Qualitative: your quotes are decorative, not evidentiary; coding is undocumented
  • Quantitative: main results exist but robustness/alternative explanations are thin
  • Reviewers ask "how did you get from your data to these constructs?"

Branch A — Qualitative analysis (the data-to-theory link)

ASQ expects readers to see how raw data became theory — its guidelines stress that helping readers understand how the research was performed and ensuring the trustworthiness of published work are explicit aims (verify at journals.sagepub.com/author-instructions/asq). Qualitative rigor is judged on its own terms here, not held to a quantitative yardstick. Make the analytic ladder visible.

  • Transparent coding. Describe first-order codes (informant terms), second-order themes (researcher constructs), and aggregate dimensions — the Gioia-style data structure — or an equivalent (Eisenhardt cross-case, Langley process bracketing). State who coded, how disagreements were resolved, and how iteration proceeded.
  • Data-to-theory table. Provide a table linking representative raw evidence → codes → constructs, so the inference is auditable (see asq-tables-figures).
  • Power quotes vs. proof quotes. Use a few vivid "power quotes" in the body; place corroborating "proof quotes" in tables/appendix. Quotes must carry the claim, not illustrate it after the fact.
  • Evidence for each construct. Every theoretical construct should be backed by patterned evidence across informants/cases, with counts or prevalence where appropriate.
  • Negative cases. Report disconfirming instances and how they refined the theory.
  • Process display. For process theory, show the temporal/event structure (timeline, phase model, visual mapping) — as Barley (1986, ASQ) did in tracing how CT scanners restructured radiology departments over time.

Branch B — Quantitative analysis

  • Main models match the design (FE/RE, event-history, multilevel, network models); report clearly with appropriate standard errors (clustering at the right level).
  • Robustness that targets the theory's threats: alternative measures, alternative samples, alternative specifications, endogeneity checks, and modern staggered-DiD diagnostics if relevant.
  • Mechanism evidence. Don't stop at the reduced-form relationship — provide mediation/moderation or supplementary tests that probe why.
  • Effect interpretation. Report and interpret magnitudes in organizational terms, not just significance stars.
  • Alternative explanations are tested, not waved away.

Either branch — the "so what" of the evidence

  • Tie every analytic result back to the mechanism and the surprise.
  • Distinguish what the data can and cannot establish — overclaiming is a fast path to rejection.
  • Prepare the exhibits jointly with asq-tables-figures.

Execution bridge (StatsPAI / Stata MCP)

Run the battery, don't just enumerate it. Full map: execution-with-mcp. ASQ wants a clean causal or well-identified observational design behind an organizational-theory contribution; reduced-form estimation fits the chain below, interpretive work does not.

  • Many outcomes / specifications: romano_wolf (step-down FWER) or benjamini_hochberg — report the adjusted threshold.
  • OVB sensitivity: oster_delta / sensemakr.
  • Inference: wild_cluster_bootstrap (few clusters), twoway_cluster / conley; multilevel data → cluster at the right level.
  • Re-fit off one handle: audit_result(result_id) lists the missing checks and the exact suggest_function for each.
  • Exhibits: etable / did_summary_to_latex from the handle — no retyped numbers.

Keep the decisive checks in the body and the exhaustive battery in the appendix. See the executed chain in the JF execution walkthrough.

Checklist

  • Qual: data structure (first-order → second-order → dimensions) is documented
  • Qual: a data-to-theory / evidence table is built; quotes carry (not decorate) claims
  • Qual: negative cases reported and used to refine theory
  • Quant: standard errors clustered at the appropriate level
  • Quant: robustness targets the theory's threats; effect magnitudes interpreted
  • Mechanism is probed, not just the headline relationship
  • Claims are matched to what the evidence can actually support

Anti-patterns

  • "Anecdotal" qualitative work: a few cherry-picked quotes with no coding transparency
  • Quotes that illustrate a pre-set conclusion rather than generating/supporting it
  • Quantitative robustness theater: many tables that never address the real threat
  • Reporting significance with no interpretation of organizational magnitude
  • Stopping at the X→Y relationship without evidence on the mechanism
  • Overclaiming causality or generalizability beyond the design

Output format

【Branch】qualitative / quantitative
【Data-to-theory link】data structure / mechanism tests done
【Key evidence】power quotes or main estimates
【Robustness/trustworthiness】checks completed + gaps
【What evidence cannot show】explicit limits
【Next step】asq-contribution-framing

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

The English summary is being prepared. Showing the original description.

brycewang-stanford/Awesome-Journal-Skills1.3KUpdated Sep 27, 2026

See all skills by brycewang-stanford

Report a problem with this skill