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 Literature Positioning

ASecurity

Use when positioning a Journal of Business Venturing (JBV) manuscript in the entrepreneurship literature — joining a live conversation, problematizing assumptions instead of gap-spotting, and engaging across economics, psychology, and sociology. Positions the paper; it does not derive the mechanism (jbv-theory-development) or state the contribution claim (jbv-contribution-framing).

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

Security Analysis

A100/100

Scanned 6/5/2026

Install to Claude Code

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

Installs into .claude/skills of the current project.

Are you the author of Jbv Literature Positioning?

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

Security grade badge for Jbv Literature Positioning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbv-literature-positioning/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbv-literature-positioning)

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

Download with Pro
Files
SKILL.md
---
name: jbv-literature-positioning
description: Use when positioning a Journal of Business Venturing (JBV) manuscript in the entrepreneurship literature — joining a live conversation, problematizing assumptions instead of gap-spotting, and engaging across economics, psychology, and sociology. Positions the paper; it does not derive the mechanism (jbv-theory-development) or state the contribution claim (jbv-contribution-framing).
---

# Literature Positioning (jbv-literature-positioning)

## When to trigger

- Your introduction reads as "X is understudied in entrepreneurship" (gap-spotting)
- Reviewers say you "ignore the canonical entrepreneurship conversation"
- You cite only one discipline when the phenomenon spans several
- You are unsure which scholarly conversation your paper actually joins

## Join a conversation, do not spot a gap

At an FT50 entrepreneurship flagship, "no one has studied this" is a weak motivation. Instead:

- **Problematize**: surface and challenge an assumption the entrepreneurship field takes for granted (e.g., that opportunities are discovered vs. created, that VC signals quality, that more resources always help nascent ventures). Problematization beats gap-filling.
- **Name the conversation**: state precisely which entrepreneurship debate you enter — opportunity discovery vs. creation, effectuation vs. causation, the role of failure and learning, financing signals, ecosystem effects — and what you add or overturn.
- **Engage multidisciplinarily**: JBV is grounded in economics, psychology, and sociology. If your phenomenon spans lenses, cite across them; positioning only within one discipline when the puzzle is broader reads as thin to a field editor who routes across domains.

## Map the landscape before claiming novelty

- Distinguish the *entrepreneurship* literature from the general management/strategy literature your work touches. JBV cares that the conversation is about the entrepreneurial phenomenon.
- Cite the foundational and the most recent JBV / entrepreneurship work on your topic; show you are current, not re-deriving settled results.
- Identify the closest two or three papers and articulate the *delta* — what they assumed or could not see that you now show.

## Field-editor routing implication

Because manuscripts are managed by **field editors** who curate their own reviewer pools, your positioning signals which domain (and editor) should handle the paper. Make the home conversation unmistakable in the first two pages so the paper routes to a sympathetic, expert field editor and reviewers.

## Checklist

- [ ] Motivation is problematization, not "understudied"
- [ ] The specific entrepreneurship conversation is named
- [ ] Multidisciplinary engagement where the phenomenon warrants it
- [ ] Closest 2-3 papers identified with an explicit delta
- [ ] Entrepreneurship literature distinguished from adjacent general-management work
- [ ] Positioning makes the field-editor domain obvious

## Anti-patterns

- **Gap-spotting** as the sole hook.
- **Citation dumping** — long undifferentiated reference lists with no conversation.
- **Single-silo positioning** when the phenomenon is multidisciplinary.
- **Straw-manning** the discovery/creation or effectuation debates to manufacture novelty.

## Output format

```
【Conversation joined】the entrepreneurship debate, named ...
【Assumption problematized】...
【Disciplines engaged】econ / psych / sociology ...
【Closest papers + delta】[A] assumed ...; we show ...
【Field-editor signal】home domain for routing ...
【Next step】jbv-methods or jbv-contribution-framing
```

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 →