Agent skill · Documentation

jbv-writing-style

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 reference conventions and a ≤250-word abstract. Late-stage polish; do not use as a substitute for a real entrepreneurship-theory contribution (jbv-contribution-framing).

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-writing-style --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: Journal-of-Business-Venturing-Skills/skills/jbv-writing-style/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 yo

What's inside
Steps it walks through
  1. When to trigger
  2. Phenomenon-forward writing
  3. Write for a multidisciplinary reader
  4. Voice: deductive and narrative are both legitimate
  5. House style
  6. Checklist
  7. Anti-patterns
  8. Style execution pass for Journal of Business Venturing
  9. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the jbv-writing-style skill do?

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 reference conventions and a ≤250-word abstract. Late-stage polish; do not use as a substitute for a real entrepreneurship-theory contribution (jbv-contribution-framing).

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-writing-style --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going