Video Understand
calesthio/OpenMontage
Understand video content locally using ffmpeg frame extraction and Whisper transcription.
A skill your agent uses when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers…
MITAuto-check passed
Install Jbv Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .claude/skills/jbv-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .claude/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .agents/skills/jbv-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .agents/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .cursor/skills/jbv-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .cursor/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path Journal-of-Business-Venturing-Skills/skills/jbv-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .gemini/skills/jbv-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .gemini/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .github/skills/jbv-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .github/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jbv-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Journal-of-Business-Venturing-Skills/skills/jbv-review-process .opencode/skills/jbv-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jbv-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Business-Venturing-Skills/skills/jbv-review-process into .opencode/skills/jbv-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jbv-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jbv-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 637 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers…
- Works in 4 steps: Handling editor's letter first — it… → Sort reviewer points into:… → Find the integrative concern — the… → …
- Understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing
- SKILL.md covers When to trigger, How JBV review works, Likely decision outcomes and Reading the decision letter, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jbv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers, desk-reject risk for off-phenomenon work, and reading a JBV decision letter. Explains the process and reads the letter; the response is drafted with jbv-rebuttal.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing
- Double-anonymized review by a minimum of two reviewers
- Desk-reject risk for off-phenomenon work
- Reading a JBV decision letter
Example prompts
- “/jbv-review-process”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Handling editor's letter first — it states the decision and the priority concerns; these are the make-or-break issues.
- Sort reviewer points into: theory/contribution, identification/selection/survivorship, framing/positioning, and presentation.
- Find the integrative concern — the cross-cutting worry (often "is the entrepreneurship contribution real?") that, if solved, resolves…
- Gauge invitation strength — does the editor signal genuine interest, or a courtesy R&R? Calibrate effort accordingly.
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Jbv Review Process loads about 1.5k tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 637 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 637 words, ~1,523 tokens.
Download SKILL.mdSave it as
.claude/skills/jbv-review-process/SKILL.md (or your agent's skills folder).- name
- jbv-review-process
- description
- Use when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers, desk-reject risk for off-phenomenon work, and reading a JBV decision letter. Explains the process and reads the letter; the response is drafted with jbv-rebuttal.
Review Process (jbv-review-process)
When to trigger
- You want to set expectations before or after submitting to JBV
- You received a decision letter and need to interpret it
- You are unsure who decides and what the bar is
- You want to gauge desk-reject risk before submitting
How JBV review works
- Area-editor routing: ScienceDirect lists current Co-Editors-in-Chief Sophie Bacq and Simon Parker and an editorial-board structure with area editors by domain. Fit with the relevant area shapes both routing and outcome — make your home conversation obvious so the paper reaches a sympathetic, expert editor.
- Double-anonymized review: suitable manuscripts are sent to a minimum of two reviewers; neither side sees identities. Off-fit or insufficiently theorized papers may be desk-rejected by the editor before review — common at this FT50 flagship.
- The bar: reviewers and the handling editor judge whether the paper advances theory about the entrepreneurial phenomenon, not just whether the method is clean. "Entrepreneurship is only the setting" is a frequent reject rationale.
Likely decision outcomes
- Desk reject: off-topic, entrepreneurship incidental, or insufficiently theorized; sometimes a fit/scope mismatch.
- Reject after review: a fatal identification/selection/survivorship problem, or a contribution judged incremental.
- Major revision (R&R): the phenomenon and contribution are promising but theory, identification, or framing need substantial work — the normal path to acceptance.
- Minor revision: targeted fixes; less common on a first decision.
Reading the decision letter
- Handling editor's letter first — it states the decision and the priority concerns; these are the make-or-break issues.
- Sort reviewer points into: theory/contribution, identification/selection/survivorship, framing/positioning, and presentation.
- Find the integrative concern — the cross-cutting worry (often "is the entrepreneurship contribution real?") that, if solved, resolves several points.
- Gauge invitation strength — does the editor signal genuine interest, or a courtesy R&R? Calibrate effort accordingly.
Norms & culture
- JBV has a strong reviewer-development and entrepreneurship-community ethos. Expect developmental, substantive reviews.
- Reviewing reciprocity is part of the community; engage constructively.
Checklist
- Identified the handling editor's priority concerns
- Reviewer points sorted (theory / identification / framing / presentation)
- Integrative concern named
- Invitation strength gauged (genuine R&R vs. courtesy)
- Desk-reject risks (off-phenomenon, thin theory) checked pre-submission
Show full SKILL.md (295 more words)Show less
Desk-reject pattern map (read before submitting)
The editor screens before review; these are the recurring grounds for a desk-reject at an entrepreneurship flagship, with the pre-emptive fix.
| Desk-reject trigger | Pre-emptive fix before upload |
|---|---|
| Entrepreneurship is the setting, not the contribution. | Make the venture/opportunity/founder mechanism the headline of abstract and intro. |
| Phenomenon-rich but theory-thin. | State the assumption challenged or new process theory; a vivid case is not yet a contribution. |
| Out-of-scope for any area editor's domain. | Position the home conversation in the first two pages so routing is clean. |
| Incremental confirmation in a new startup sample. | Reframe around what is overturned, not "first to test X on founders." |
Worked micro-example: reading a JBV letter (illustrative)
A handling editor returns a major revision on a crowdfunding-signaling paper. Triage:
- Handling-editor letter: one make-or-break concern — "I am not convinced the signaling mechanism is entrepreneurial rather than generic information economics." That is the integrative concern; solving it unlocks several points.
- Reviewer 1 (theory): wants the liability-of-newness logic made central → maps to the integrative concern.
- Reviewer 2 (identification): backers self-select into campaigns → selection threat, route to
jbv-data-analysis. - Reviewer 3 (presentation): exhibits unreadable → lowest priority, cosmetic.
- Invitation strength: "I would welcome a revision," plus specific theoretical guidance → a genuine R&R, so full effort is warranted.
Calibration anchors (hedged)
- Treat the handling editor's letter as the binding contract: the editor's stated priorities decide the outcome. Answer those first and fully.
- Multi-round R&R is the realistic path to acceptance; a first-round accept is rare.
- Numbers (timelines, acceptance rates, masthead) drift. The minimum-two-reviewer rule and area-editor structure should be confirmed against the current masthead and author guidelines.
Anti-patterns
- Treating reviewers as a checklist while ignoring the handling editor's priorities.
- Underestimating desk-reject risk for entrepreneurship-as-setting papers.
- Assuming first-round acceptance — multi-round R&R is the norm.
Output format
【Decision】desk-reject | reject | major R&R | minor ...
【Handling-editor priorities】top concerns ...
【Integrative concern】the cross-cutting issue ...
【Point map】theory / identification / framing / presentation ...
【Invitation strength】genuine | courtesy ...
【Next step】jbv-rebuttal (if R&R)© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in Journal-of-Business-Venturing-Skills/skills/jbv-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jbv Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jbv Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Video Understandcalesthio/OpenMontage | 66k | — | ~841 | Automated safety check: Pass | AGPL-3.0 | |
| Understand ExplainEgonex-AI/Understand-Anything | 86k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Understanding by Design PlannerTHU-MAIC/OpenMAIC | 40k | — | ~548 | Automated safety check: Pass | MIT | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Understand Issuemastra-ai/mastra | 29k | — | ~3.1k | Automated safety check: Pass | Custom licence |
Similar skills
Understand Explain
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
Understanding by Design Planner
THU-MAIC/OpenMAIC
Plans an OpenMAIC lesson or course series by backward design: enduring understandings and essential questions first, then performance evidence, then learning activities.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Understand Issue
mastra-ai/mastra
Investigate a GitHub issue or reported bug the way a seasoned maintainer would — form an independent model before reading the thread's theories, trace the mechanism and history, verify the…
Understand PR
mastra-ai/mastra
Review a PR the way a seasoned maintainer would — build an independent model before seeing the diff, investigate the implementation and history, verify material claims, and return a concise briefing.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Questions about Jbv Review Process
What does Jbv Review Process do?
A skill your agent uses when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers…. Jbv Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing, double-anonymized review by a minimum of two reviewers, desk-reject risk for off-phenomenon work, and reading a JBV decision letter.
When should I use Jbv Review Process?
Jbv Review Process fits situations like: understanding how the Journal of Business Venturing (JBV) review process works — Co-EIC / area-editor routing; double-anonymized review by a minimum of two reviewers; desk-reject risk for off-phenomenon work; reading a JBV decision letter.
How do I install Jbv Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a claude-code`. Or copy the skill folder (Journal-of-Business-Venturing-Skills/skills/jbv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jbv-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Jbv Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a codex`. Or copy the skill folder (Journal-of-Business-Venturing-Skills/skills/jbv-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jbv-review-process in your project. Codex loads it when a task matches its description.
Can I use Jbv Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jbv-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jbv-review-process, .gemini/skills/jbv-review-process, .github/skills/jbv-review-process and .opencode/skills/jbv-review-process in your project.
What does Jbv Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Jbv Review Process is instructions for the agent only.
Does Jbv Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Jbv Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jbv Review Process use?
Jbv Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Jbv Review Process use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Jbv Review Process?
Skills that share tags, products or a category with Jbv Review Process: Video Understand (calesthio/OpenMontage, 66k stars), Understand Explain (Egonex-AI/Understand-Anything, 86k stars), Understanding by Design Planner (THU-MAIC/OpenMAIC, 40k stars) and Understand Diff Analysis (Egonex-AI/Understand-Anything, 86k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jbv Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.