Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when deciding which jep- sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of…
Install Jep Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-workflow --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-Economic-Perspectives-Skills/skills/jep-workflow .claude/skills/jep-workflow && 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 "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .claude/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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-Economic-Perspectives-Skills/skills/jep-workflowType 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 jep-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-workflow --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-Economic-Perspectives-Skills/skills/jep-workflow .agents/skills/jep-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .agents/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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 jep-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-workflow --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-Economic-Perspectives-Skills/skills/jep-workflow .cursor/skills/jep-workflow && 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 "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .cursor/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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-Economic-Perspectives-Skills/skills/jep-workflow--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 jep-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jep-workflow --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-Economic-Perspectives-Skills/skills/jep-workflow .gemini/skills/jep-workflow && 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 "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .gemini/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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 jep-workflowInstalls 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 jep-workflow -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-Economic-Perspectives-Skills/skills/jep-workflow .github/skills/jep-workflow && 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 "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .github/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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 jep-workflow -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 jep-workflow --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-Economic-Perspectives-Skills/skills/jep-workflow .opencode/skills/jep-workflow && 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 "jep-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Economic-Perspectives-Skills/skills/jep-workflow into .opencode/skills/jep-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jep-workflow", 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
jep-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 731 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when deciding which jep- sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of…
- Works in 11 steps: jep-topic-selection — confirm the topic… → jep-proposal-and-symposium — craft the… → jep-narrative-arc — structure the essay… → …
- Deciding which jep- sub-skill to invoke next
- SKILL.md covers Overview, When to trigger, Routing table and Default order, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jep Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jep- sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of Economic Perspectives (JEP) submission. Routes — it does not replace — the specialized skills.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science. 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
- Deciding which jep- sub-skill to invoke next
Example prompts
- “/jep-workflow”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- jep-topic-selection — confirm the topic is JEP-shaped (broad, timely, synthesizable)
- jep-proposal-and-symposium — craft the 2–5 page proposal or symposium pitch
- jep-narrative-arc — structure the essay as an argument, not a survey
- jep-accessibility-and-translation — strip jargon/notation without dumbing down
- jep-evidence-without-equations — present evidence credibly with minimal math
- jep-exhibits-for-general-readers — build self-explanatory figures/tables
- jep-writing-style — the JEP voice; abstract and opening last
- jep-balance-and-objectivity — fair to competing views; honest about uncertainty
- jep-editor-strategy — scope/length/symposium negotiation with the team
- jep-submission — email-proposal preflight (accessibility bar, disclosure, JEL)
- jep-revision — after the editor's letter
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
Jep Workflow loads about 1.7k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 731 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). 731 words, ~1,688 tokens.
Download SKILL.mdSave it as
.claude/skills/jep-workflow/SKILL.md (or your agent's skills folder).- name
- jep-workflow
- description
- Use when deciding which jep-* sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of Economic Perspectives (JEP) submission. Routes — it does not replace — the specialized skills.
JEP Workflow Router (jep-workflow)
Overview
This is the router. It tells you which jep- skill to use at the current stage* of an article aimed at the Journal of Economic Perspectives (JEP) — the open-access, non-technical synthesis journal of the American Economic Association, founded 1987. JEP is not a primary-research outlet. It rewards articles that synthesize and communicate a body of economics to a broad audience — readable by 90 percent or more of the AEA membership — avoiding formal models and heavy econometrics in the body. The product is a compelling, accessible, balanced essay, not an identification strategy or a replication package.
Default assumption: unless the user says otherwise, treat the target as JEP. Operational tells that you are at JEP and not a research journal or its sibling Journal of Economic Literature (JEL): JEP is largely invited / commissioned and organized in symposia; almost all articles begin as a 2–5 page proposal emailed to jep@aeapubs.org (about 10–15% of published articles originate as unsolicited proposals); the writing must be legible to non-specialists; there are recurring features ("Recommendations for Further Reading", retrospectives). Editor as of 2026: Heidi Williams; Managing Editor Timothy Taylor (检索于 2026-06；以官网为准). Re-verify volatile specifics on the official AEA pages.
When to trigger
- The user asks "what should I do next?" on a JEP article or proposal
- A draft reads like a research paper or a JEL survey, not a JEP essay
- Work is ping-ponging between idea, proposal, narrative, accessibility, and balance
- A JEP editor's letter arrived and the user needs to switch into revision mode
Routing table
| Current symptom | Next skill |
|---|---|
| Unsure the topic is broad/timely/synthesizable for non-specialists | jep-topic-selection |
| Need to pitch the article or a symposium to the editors | jep-proposal-and-symposium |
| Structure is a literature dump, not a story/argument | jep-narrative-arc |
| Prose is jargon-heavy; notation everywhere; reads like a working paper | jep-accessibility-and-translation |
| Evidence is presented with equations/regressions a general reader can't follow | jep-evidence-without-equations |
| Figures/tables are dense, not self-explanatory | jep-exhibits-for-general-readers |
| Voice is dry/hedged; abstract and opening don't land | jep-writing-style |
| Reads as advocacy; competing views or uncertainty underplayed | jep-balance-and-objectivity |
| Need to negotiate scope/length/symposium with the editorial team | jep-editor-strategy |
| Ready to email the proposal/manuscript; need a preflight | jep-submission |
| An editor asked for revisions (accessibility/balance/length/framing) | jep-revision |
Default order
jep-topic-selection— confirm the topic is JEP-shaped (broad, timely, synthesizable)jep-proposal-and-symposium— craft the 2–5 page proposal or symposium pitchjep-narrative-arc— structure the essay as an argument, not a surveyjep-accessibility-and-translation— strip jargon/notation without dumbing downjep-evidence-without-equations— present evidence credibly with minimal mathjep-exhibits-for-general-readers— build self-explanatory figures/tablesjep-writing-style— the JEP voice; abstract and opening lastjep-balance-and-objectivity— fair to competing views; honest about uncertaintyjep-editor-strategy— scope/length/symposium negotiation with the teamjep-submission— email-proposal preflight (accessibility bar, disclosure, JEL)jep-revision— after the editor's letter
jep-writing-styleis a late polish; do not perfect sentences before the narrative arc and the balance settle.
Show full SKILL.md (262 more words)Show less
Anti-patterns
- Writing a full unsolicited manuscript before pitching a 2–5 page proposal (low odds; editors prefer proposals)
- Treating JEP like a research journal — leading with identification, a model, or a regression table
- Confusing JEP with JEL: JEL is the long, technical survey of record; JEP is the short, non-technical, broad-audience essay
- Letting
jep-exhibits-for-general-readerspolish a dense figure while the argument is still a literature dump - Advocacy framing that an editor will read as an op-ed, not a balanced synthesis
Routing by article archetype
JEP essays come in a few shapes, and the bottleneck differs. Read the archetype, then enter the chain at the right link.
| Archetype | Likely first bottleneck | Enter at |
|---|---|---|
| "State of a field" synthesis | scope too narrow or too technical | jep-topic-selection → jep-narrative-arc |
| Symposium contribution (invited) | fit with the symposium frame + length | jep-editor-strategy → jep-narrative-arc |
| Translating one's own technical agenda | jargon/notation; over-claiming | jep-accessibility-and-translation → jep-balance-and-objectivity |
| Policy-relevant debate | reads as advocacy; uncertainty buried | jep-balance-and-objectivity |
Worked routing example (illustrative)
A user says: "I've drafted a 9,000-word piece summarizing my structural IO research for JEP, but a colleague says it reads like my JPE paper with the proofs deleted." That is two distinct JEP problems — not yet translated for a general reader and no story for a non-specialist — owned by jep-accessibility-and-translation and jep-narrative-arc. Route there first; only once a non-IO economist can follow the argument and one memorable through-line carries it do you return to jep-writing-style and jep-exhibits-for-general-readers. And before any of that, since this is an unsolicited full draft, jep-proposal-and-symposium would convert it into the 2–5 page proposal the editors actually want.
Minimal decision snippet
if editor_letter_arrived: -> jep-revision
elif ready_to_email: -> jep-submission
elif reads_as_advocacy: -> jep-balance-and-objectivity
elif exhibits_dense: -> jep-exhibits-for-general-readers
elif math_or_jargon_heavy: -> jep-evidence-without-equations / jep-accessibility-and-translation
elif structure_is_a_survey: -> jep-narrative-arc
elif no_pitch_yet: -> jep-proposal-and-symposium
else: -> jep-topic-selection© 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-Economic-Perspectives-Skills/skills/jep-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jep Workflow 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 |
|---|---|---|---|---|---|---|
| Jep Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.8k | 15 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 46k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Read arXiv Paperkarpathy/nanochat | 58k | 2 repos | ~494 | Automated safety check: Pass | MIT | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
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…
Related
Categories
Questions about Jep Workflow
What does Jep Workflow do?
A skill your agent uses when deciding which jep- sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of…. Jep Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jep- sub-skill to invoke next, or when sequencing work on an accessible synthesis article from topic idea through editor revision for a Journal of Economic Perspectives (JEP) submission.
When should I use Jep Workflow?
Jep Workflow fits situations like: deciding which jep- sub-skill to invoke next.
How do I install Jep Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-workflow -a claude-code`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jep-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Jep Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jep-workflow -a codex`. Or copy the skill folder (Journal-of-Economic-Perspectives-Skills/skills/jep-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jep-workflow in your project. Codex loads it when a task matches its description.
Can I use Jep Workflow 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 jep-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jep-workflow, .gemini/skills/jep-workflow, .github/skills/jep-workflow and .opencode/skills/jep-workflow in your project.
What does Jep Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Jep Workflow is instructions for the agent only.
Does Jep Workflow 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 Jep Workflow 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 Jep Workflow use?
Jep Workflow 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 Jep Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.8k 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 Jep Workflow?
Skills that share tags, products or a category with Jep Workflow: Hypothesis Generation (spacering-net/codeg, 3.8k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars), Nature Paper Card (Yuan1z0825/nature-skills, 46k stars) and Read arXiv Paper (karpathy/nanochat, 58k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jep Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.