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 Writing Style

ASecurity

Use when polishing the prose of a Journal of Business Venturing (JBV) manuscript — front-loading the entrepreneurial phenomenon, writing for a multidisciplinary audience, honoring JBV's openness to narrative/interpretive voice, and applying Elsevier author–date conventions and a ≤250-word abstract. Late-stage polish; do not use as a substitute for a real entrepreneurship-theory contribution (jbv-contribution-framing).

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-writing-style --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Jbv Writing Style?

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

Security grade badge for Jbv Writing Style
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/brycewang-stanford-jbv-writing-style/badge)](https://www.skillsdirectory.com/skills/brycewang-stanford-jbv-writing-style)

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

Download with Pro
Files
SKILL.md
---
name: jbv-writing-style
description: Use when polishing the prose of a Journal of Business Venturing (JBV) manuscript — front-loading the entrepreneurial phenomenon, writing for a multidisciplinary audience, honoring JBV's openness to narrative/interpretive voice, and applying Elsevier author–date conventions and a ≤250-word abstract. Late-stage polish; do not use as a substitute for a real entrepreneurship-theory contribution (jbv-contribution-framing).
---

# Writing Style (jbv-writing-style)

## When to trigger

- The prose buries the entrepreneurial phenomenon under jargon or method detail
- The paper reads as written for one discipline only
- You are tightening the abstract, intro, and discussion before submission
- A reviewer says the argument is "hard to follow" or "the entrepreneurship is lost"

## Phenomenon-forward writing

JBV is phenomenon-driven, so the writing must put the **entrepreneurial phenomenon first**:

- **Open on the phenomenon**: the first paragraph should make a reader feel the entrepreneurial puzzle (a venture-creation tension, a founder/investor decision under uncertainty), not open on a literature gap or a method.
- **Front-load the argument**: state the question, the mechanism, and the contribution to entrepreneurship early; do not make the reader wait until the discussion.
- **Keep entrepreneurship central in every section** — methods and results prose should keep tying back to what is learned about the phenomenon, so the paper never reads as a generic study that happened to use startups.

## Write for a multidisciplinary reader

Because JBV spans economics, psychology, and sociology, your reader may not share your home discipline:

- Define discipline-specific constructs on first use; avoid unexplained jargon from one lens.
- When you integrate lenses, signpost the move explicitly so an economist and a psychologist both follow.

## Voice: deductive and narrative are both legitimate

JBV welcomes "theories, narratives, and interpretations." Match voice to mode:

- **Hypothesis-testing**: crisp, active, claim-first sentences; hypotheses stated plainly.
- **Narrative/interpretive**: a coherent, vivid account is appropriate and valued — but it must still be disciplined theorizing, not storytelling for its own sake.

## House style

- **Abstract**: concise and factual, **not exceeding 250 words**; convey phenomenon, approach, and contribution.
- **References**: author–date style; at first submission, "Your Paper Your Way" allows flexible formatting provided each reference is complete (author, title, year, journal/book, volume, pages/article number).
- Active voice, present tense for established findings, past tense for what you did.

## Checklist

- [ ] Opening makes the entrepreneurial phenomenon vivid (not a gap or a method)
- [ ] Question, mechanism, and contribution front-loaded
- [ ] Entrepreneurship stays central across methods/results prose
- [ ] Cross-discipline constructs defined; integration signposted
- [ ] Voice matches mode (deductive crispness vs. disciplined narrative)
- [ ] Abstract ≤ 250 words, phenomenon-first
- [ ] Author–date references complete and consistent

## Anti-patterns

- **Method-first opening** that hides the entrepreneurial stakes.
- **Single-discipline jargon** that excludes JBV's broader audience.
- **Story without theory** mistaken for "narrative" — JBV wants disciplined narrative.
- **Abstract over 250 words** or that omits the contribution.

## Output format

```
【Hook】does it open on the phenomenon? fix ...
【Front-loading】question/mechanism/contribution early? ...
【Multidisciplinary clarity】jargon defined; integration signposted ...
【Voice】deductive | disciplined-narrative — consistent? ...
【Abstract】word count ≤250; phenomenon-first? ...
【References】author–date complete/consistent? ...
【Next step】jbv-submission
```

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 →