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 Contribution Framing

ASecurity

Use when turning results or a theory into an explicit contribution for the Journal of Business Venturing (JBV) — stating what new theory of the entrepreneurial phenomenon the paper delivers, its boundary conditions, and its multidisciplinary reach. Frames the claim; it does not build the mechanism (jbv-theory-development) or polish the prose (jbv-writing-style).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jbv Contribution Framing?

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

Security grade badge for Jbv Contribution Framing
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbv-contribution-framing/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbv-contribution-framing)

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

Download with Pro
Files
SKILL.md
---
name: jbv-contribution-framing
description: Use when turning results or a theory into an explicit contribution for the Journal of Business Venturing (JBV) — stating what new theory of the entrepreneurial phenomenon the paper delivers, its boundary conditions, and its multidisciplinary reach. Frames the claim; it does not build the mechanism (jbv-theory-development) or polish the prose (jbv-writing-style).
---

# Contribution Framing (jbv-contribution-framing)

## When to trigger

- Results exist but the "so what for entrepreneurship theory" is thin or implicit
- A reviewer/field editor calls the contribution "incremental" or "a setting, not a contribution"
- You cannot state in one sentence what the field now knows about entrepreneurship that it did not
- You need to write the contribution paragraph of the intro and the theoretical-implications section

## The JBV contribution bar

JBV is a discipline-defining FT50 flagship, so the theory bar is high: the paper must **clarify assumptions, expose tensions, or challenge orthodoxies** about the entrepreneurial phenomenon. State the contribution explicitly — it cannot be left implicit.

- **Phenomenon-centered**: the contribution must be to understanding entrepreneurship — venture creation, entrepreneurial cognition/behavior, financing, teams, social/sustainable/international entrepreneurship, or ecosystems — not a generic organizational insight that merely used a startup sample.
- **What changes**: name the assumption you overturn, the tension you resolve, or the new mechanism you reveal in the entrepreneurial process.
- **Multidisciplinary reach**: because JBV spans economics, psychology, and sociology, articulate which conversation(s) the contribution advances and whether it travels across lenses.

## Match the contribution to your mode

- **Hypothesis-testing paper**: the contribution is the validated (or surprising) mechanism plus its boundary conditions; say what the confirmed/disconfirmed prediction teaches about entrepreneurship.
- **Narrative/interpretive paper**: JBV values "theories, narratives, and interpretations," so the contribution can be a reconceptualization or process theory — state the new way of seeing the phenomenon and why it is more useful.

## Build the contribution statement

1. **Before**: what the entrepreneurship field assumed or could not explain.
2. **Move**: the specific theoretical move (new mechanism, boundary, reconception, integration of lenses).
3. **After**: what we now understand about the entrepreneurial phenomenon.
4. **Boundary conditions**: where the claim holds (stage, context, venture type, ecosystem).
5. **Implications**: for entrepreneurship theory first; practice (founders, investors, policy) second.

## Checklist

- [ ] One-sentence claim of new entrepreneurship knowledge is explicit
- [ ] Contribution is to the phenomenon, not a generic org insight on a startup sample
- [ ] An assumption is challenged / tension resolved / orthodoxy questioned
- [ ] Boundary conditions stated
- [ ] Conversation(s) advanced named; cross-lens reach noted if any
- [ ] Practical relevance to founders/investors/policy articulated, but secondary to theory

## Anti-patterns

- **"First to study X in startups"** dressed up as a contribution.
- **Confirmation-only** — replicating a known effect in a new venture sample.
- **Setting, not contribution** — the insight would hold for any organization.
- **Implicit contribution** — the reader must infer the "so what."

## Output format

```
【New knowledge】one sentence: what entrepreneurship now knows ...
【Before→move→after】...
【Assumption/orthodoxy challenged】...
【Boundary conditions】stage / context / venture type ...
【Conversations advanced】econ / psych / sociology ...
【Practical relevance】founders / investors / policy ...
【Next step】jbv-tables-figures or jbv-writing-style
```

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 →