Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience…
Install Jppm Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-writing-style --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-writing-style .claude/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .claude/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-styleType 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-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-writing-style --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-writing-style .agents/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .agents/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-writing-style --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-writing-style .cursor/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .cursor/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-style--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-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills jppm-writing-style --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-writing-style .gemini/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .gemini/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-styleInstalls 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-writing-style -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-writing-style .github/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .github/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-style -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-writing-style --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-writing-style .opencode/skills/jppm-writing-style && 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-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style into .opencode/skills/jppm-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jppm-writing-style", 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-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 674 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience…
- Works in 5 steps: The policy problem, concretely. Open… → Why existing knowledge cannot settle it.… → What this paper does. The design and… → …
- Revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction
- SKILL.md covers When to trigger, Write for the reader who can act, The JPP&M introduction, beat… and The abstract, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jppm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience clarity, and the evidence-not-advocacy voice. Polishes the writing; it does not change design, analysis, or framing decisions.
Its SKILL.md is about 1.4k 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 Writing & Content, covering Brand voice and tone. 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
- Revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction
- The 200-word abstract
- Dual-audience clarity
- The evidence-not-advocacy voice
Example prompts
- “/jppm-writing-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- The policy problem, concretely. Open with the marketplace harm or regulatory decision — the pending rule, the enforcement gap, the…
- Why existing knowledge cannot settle it. What the marketing-and-policy literature and the regulatory record establish, and the…
- What this paper does. The design and setting in two or three sentences, in words a policy reader follows ("we compare purchases in states…
- What was found, with magnitude. The headline estimate in decision units, including the heterogeneity or backfire result if it matters.
- Who should do what. One or two sentences previewing the stakeholder actions the findings support — the intro's version of the Policy…
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 Writing Style loads about 1.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 674 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). 674 words, ~1,385 tokens.
Download SKILL.mdSave it as
.claude/skills/jppm-writing-style/SKILL.md (or your agent's skills folder).- name
- jppm-writing-style
- description
- Use when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience clarity, and the evidence-not-advocacy voice. Polishes the writing; it does not change design, analysis, or framing decisions.
Writing Style (jppm-writing-style)
When to trigger
- The introduction opens with a literature gap instead of the policy problem
- The abstract never says who should do what differently
- Method jargon (ATTs, bandwidths, moderated mediation) floods sections a practitioner must read
- The tone slips from findings into editorializing about what government "must" do
- Prose is the last bottleneck — estimates, framing, and exhibits are stable
Write for the reader who can act
A JPP&M paper is read by marketing academics, by scholars in law and policy, and — if it succeeds — by people inside agencies and NGOs. The prose contract: the policy problem carries the story, the evidence carries the authority, and any reader should be able to extract the actionable takeaway without decoding the econometrics. That means plain-language topic sentences, technical depth layered underneath rather than in front, and a strict separation between what the data show and what the authors prefer. The manuscript is double-spaced, at most 50 pages including everything, with a 200-word unstructured abstract and at least three keywords (per the AMA journals guidelines; re-check current specifics on ama.org).
The JPP&M introduction, beat by beat
- The policy problem, concretely. Open with the marketplace harm or regulatory decision — the pending rule, the enforcement gap, the population being hurt — with a fact and a source, not throat-clearing about "growing interest."
- Why existing knowledge cannot settle it. What the marketing-and-policy literature and the regulatory record establish, and the decision-relevant unknown that remains.
- What this paper does. The design and setting in two or three sentences, in words a policy reader follows ("we compare purchases in states that adopted the rule to matched states that did not").
- What was found, with magnitude. The headline estimate in decision units, including the heterogeneity or backfire result if it matters.
- Who should do what. One or two sentences previewing the stakeholder actions the findings support — the intro's version of the Policy Contribution Statement.
The abstract
Two hundred words must state the policy question, the method in one clause, the key finding with direction and rough magnitude, and the implication for named stakeholders. Editors desk-screen from the abstract plus the Policy Contribution Statement; an abstract that ends at "implications are discussed" invites the bolted-on-policy suspicion.
Show full SKILL.md (302 more words)Show less
Voice: evidence, not editorial
- Verbs match identification: "shows/reduces" for well-identified estimates; "suggests/is consistent with" for correlational or lab-only evidence.
- No advocacy adverbs: "clearly," "obviously," "alarmingly" signal a brief, not a study.
- Respect the other side of the ledger: costs to firms, implementation burden, and speech or preemption constraints get honest sentences, not dismissals.
- Define instruments on first use: not every reader knows what the Green Guides or a consent order is; not every reader knows what an ATT is either. One clause each.
- Vulnerable populations are people: person-first, non-stigmatizing language; describe constraints, not deficiencies.
Sentence-level craft
- Lead paragraphs with the claim, follow with the evidence; never make the reader assemble the point from a stack of citations.
- Keep one term per construct — a "warning," "disclosure," and "label" that are the same thing multiply confusion.
- Numbers in text carry their units and comparison ("a 2-percentage-point drop from a 14% base"), never naked coefficients.
- Cut the methods-section prose that repeats the table; cite the exhibit and interpret it instead.
Checklist
- The intro opens on the policy problem with a sourced fact
- The decision-relevant unknown is stated before the method
- Headline results appear in decision units in both intro and abstract
- Abstract ≤200 words: question, method, finding, stakeholder implication
- Claim verbs are calibrated to identification strength throughout
- No advocacy tone; trade-offs acknowledged in the discussion
- Jargon layered: any section a practitioner needs is readable without training
Anti-patterns
- Gap-first opening: "despite growing interest, little research…" before any reader knows why to care
- "Implications are discussed": an abstract that hides the takeaway
- Brief-speak: prose whose conviction outruns its confidence intervals
- Jargon front-loading: estimator names in the introduction, harms in the appendix
- Term drift: the same instrument renamed section by section
- Deficit framing: writing about vulnerable consumers as problems rather than as people the market underserves
Output format
【Intro lead】policy problem + sourced fact in paragraph one? [Y/N]
【Unknown】decision-relevant gap stated pre-method? [Y/N]
【Abstract】≤200 words with question/method/finding/actor? [Y/N]
【Voice audit】verbs calibrated; advocacy adverbs removed? [Y/N]
【Dual-audience pass】practitioner-readable sections confirmed? [Y/N]
【Next skill】jppm-submission© 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-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Jppm Writing Style 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 Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| BrandOhh-889/skyroc | 795 | 13 repos | ~733 | Automated safety check: Pass | MIT | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Writing Guidelinesvercel-labs/agent-skills | 32k | 7 repos | ~309 | Automated safety check: Pass | None | |
| Unslop AI Writing Cleanuptheclaymethod/unslop | 518 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Brand
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
- Official
Writing Guidelines
vercel-labs/agent-skills
Review docs/prose for Writing Guidelines compliance. An agent skill from vercel-labs/agent-skills.
Unslop AI Writing Cleanup
theclaymethod/unslop
Removes AI writing tells from prose through an audit-first flow, routing to a two-pass rewrite, a report-only cleanup, voice teaching or mimicry depending on the sub-command used.
UX Writing
content-designer/ux-writing-skill
Applies UX writing practice to interface copy such as buttons, errors, forms and onboarding, using four quality standards and accessibility guidance.
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 Writing Style
What does Jppm Writing Style do?
A skill your agent uses when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience…. Jppm Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience clarity, and the evidence-not-advocacy voice.
When should I use Jppm Writing Style?
Jppm Writing Style fits situations like: revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction; the 200-word abstract; dual-audience clarity; the evidence-not-advocacy voice.
How do I install Jppm Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-writing-style -a claude-code`. Or copy the skill folder (Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/jppm-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Jppm Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jppm-writing-style -a codex`. Or copy the skill folder (Journal-of-Public-Policy-and-Marketing-Skills/skills/jppm-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/jppm-writing-style in your project. Codex loads it when a task matches its description.
Can I use Jppm Writing Style 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-writing-style -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-writing-style, .gemini/skills/jppm-writing-style, .github/skills/jppm-writing-style and .opencode/skills/jppm-writing-style in your project.
What does Jppm Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Jppm Writing Style is instructions for the agent only.
Does Jppm Writing Style 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 Writing Style 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 Writing Style use?
Jppm Writing Style 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 Writing Style use?
About 1.4k tokens (SKILL.md is roughly 5.5k 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 Writing Style?
Skills that share tags, products or a category with Jppm Writing Style: Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars), Brand (Ohh-889/skyroc, 795 stars), Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars) and Writing Guidelines (vercel-labs/agent-skills, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jppm Writing Style?
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.