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 jppm- sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing…
Install Jppm Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .claude/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .claude/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-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 jppm-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .agents/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .agents/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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 jppm-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .cursor/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .cursor/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-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 jppm-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .gemini/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .gemini/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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 jppm-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 jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .github/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .github/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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 jppm-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 jppm-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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow .opencode/skills/jppm-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 "jppm-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow into .opencode/skills/jppm-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-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
jppm-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 721 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 jppm- sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing…
- Deciding which jppm- 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
- Sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission
What it does
Jppm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jppm- sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission. Routes to the specialized skills — it does not do their work.
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 jppm- sub-skill to invoke next
- Sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission
Example prompts
- “/jppm-workflow”
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
Jppm Workflow loads about 1.7k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 721 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). 721 words, ~1,652 tokens.
Download SKILL.mdSave it as
.claude/skills/jppm-workflow/SKILL.md (or your agent's skills folder).- name
- jppm-workflow
- description
- Use when deciding which jppm-* sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission. Routes to the specialized skills — it does not do their work.
JPP&M Workflow Router (jppm-workflow)
Overview
This router directs work on a manuscript aimed at the Journal of Public Policy & Marketing (JPP&M) — the American Marketing Association journal, published by SAGE, that lives at the intersection of marketing, public policy, and consumer/societal welfare. Since April 1, 2026, new submissions are handled by joint Editors in Chief Melissa Bublitz and Stacey Finkelstein, who succeeded Jeremy Kees and Beth Vallen (checked 2026-07-16 on ama.org; re-check the masthead before submitting). The journal's home turf: consumer protection and deception, warning and disclosure design, public-health marketing (tobacco, alcohol, food and nutrition labeling), privacy and data policy, sustainability, financial well-being, vulnerable consumers, and equity in marketplaces.
What makes JPP&M unlike any other marketing outlet is a hard policy-relevance bar. Every submission must include a Policy Contribution Statement (max 300 words, first page of the main document, excluded from the page cap) that names the policy conversation the paper joins, the advance over existing marketing-and-policy literature, and the specific stakeholders — FTC, FDA, CFPB, state regulators, NGOs, or marketers navigating regulation — who could act on the findings. A technically excellent consumer study with a policy paragraph stapled to the discussion is the journal's signature desk reject. Review is double-anonymized; manuscripts run at most 50 double-spaced pages inclusive of everything at every stage; submission goes through SageTrack at mc.manuscriptcentral.com/ama_jppm.
When to trigger
- "What should I do next?" on a marketing-and-policy manuscript
- The paper has strong evidence but nobody can say which regulator would care
- Work is bouncing among framing, evaluation design, and the implications section
- A JPP&M decision letter arrived and you need to enter revision mode at the right link
- The team is torn between JPP&M and JM, JCR/JCP, Journal of Consumer Affairs, or a policy-school journal
Routing table
| Current symptom | Next skill |
|---|---|
| Unclear whether the question is policy-first or just consumer research in a policy costume | jppm-topic-selection |
| No account of why the policy lever should change marketplace behavior | jppm-theory-development |
| Paper ignores the JPP&M canon or the regulatory record; gap statement is soft | jppm-literature-positioning |
| Choosing between an experiment, a quasi-experiment around a policy rollout, a survey, or a meta-analysis | jppm-methods |
| DiD/RDD estimates, treatment effects, or subgroup analyses need to be defensible | jppm-data-analysis |
| The Policy Contribution Statement is vague, or implications are not actionable | jppm-contribution-framing |
| Exhibits speak only to academics, not to a policy reader | jppm-tables-figures |
| Prose is jargon-heavy, advocacy-tinged, or the intro buries the policy problem | jppm-writing-style |
| Ready for SageTrack; need the anonymization, page-count, and statement preflight | jppm-submission |
| Need to understand the editor/AE pipeline, desk-reject odds, R&R norms | jppm-review-process |
| Drafting the response letter and revision plan for an R&R | jppm-rebuttal |
Show full SKILL.md (291 more words)Show less
Default order
jppm-workflow → jppm-topic-selection → jppm-theory-development → jppm-literature-positioning → jppm-methods → jppm-data-analysis → jppm-contribution-framing → jppm-tables-figures → jppm-writing-style → jppm-submission → jppm-review-process → jppm-rebuttal
The Policy Contribution Statement is written twice: a draft at
jppm-topic-selection(to test whether the paper deserves to exist) and a final version atjppm-contribution-framing(once the estimates are in). Do not polish prose before the counterfactual holds up.
Routing by paper archetype
| Archetype | Binding constraint | Enter at |
|---|---|---|
| Policy evaluation (a law/rule changed; did behavior?) | counterfactual credibility (DiD/RDD design) | jppm-methods |
| Consumer-protection experiment (warning, disclosure, label) | realistic stimuli + regulator-usable treatment contrasts | jppm-methods |
| Vulnerable-population field study | ethics, access, and welfare framing | jppm-topic-selection → jppm-theory-development |
| Privacy / data-policy study | mapping findings to a live rulemaking debate | jppm-literature-positioning |
| Conceptual / review piece for policymakers | synthesis that yields decisions, not a tour | jppm-contribution-framing |
Worked routing example (illustrative)
A user says: "We ran three studies showing calorie counts on menus reduce ordering; a friendly reviewer said 'nice JCP paper — why is this JPP&M?'" That is the classic boundary failure. Route to jppm-topic-selection to re-anchor the question in the live disclosure-regulation debate (what the FDA menu-labeling rule already requires, what remains contested), then jppm-contribution-framing to rewrite the Policy Contribution Statement around a decision a named stakeholder faces — e.g., whether to extend the rule to delivery platforms — and only then reconsider whether an extra study on the contested margin is needed (jppm-methods).
Anti-patterns
- Treating JPP&M as "JCP plus a policy paragraph" — the mechanism is welcome, but the policy question must drive
- Routing straight to
jppm-writing-stylewhen the real problem is a missing counterfactual - Advocating a regulation the data do not test — evidence-free advocacy is a desk reject here
- Writing implications no actual regulator has the authority or instrument to act on
- Quoting the editor team or portal from memory instead of re-checking ama.org / SAGE before submission
Output format
【Target】Journal of Public Policy & Marketing
【Archetype】policy-evaluation / protection-experiment / vulnerable-population / privacy-data / conceptual-review
【Current bottleneck】fit / theory-of-the-lever / positioning / design / estimates / policy-framing / exhibits / style / submission / revision
【Next skill】<one jppm-* skill>
【Reason】why this is the binding constraint now
【Source check】official facts verified (2026-07-16) or flagged "re-check on the official site"© 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-Public-Policy-and-Marketing-Skills/skills/jppm-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jppm 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 |
|---|---|---|---|---|---|---|
| Jppm Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | 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.
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.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Jppm Workflow
What does Jppm Workflow do?
A skill your agent uses when deciding which jppm- sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing…. Jppm Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when deciding which jppm- sub-skill to invoke next, or when sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission.
When should I use Jppm Workflow?
Jppm Workflow fits situations like: deciding which jppm- sub-skill to invoke next; sequencing manuscript work from topic selection through rebuttal for a Journal of Public Policy & Marketing (JPP&M) submission.
How do I install Jppm Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-workflow -a claude-code`. Or copy the skill folder (Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jppm-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Jppm Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-workflow -a codex`. Or copy the skill folder (Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jppm-workflow in your project. Codex loads it when a task matches its description.
Can I use Jppm 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 jppm-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/jppm-workflow, .gemini/skills/jppm-workflow, .github/skills/jppm-workflow and .opencode/skills/jppm-workflow in your project.
What does Jppm Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Jppm Workflow is instructions for the agent only.
Does Jppm 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 Jppm 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 Jppm Workflow use?
Jppm 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 Jppm 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 Jppm Workflow?
Skills that share tags, products or a category with Jppm Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jppm Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.