Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
A skill your agent uses when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a…
Install Soda Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-writing-style .claude/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .claude/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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/SODA-Skills/skills/soda-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 soda-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-writing-style .agents/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .agents/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-writing-style .cursor/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .cursor/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 SODA-Skills/skills/soda-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 soda-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills soda-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/SODA-Skills/skills/soda-writing-style .gemini/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .gemini/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-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 soda-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/SODA-Skills/skills/soda-writing-style .github/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .github/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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 soda-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 soda-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/SODA-Skills/skills/soda-writing-style .opencode/skills/soda-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 "soda-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SODA-Skills/skills/soda-writing-style into .opencode/skills/soda-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "soda-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
soda-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 708 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a…
- Works in 4 steps: Barrier paragraph — what specifically… → Technique narrative with a running… → Proof roadmap — lemma dependency sketch,… → …
- Revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly
- SKILL.md covers The headline bound, The title-page abstract, First ten pages: the overview… and The prior-bound table, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Soda Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a first-ten-pages overview for triage readers, prior-bound comparison tables, and prose discipline for an uncapped full-version document.
Its SKILL.md is about 1.6k 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 a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly
- The title-page abstract that wins bidding
- A first-ten-pages overview for triage readers
- Prior-bound comparison tables
Example prompts
- “/soda-writing-style”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Barrier paragraph — what specifically stops the previous technique.
- Technique narrative with a running example — a small concrete instance
- Proof roadmap — lemma dependency sketch, so the back matter reads as
- Comparison table — see below.
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
Soda Writing Style loads about 1.6k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 708 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). 708 words, ~1,573 tokens.
Download SKILL.mdSave it as
.claude/skills/soda-writing-style/SKILL.md (or your agent's skills folder).- name
- soda-writing-style
- description
- Use when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a first-ten-pages overview for triage readers, prior-bound comparison tables, and prose discipline for an uncapped full-version document.
SODA Writing Style
SODA prose serves two readers with opposite budgets: a PC member triaging a record-size pool who gives you minutes, and a subreviewer in your exact niche who gives you days. The uncapped format (no page limit, full version encouraged — 2027 CFP, checked 2026-07-08) means you never trade completeness for space; the craft is entirely in layering, so the minutes-reader and the days-reader each get a document built for them.
The headline bound
An algorithms paper is quoted by its bound, so engineer the quotable sentence:
- State it with exact parameters: "a deterministic
O(m log^2 n)-time algorithm for weighted global min-cut," not "a faster deterministic algorithm." - Pair it immediately with the displaced bound: "improving the
O(m log^4 n)bound of [X, SODA 2019]." New readers calibrate by the delta. - If randomization, approximation, or model caveats qualify the bound, they appear in the same sentence — a caveat discovered on page 30 reads as concealment.
- Resist rounding up: "near-optimal" claims invite the referee to construct the regime where you are not.
The title-page abstract
SODA submissions open with a title page: title plus a one-to-two-paragraph abstract of the contributions (2027 CFP). This abstract is the PC's bidding surface — it decides who reviews you. Structure that has survived contact:
Paragraph 1 (the result):
Problem, model, headline bound, displaced prior bound, and the
open-problem citation if one exists. Numbers, not adjectives.
Paragraph 2 (the technique):
The one new idea, named concretely ("a recursive sparsifier that
tolerates deletions"), plus why known approaches get stuck —
one sentence each. This paragraph recruits the right expert.First ten pages: the overview contract
Everything after the overview is verification; the overview itself must let a non-specialist theorist reconstruct why the result is true at cartoon resolution. Ingredients, in order of most common omission:
- Barrier paragraph — what specifically stops the previous technique. Papers that skip this get "incremental" reviews from readers who cannot see why the improvement was hard.
- Technique narrative with a running example — a small concrete instance walked through the new algorithm beats three pages of notation.
- Proof roadmap — lemma dependency sketch, so the back matter reads as
planned architecture (
soda-supplementary). - Comparison table — see below.
The prior-bound table
Algorithms referees expect the lineage as a table and will reconstruct it if you do not provide it — on their terms, not yours:
| Reference | Bound | Deterministic? | Model / caveat |
|---|---|---|---|
| [Karger-era result] | O(m log^3 n) | randomized | Monte Carlo |
| [previous best] | O(m log^4 n) | deterministic | — |
| This paper | O(m log^2 n) | deterministic | — |
Rules: cite the strongest version of each prior result (journal version if it improved), include the inconvenient rows, and footnote incomparable results rather than omitting them.
Show full SKILL.md (320 more words)Show less
Prose discipline for long documents
- Uncapped is not unedited. Every page must still earn verification effort; padding multiplies referee fatigue and referee fatigue reads as doubt.
- One notation system, declared once. Re-derivations of standard facts get a citation, not a subsection.
- Theorem statements are self-contained: model, input restrictions, and probability regime inside the statement, never "under the assumptions of Section 2" (referees quote theorems out of context; make that safe).
- Lemmas get names in comments ("the charging lemma") — PC discussion happens in nicknames, and you want yours to have them.
- Third-person self-citation throughout (lightweight double-blind,
soda-submission), but keep the citations present.
Titles that survive PC compression
The title is the unit of memory in deliberation and in citation. Patterns, with fictional examples:
| Pattern | Fictional example | When it fits |
|---|---|---|
| Bound-carrying | "Dynamic Interval Stabbing in Polylogarithmic Worst-Case Time" | The bound is the news — the default SODA choice |
| Barrier-breaking | "Breaking the sqrt(n) Barrier for Online Recoloring" | A named threshold falls; use only if prior work called it a barrier |
| Problem-resolving | "The Communication Complexity of Threshold Joins" | You close the problem (up to stated factors) |
| Technique-forward | "Deletion-Tolerant Sparsifiers and Their Applications" | Only when the tool provably outlives the application |
| Question title | "Is Sorting by Prefix Swaps Fixed-Parameter Tractable?" | Rare; only if the answer is surprising |
Anti-patterns: pun-first titles (unquotable in a review), "Towards..." (admits incompleteness), "A New Approach to..." (contains zero information), and stacked qualifiers that belong in the theorem, not the marquee.
Register calibration
| Overclaim | Calibrated version |
|---|---|
| "We settle the complexity of X" | "We resolve the deterministic time complexity of X up to log log n factors" |
| "Our technique is completely new" | "We are not aware of prior uses of deletion-tolerant sparsification in this setting" |
| "Experiments confirm our algorithm is practical" | "A preliminary implementation (not part of our claims) suggests the constants are moderate" |
| "It is easy to see" (×20) | Prove it once; "routine calculation, included for completeness, in Appendix D" |
Output format
[Style verdict] Submission-grade / Needs revision / Needs restructuring
[Headline audit] <bound stated exactly? caveats co-located? displaced bound named?>
[Abstract audit] <bidding-surface quality; expert-recruiting technique sentence present?>
[Overview audit] <barrier, running example, roadmap, table — which are missing>
[Register flags] <overclaims with suggested calibrated rewrites>© 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 SODA-Skills/skills/soda-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Soda 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 |
|---|---|---|---|---|---|---|
| Soda Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 Soda Writing Style
What does Soda Writing Style do?
A skill your agent uses when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a…. Soda Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when writing or revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly, the title-page abstract that wins bidding, a first-ten-pages overview for triage readers, prior-bound comparison tables, and prose discipline for an uncapped full-version document.
When should I use Soda Writing Style?
Soda Writing Style fits situations like: revising a SODA (ACM-SIAM Symposium on Discrete Algorithms) paper — headline bounds stated exactly; the title-page abstract that wins bidding; A first-ten-pages overview for triage readers; prior-bound comparison tables.
How do I install Soda Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-writing-style -a claude-code`. Or copy the skill folder (SODA-Skills/skills/soda-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/soda-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Soda Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill soda-writing-style -a codex`. Or copy the skill folder (SODA-Skills/skills/soda-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/soda-writing-style in your project. Codex loads it when a task matches its description.
Can I use Soda 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 soda-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/soda-writing-style, .gemini/skills/soda-writing-style, .github/skills/soda-writing-style and .opencode/skills/soda-writing-style in your project.
What does Soda Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Soda Writing Style is instructions for the agent only.
Does Soda 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 Soda 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 Soda Writing Style use?
Soda 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 Soda Writing Style use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Soda Writing Style?
Skills that share tags, products or a category with Soda 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 Soda 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.