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

Orgsci Methods

ASecurity

Use when choosing and defending the research design for an Organization Science manuscript — matching one of the journal's eclectic methods (qualitative/inductive, quantitative/archival, experimental, computational/simulation, formal-analytical) to the question and level of analysis, and justifying design without requiring causal identification.

1,052 stars
0 votes
0 copies
2 views
Added 6/6/2026
ai-agentsrustgo

Security Analysis

A100/100

Scanned 6/6/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Orgsci Methods?

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

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

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

Download with Pro
Files
SKILL.md
---
name: orgsci-methods
description: Use when choosing and defending the research design for an Organization Science manuscript — matching one of the journal's eclectic methods (qualitative/inductive, quantitative/archival, experimental, computational/simulation, formal-analytical) to the question and level of analysis, and justifying design without requiring causal identification.
---

# Research Design & Methods (orgsci-methods)

## When to trigger

- You are choosing a method, or a reviewer says the method does not fit the question
- A reviewer demands causal identification you cannot obtain
- Your level of analysis and your data source do not line up
- You are mixing methods and need to justify the combination

## Match the method to the question — the journal is pluralistic

Organization Science is **methodologically eclectic**: it publishes qualitative and inductive fieldwork, quantitative and archival studies, experiments, computational/simulation models, and formal-analytical theory, and it does not privilege one. The design must **fit the theoretical contribution and the level of analysis**, not signal methodological fashion.

| Theoretical goal / data structure | Design that fits |
|-----------------------------------|------------------|
| Build a new process or construct from the field | Inductive qualitative (grounded theory, ethnography, comparative cases) |
| Test a cross-level mechanism in nested data | Multilevel / HLM with explicit composition or contextual logic |
| Trace organizational founding/failure over time | Event-history / survival; panel |
| Isolate a behavioral mechanism | Lab or field experiment, vignette/conjoint |
| Explore adaptation, learning, search dynamics | Agent-based / NK simulation or formal model |
| Characterize an interfirm or intra-org structure | Network analysis (ERGM, centrality, brokerage) |

## Causal inference is valued but not required

A defining stance: causal inference is valued but **"not necessary and often impossible"** at this venue. Do **not** abandon a strong organizational question because clean identification is unavailable. Instead, support inference with **research design, theoretical logic, institutional/field knowledge, and mechanism evidence** — triangulation, process tracing, placebo and falsification logic, and ruling out alternative explanations. This distinguishes Organization Science from identification-first, economics-leaning venues: a transparent design with a credible mechanism beats a thin paper with a clever instrument.

## Design quality that reviewers check

- **Fit:** the method can actually deliver the theoretical claim and operates at the right level.
- **Transparency:** sampling, case selection, coding scheme, manipulation, model assumptions, or parameter ranges are fully specified.
- **Trustworthiness (qualitative):** purposive sampling rationale, saturation, audit trail, member checks where relevant.
- **Replicability:** enough detail and references that others could reproduce the study; appendices carry the design detail.

## Anti-patterns

- Reaching for an instrument or quasi-experiment the setting cannot support, when mechanism evidence would serve better.
- Aggregating individual data to organizational claims with no composition justification.
- A simulation with no empirical anchor or unjustified parameter ranges.
- Method chosen to look rigorous rather than to test the theory.

## Output format

```
【Design】qualitative-inductive / multilevel / panel-EH / experiment / simulation / formal
【Level fit】matches the theoretical claim's level? cross-level logic stated?
【Inference strategy】design + logic + institutional knowledge + mechanism (not identification-only)
【Transparency/trustworthiness plan】sampling, coding, assumptions, audit trail
【Next step】orgsci-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', ...

693161 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 →