Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Misq Data Analysis

ASecurity

Use when running and reporting the empirical core of a MIS Quarterly manuscript — measurement and structural models (PLS/CB-SEM) for behavioral IS, causal identification and robustness for economics-of-IS, artifact evaluation for design science, or trustworthiness for qualitative IS — and assembling the genre-appropriate transparency materials. Executes/reports the analysis; it does not design the study (misq-methods) or frame the contribution (misq-contribution-framing).

1,052 stars
0 votes
0 copies
0 views
Added 6/5/2026
ai-agentsrusttestingperformancedocumentation

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill misq-data-analysis --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Misq Data Analysis?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Misq Data Analysis
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-misq-data-analysis/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-misq-data-analysis)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: misq-data-analysis
description: Use when running and reporting the empirical core of a MIS Quarterly manuscript — measurement and structural models (PLS/CB-SEM) for behavioral IS, causal identification and robustness for economics-of-IS, artifact evaluation for design science, or trustworthiness for qualitative IS — and assembling the genre-appropriate transparency materials. Executes/reports the analysis; it does not design the study (misq-methods) or frame the contribution (misq-contribution-framing).
---

# Data Analysis, Evaluation & Transparency (misq-data-analysis)

## When to trigger

- Data are collected (or the artifact is built) and it is time to estimate, evaluate, and report
- A reviewer probes measurement validity, identification, artifact utility, or replicability
- You must prepare the pluralistic transparency materials uploaded at submission

## Analyze by tradition — there is no single MISQ estimator

| Tradition | What to report |
|-----------|----------------|
| **Behavioral** | Reliability (alpha/CR), CFA or PLS measurement model, AVE, discriminant validity (Fornell-Larcker / HTMT); structural paths with effect sizes; mediation via bootstrap CIs; moderation via simple slopes |
| **Economics of IS** | The identifying variation, parallel-trends/exogeneity evidence, clustered SEs, and a battery of robustness checks (alternative specifications, placebo/event-time tests, sensitivity to assumptions) |
| **Design science** | Artifact performance against credible baselines on held-out data; ablations; field/A-B or expert evaluation tied to the design propositions; cost/utility discussion |
| **Organizational / qualitative** | A transparent data structure (codes → themes → dimensions), an audit trail, and representative quotations so the path from raw data to constructs is traceable |

## Behavioral IS: defend measurement before structure

IS reviewers expect the measurement model first. PLS-SEM is common in IS for predictive/formative models; covariance-based SEM for theory-testing with reflective constructs — justify the choice. Report reliabilities, AVE, and discriminant validity, and address **common-method bias** beyond a single-factor test (marker variable, unmeasured method factor, or showing interactions survive). Then report structural paths with effect sizes, not just significance.

## Economics of IS: make the causal claim earn its keep

Lead with the identification logic, then stress-test it: alternative specifications, placebo and event-study plots, sensitivity to the key assumption, and clustering that matches the data structure. Report magnitudes and their economic meaning, not just stars.

## Design science: evaluate the artifact, not just the math

Demonstrate utility for the real problem: benchmark against the baselines a skeptic would name, run ablations to show which design principles matter, and connect each result back to a design proposition. Where possible, evaluate in a realistic field setting.

## Assemble the pluralistic transparency materials

MISQ's research-transparency policy is genre-appropriate, not a single template. Document the study's design, data, and analysis to the standard of your tradition, and include **procedures and/or code sufficient to permit replication**. The transparency commitment is declared and uploaded at submission (Step 2, Miscellaneous). Consider replication badges and the AIS Transactions on Replication Research collaboration. Plan code/data sharing within confidentiality and platform terms.

## Checklist

- [ ] Analysis matches the tradition (SEM / causal econometrics / artifact evaluation / qualitative)
- [ ] Behavioral: reliability, AVE, discriminant validity, CMB beyond single-factor; effect sizes
- [ ] Economics: identification defended, robustness/placebo tests, clustered SEs, magnitudes
- [ ] Design science: baselines, ablations, field/expert evaluation tied to design propositions
- [ ] Qualitative: traceable data structure and audit trail
- [ ] Genre-appropriate transparency package with procedures/code for replication prepared

## Anti-patterns

- Single-factor test as the sole common-method-bias defense.
- A causal claim with no identification and no robustness battery.
- A design-science "evaluation" that benchmarks against no credible baseline.
- Reporting p-values with no effect sizes or practical/economic interpretation.
- Treating transparency as an afterthought rather than genre-appropriate documentation.

## Output format

```
【Tradition & analysis】SEM / DiD-IV-RD / artifact eval / qualitative
【Validity or identification】measurement + CMB / identification + robustness / baselines + ablations
【Effect sizes / utility】magnitudes and meaning
【Transparency package】procedures/code for replication: ready/gaps
【Next step】misq-contribution-framing
```

Attribution

brycewang-stanfordbrycewang-stanford
View sourceMore from brycewang-stanford →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1066601 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

686011 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

651 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →