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 jms- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission.
Install Jms Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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-Management-Studies-Skills/skills/jms-workflow .claude/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .claude/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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-Management-Studies-Skills/skills/jms-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 jms-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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-Management-Studies-Skills/skills/jms-workflow .agents/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .agents/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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-Management-Studies-Skills/skills/jms-workflow .cursor/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .cursor/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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-Management-Studies-Skills/skills/jms-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 jms-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jms-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-Management-Studies-Skills/skills/jms-workflow .gemini/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .gemini/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-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 jms-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-Management-Studies-Skills/skills/jms-workflow .github/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .github/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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 jms-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 jms-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-Management-Studies-Skills/skills/jms-workflow .opencode/skills/jms-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 "jms-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Management-Studies-Skills/skills/jms-workflow into .opencode/skills/jms-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jms-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
jms-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 706 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 jms- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission.
- Works in 11 steps: jms-topic-selection — lock a… → jms-theory-development — build the… → jms-literature-positioning — stake the… → …
- Deciding which jms- 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
Jms Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jms- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) 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 jms- sub-skill to invoke next
- Sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission
Example prompts
- “/jms-workflow”
Workflow steps
11 steps, taken from the first numbered list in SKILL.md.
- jms-topic-selection — lock a phenomenon-grounded management question
- jms-theory-development — build the mechanism / propositions (or hypotheses)
- jms-literature-positioning — stake the contribution to a live conversation
- jms-methods — match design to the question (qual / quant / multi-method)
- jms-data-analysis — estimation or qualitative trustworthiness
- jms-contribution-framing — sharpen the "so what for theory & practice"
- jms-tables-figures — exhibits, data tables, process / data-structure figures
- jms-writing-style — make the idea land (abstract + intro last)
- jms-submission — ScholarOne preflight (anonymisation, Harvard, word count)
- jms-review-process — calibrate the developmental, multi-round culture
- jms-rebuttal — after the R&R
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
Jms Workflow loads about 1.7k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 706 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). 706 words, ~1,657 tokens.
Download SKILL.mdSave it as
.claude/skills/jms-workflow/SKILL.md (or your agent's skills folder).- name
- jms-workflow
- description
- Use when deciding which jms-* sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission. Routes — it does not replace — the specialized skills.
JMS Workflow Router (jms-workflow)
Overview
This is the router. It tells you which jms- skill to use at the current stage* of a manuscript aimed at the Journal of Management Studies (JMS) — the Society for the Advancement of Management Studies (SAMS) journal published by Wiley, an internationally oriented, European-rooted outlet for management and organization studies: strategy, organization theory, entrepreneurship, innovation, OB, and the broader study of management. JMS's defining trait is methodological pluralism: it publishes strong quantitative and strong qualitative / interpretive / process / theory-building work, plus Point–CounterPoint debates and JMS Says essays. What earns space is a genuine theoretical contribution engaged with an organizational phenomenon — the "so what for management theory and practice."
Default assumption: unless the user says otherwise, treat the target as JMS. Tells that you are at JMS and not a sibling: double-blind review with full anonymisation; Harvard author-date referencing; a typical length of 10,000–13,000 words inclusive of tables/figures/references; submission via ScholarOne (mc.manuscriptcentral.com/jmstudies); editorial office at Durham University; and a house culture that treats a rigorous qualitative case or process study as first-class rather than second-best. Mark volatile specifics (检索于 2026-06；以官网为准).
When to trigger
- The user asks "what should I do next?" on a JMS-bound paper
- A draft needs its current bottleneck diagnosed
- Work is ping-ponging between theory, design, evidence, framing, writing, and the response letter
- A JMS decision letter arrived and the user needs to switch into revision mode
Routing table
| Current symptom | Next skill |
|---|---|
| Topic feels narrow / not clearly a management-theory question | jms-topic-selection |
| The theoretical mechanism / propositions are thin or borrowed | jms-theory-development |
| Contribution vs. the conversation is fuzzy or oversold | jms-literature-positioning |
| Design (qual/quant/multi-method) does not fit the theory | jms-methods |
| Estimation, coding, or trustworthiness of the analysis is weak | jms-data-analysis |
| The "so what for theory & practice" is not sharp | jms-contribution-framing |
| Tables/figures (or a data structure / process figure) are dense | jms-tables-figures |
| Prose buries the idea; abstract/intro do not land | jms-writing-style |
| Anonymisation, Harvard refs, word count, portal preflight | jms-submission |
| Want to understand the developmental review timeline / desk-reject odds | jms-review-process |
| Received an R&R; need a response-letter strategy | jms-rebuttal |
Default order
jms-topic-selection— lock a phenomenon-grounded management questionjms-theory-development— build the mechanism / propositions (or hypotheses)jms-literature-positioning— stake the contribution to a live conversationjms-methods— match design to the question (qual / quant / multi-method)jms-data-analysis— estimation or qualitative trustworthinessjms-contribution-framing— sharpen the "so what for theory & practice"jms-tables-figures— exhibits, data tables, process / data-structure figuresjms-writing-style— make the idea land (abstract + intro last)jms-submission— ScholarOne preflight (anonymisation, Harvard, word count)jms-review-process— calibrate the developmental, multi-round culturejms-rebuttal— after the R&R
jms-writing-styleis a late-stage polish; do not rewrite the intro before the theory and evidence settle. For qualitative work, theory and data co-evolve, so cycle 2↔4↔5 more than once.
Show full SKILL.md (251 more words)Show less
Routing by paper archetype
JMS spans four archetypes, and the binding constraint differs by archetype. Read the archetype, then enter the chain at the right link.
| Archetype | Likely first bottleneck | Enter at |
|---|---|---|
| qualitative / grounded theory-building (cases, ethnography) | data-to-construct transparency + theoretical model from data | jms-theory-development → jms-methods |
| process / longitudinal (how things unfold over time) | temporal bracketing, mechanism, narrative-to-theory | jms-theory-development → jms-data-analysis |
| quantitative hypothesis-testing (survey / archival) | endogeneity, CMB, a non-bald mechanism | jms-methods → jms-data-analysis |
| Point–CounterPoint / review essay / JMS Says | a contestable claim + a conversation worth moving | jms-contribution-framing → jms-literature-positioning |
Worked routing example (illustrative)
A user says: "My inductive study of how family firms professionalise is rich, but a reviewer says the contribution is 'a nice description, not theory,' and the data structure is hard to follow." That is two JMS pushbacks — no abstracted theoretical model and opaque data-to-theory chain — owned by jms-theory-development (abstract the first-order codes into second-order themes and aggregate dimensions, then a process model) and jms-tables-figures (a Gioia-style data-structure figure plus a representative-quotes table). Route to theory first; only once the emergent model is crisp do you return to exhibits and jms-contribution-framing.
Anti-patterns
- Treating JMS like AMJ (US hypothetico-deductive default), Organization Studies (more EGOS / process-theoretical), Journal of Management (SMA, US general/meta-analytic), or SMJ (strategy-economics) — JMS is the SAMS pluralist outlet that genuinely welcomes strong qualitative work
- Polishing prose before the theoretical contribution and evidence hierarchy are stable
- Forcing a qualitative study into a hypotheses-and-controls template, or judging it by quant criteria
- Letting an online appendix carry claims the 13,000-word main text must establish
Output format
【Target】Journal of Management Studies (JMS)
【Archetype】qualitative / process / quantitative / Point-CounterPoint
【Current bottleneck】topic / theory / positioning / design / evidence / framing / exhibits / style / submission / revision
【Next skill】<one jms-* skill>
【Reason】why this step is the binding constraint
【Source check】official facts verified or marked 待核实© 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-Management-Studies-Skills/skills/jms-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jms 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 |
|---|---|---|---|---|---|---|
| Jms 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 Jms Workflow
What does Jms Workflow do?
A skill your agent uses when deciding which jms- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission. Jms Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jms- sub-skill to invoke next, or when sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission.
When should I use Jms Workflow?
Jms Workflow fits situations like: deciding which jms- sub-skill to invoke next; sequencing manuscript work from topic through rebuttal for a Journal of Management Studies (JMS) submission.
How do I install Jms Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-workflow -a claude-code`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jms-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Jms Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jms-workflow -a codex`. Or copy the skill folder (Journal-of-Management-Studies-Skills/skills/jms-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jms-workflow in your project. Codex loads it when a task matches its description.
Can I use Jms 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 jms-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/jms-workflow, .gemini/skills/jms-workflow, .github/skills/jms-workflow and .opencode/skills/jms-workflow in your project.
What does Jms Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Jms Workflow is instructions for the agent only.
Does Jms 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 Jms 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 Jms Workflow use?
Jms 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 Jms Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.6k 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 Jms Workflow?
Skills that share tags, products or a category with Jms 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 Jms 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.