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

Jbv Theory Development

ASecurity

Use when building the theoretical argument for a Journal of Business Venturing (JBV) manuscript — constructing a multidisciplinary mechanism (economics, psychology, sociology) for an entrepreneurial phenomenon, and choosing between hypothesis-testing and narrative/interpretive theorizing. Builds the argument; it does not pick the question (jbv-topic-selection) or run the analysis (jbv-data-analysis).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

$npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-theory-development --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jbv Theory Development?

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

Security grade badge for Jbv Theory Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbv-theory-development/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbv-theory-development)

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

Download with Pro
Files
SKILL.md
---
name: jbv-theory-development
description: Use when building the theoretical argument for a Journal of Business Venturing (JBV) manuscript — constructing a multidisciplinary mechanism (economics, psychology, sociology) for an entrepreneurial phenomenon, and choosing between hypothesis-testing and narrative/interpretive theorizing. Builds the argument; it does not pick the question (jbv-topic-selection) or run the analysis (jbv-data-analysis).
---

# Theory Development (jbv-theory-development)

## When to trigger

- Your "hypotheses" are descriptive ("A relates to B in startups") with no entrepreneurial mechanism
- You need to choose the disciplinary engine — agency/real-options (economics), cognition/affect (psychology), networks/legitimacy (sociology)
- A field editor or reviewer says the theory "could be about any organization, not entrepreneurship"
- You are deciding whether to write a deductive model or a narrative/interpretive theory

## JBV's theory bar

JBV elevates **"theories, narratives, and interpretations"** of the antecedents, mechanisms, and consequences of entrepreneurship. Two legitimate paths:

- **Hypothetico-deductive**: derive testable hypotheses from an explicit mechanism. The mechanism must be *about the entrepreneurial phenomenon* — opportunity, judgment under Knightian uncertainty, resource assembly under resource constraints, legitimacy of the new and unknown (liability of newness), founder identity, etc. — not a generic organizational process.
- **Narrative / interpretive**: build an interesting, internally coherent account or process theory of how entrepreneurial action unfolds. JBV's stance is broader than the strict deductive template of many top management journals — a compelling reconceptualization can be the contribution.

## Pick the disciplinary engine (and combine deliberately)

JBV is multidisciplinary *by design*. Make the lens explicit and consider integrating two:

- **Economics**: uncertainty vs. risk, search and experimentation, real options, information asymmetry and signaling in financing, incentives, selection markets.
- **Psychology**: entrepreneurial cognition, judgment and heuristics, self-efficacy, passion, affect, regulatory focus, grit, overconfidence.
- **Sociology**: networks, embeddedness, institutional logics, legitimacy, categories, status, social movements, regional/ecosystem structure.

State a clear mechanism: a causal/process chain with a why, scope conditions, and the entrepreneurial actor or activity at its center.

## Build moderation/mediation around the phenomenon

- Moderators should reflect entrepreneurial context — uncertainty, resource scarcity, novelty, ecosystem support, founder/team attributes — not generic firm covariates.
- Mediators should trace the entrepreneurial process (opportunity belief → action → outcome), making the mechanism observable.

## Checklist

- [ ] Mechanism is specific to the entrepreneurial phenomenon (not any organization)
- [ ] Primary disciplinary engine named; integration justified if multidisciplinary
- [ ] Mode chosen (deductive hypotheses vs. narrative/interpretive theory) and executed consistently
- [ ] Scope/boundary conditions of the theory stated
- [ ] Moderators/mediators reflect entrepreneurial context, not generic covariates
- [ ] Assumptions surfaced; a tension or orthodoxy is challenged, not just confirmed

## Anti-patterns

- **Generic-org theory in a startup costume** — the mechanism would read identically for an incumbent.
- **Hypothesis salad** — many predictions, no unifying entrepreneurial mechanism.
- **Borrowing a construct without a boundary** — importing a psychology/sociology construct with no scope for the entrepreneurial setting.
- **Pretend deduction (HARKing)** — hypotheses reverse-engineered from results.

## Output format

```
【Phenomenon mechanism】the entrepreneurial why, in one chain ...
【Engine】economics / psychology / sociology (+ integration) ...
【Mode】deductive hypotheses | narrative-interpretive theory ...
【Hypotheses or propositions】H1..Hk / P1..Pk ...
【Boundary conditions】...
【Tension challenged】...
【Next step】jbv-literature-positioning
```

Attribution

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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

Know which skills are safe — weekly.

Best new skills + every skill we flagged as malicious. From the team that scanned 103,619.

Join free

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 →