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 Methods

ASecurity

Use when choosing and defending the research design for a MIS Quarterly manuscript — a behavioral survey/experiment, an economics-of-IS identification strategy, a design-science build-and-evaluate cycle, or an organizational/qualitative design. Matches the method to the IS claim and the manuscript category; it designs the study and hands estimation/evaluation to misq-data-analysis.

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Misq Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: misq-methods
description: Use when choosing and defending the research design for a MIS Quarterly manuscript — a behavioral survey/experiment, an economics-of-IS identification strategy, a design-science build-and-evaluate cycle, or an organizational/qualitative design. Matches the method to the IS claim and the manuscript category; it designs the study and hands estimation/evaluation to misq-data-analysis.
---

# Research Design & Methods (misq-methods)

## When to trigger

- You have a theory or design propositions but no defensible way to test/evaluate them
- The method may not match the tradition or the claim (e.g., a causal claim with a correlational design)
- A reviewer asks "how do you know the artifact works?" or "what identifies this effect?"
- You need to decide what fits inside the category page limit (which counts everything)

## Match the design to the tradition and claim

MISQ spans four traditions, so there is no single mandated method. Pick the design that the claim requires.

| Tradition | Typical designs | The design must establish |
|-----------|-----------------|----------------------------|
| **Behavioral** | Lab/online experiment, field experiment, multi-wave survey, panel | Internal validity, construct validity, and (for surveys) procedural remedies for common-method bias |
| **Design science** | Build-and-evaluate of an IT artifact | That the artifact is novel and useful for a real problem — utility demonstrated, not asserted |
| **Economics of IS** | Natural experiment, DiD, IV, RD, structural model | A credible identification strategy for the causal/economic effect |
| **Organizational** | Case study, ethnography, mixed methods, longitudinal field | Trustworthiness, rich context, and a transparent path from data to constructs |

## Design science: plan the evaluation up front

A MISQ design-science paper lives or dies on **evaluation**. Following Hevner et al. (2004), decide before building how you will demonstrate utility: held-out benchmarks against credible baselines, a controlled experiment or A/B field deployment, simulation, or expert evaluation — and tie each back to the design propositions. State the problem's relevance, the artifact's novelty, and the evaluation criteria so reviewers can judge rigor *and* relevance. "We built it and it ran" is not an evaluation.

## Behavioral and economics: design out the threats early

- **Behavioral surveys:** build in *procedural* separations against common-method bias — temporal/psychological/source separation, validated scales, attention/manipulation checks — because statistical fixes alone will not convince reviewers later.
- **Economics of IS:** anchor identification in a real source of exogenous variation (a platform/policy change, staggered rollout, a breach, a system go-live). Pre-commit the comparison and the assumptions you will defend.

## Mind the page budget

Because supplementary materials are discouraged and the page limit counts text, tables, figures, references, and appendices, design a study whose evidence fits the chosen category. Scope the design to the page budget rather than planning to offload it to an online appendix.

## Checklist

- [ ] Design matches the tradition and the strength of the claim
- [ ] Behavioral: validity threats and CMB designed out, not just measured
- [ ] Economics: a named source of exogenous variation and a defensible identification logic
- [ ] Design science: an evaluation plan tied to design propositions and credible baselines
- [ ] Qualitative: a transparent, traceable path from data to constructs
- [ ] The evidence fits the category page limit

## Anti-patterns

- A causal IS claim resting on a cross-sectional correlation.
- A design-science artifact with no comparison and no real-problem evaluation.
- Single-source, single-wave self-report with no procedural CMB remedies.
- A design that only "fits" by exporting half the evidence to discouraged supplements.

## Output format

```
【Tradition & design】experiment / survey / DiD-IV-RD / build-and-evaluate / qualitative
【Identification or evaluation】source of variation OR evaluation plan + baselines
【Validity threats handled】CMB / confounds / trustworthiness
【Fits page budget?】yes / trim
【Next step】misq-data-analysis
```

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 →