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 a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth…
Install Uist Writing Style
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-writing-style -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-writing-style .claude/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .claude/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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/UIST-Skills/skills/uist-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 uist-writing-style -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-writing-style .agents/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .agents/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-writing-style -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-writing-style .cursor/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .cursor/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 UIST-Skills/skills/uist-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 uist-writing-style -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-writing-style .gemini/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .gemini/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-writing-style .github/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .github/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-writing-style .opencode/skills/uist-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 "uist-writing-style" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-writing-style into .opencode/skills/uist-writing-style/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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
uist-writing-style- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 804 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 a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth…
- Works in 5 steps: Artifact-first pass — can a reader say… → Specificity pass — highlight every… → Claim-evidence pass — table every… → …
- Revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism)
- SKILL.md covers The UIST arc, Implementation prose that…, Claim discipline and Fitting the page budget, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Uist Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth, pairing every capability claim with a figure or measurement, and fitting the argument inside the 10-page or 5-page two-column limit.
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 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 UIST paper — structuring the systems-paper arc (walkthrough before mechanism)
- Writing an implementation section with real technical depth
- Pairing every capability claim with a figure
- Fitting the argument inside the 10-page
Example prompts
- “/uist-writing-style”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Artifact-first pass — can a reader say what you built after page 1?
- Specificity pass — highlight every number without a measurement condition.
- Claim-evidence pass — table every "can/enables/supports" against its proof.
- Video-consistency pass — nothing in the paper that the video contradicts.
- Cold read — a labmate outside the project reads the walkthrough and narrates
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
Uist Writing Style loads about 1.7k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 804 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). 804 words, ~1,723 tokens.
Download SKILL.mdSave it as
.claude/skills/uist-writing-style/SKILL.md (or your agent's skills folder).- name
- uist-writing-style
- description
- Use when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth, pairing every capability claim with a figure or measurement, and fitting the argument inside the 10-page or 5-page two-column limit.
UIST Writing Style
A UIST paper is a guided tour of a working thing. The reader should experience the
system before dissecting it, believe the engineering because it is specified, and
finish knowing exactly which piece they could reuse. This is a different rhetoric
from an empirical HCI paper (argument from study design) and from an ML paper
(argument from benchmark deltas). Format facts below are the 2026 cycle's
(two-column acmart, 10-page standard / 5-page short, references and appendices
excluded); verify against the current Author Guide.
The UIST arc
| Section | Job | Failure smell |
|---|---|---|
| Abstract + teaser figure | Name the artifact, the enabling idea, one number | No artifact named; "we explore..." |
| Introduction | What becomes possible that wasn't; contribution list | Motivation essay with the system in ¶5 |
| Walkthrough / scenario | Reader operates the system vicariously, figure-driven | Mechanism dumped before experience |
| Design rationale | The 2-4 decisions that define the system, with rejected alternatives | A feature inventory |
| Implementation | Enough specificity to re-implement: architecture, algorithms, parts, timings | "Built in Unity" as the whole section |
| Evaluation | Evidence matched to claims (see uist-experiments) | A ritual usability study proving nothing claimed |
| Applications | Breadth: 3-5 demonstrations the technique enables | Repeats of the walkthrough |
| Limitations | Engineering honesty: where it breaks, at what scale | Generic "future work will explore" |
The teaser figure under the title is load-bearing at UIST: many reviewers form their contribution hypothesis from it before reading a sentence. Design it to show the interaction, not the hardware on a bench.
Implementation prose that earns trust
Vague implementation writing is the most common style failure in UIST rejections. Specificity is cheap and convincing:
WEAK: "The system tracks the user's hand and updates the display with low latency."
STRONG: "A wrist-mounted IMU streams at 200 Hz over BLE; orientation is fused with
a complementary filter (α = 0.98) and mapped to cursor space in 1.8 ms
median (95th percentile 3.1 ms) on the target tablet, measured over
10,000 events with the harness in the supplement."Rules of thumb:
- Every latency, accuracy, weight, or cost figure carries its measurement condition.
- Name the algorithm, then say what is non-obvious about applying it here — the novelty is usually in the adaptation, and reviewers who know the algorithm will check.
- Fabrication and hardware papers: include the parts, materials, and process details
a motivated lab needs; put the full bill of materials in the appendix (see
uist-reproducibility).
Claim discipline
- Claim capabilities, not superlatives: "supports freehand annotation on curved surfaces up to 40 cm" survives review; "the first system to enable natural annotation" invites a counterexample hunt.
- Every "the system can X" needs a figure, measurement, or application section
pointing at X. Reviewers at a demo-culture venue mentally run your video against
your claims (see
uist-supplementaryfor keeping the two synchronized). - Write your own prior work in the third person with full citations — UIST's anonymization rule, and also a useful humility device.
Fitting the page budget
The 10-page limit (5 for short papers) excludes references and appendices, so the compression targets are figures and mechanism prose:
- Merge walkthrough and rationale figures: one annotated sequence beats three screenshots.
- Move parameter tables, extended benchmark grids, and study instruments to the appendix — but keep the body self-contained; the 2026 guide is explicit that the body must be readable without the appendix.
- Cut applications last: breadth of demonstration is UIST evidence, not decoration.
- Never buy space with
\vspaceor margin tricks; over-limit and modified templates are desk-reject territory (seeuist-submission).
Show full SKILL.md (298 more words)Show less
Figures do half the arguing
UIST papers are read figure-first, and the figure budget deserves design effort equal to the prose:
- The teaser (figure 1, under the title): the interaction at its most legible moment, ideally input and output in one frame, with a caption that states the capability rather than naming the parts.
- Sequence figures for the walkthrough: numbered frames with annotation arrows; readers should follow the interaction without the body text.
- Mechanism diagrams for the implementation: signal paths, layer stacks, state machines — one honest diagram replaces four paragraphs of prose and is what re-implementers screenshot.
- Results figures follow
uist-experimentsrules: distributions visible, conditions labeled, no truncated axes performing significance. - Captions are self-contained at this venue: many reviewers' first pass is figures-plus-captions only. Every caption should survive being read alone.
Language habits of accepted systems papers
- Present tense for the system ("the controller re-fits the model"), past tense for what you did ("we measured latency over 10,000 events").
- Active voice for design decisions — "we chose capacitive sensing because..." — since rationale is a claimed contribution, not a confession.
- Name the system early and use the name consistently; "our system/our approach" prose reads as unnamed and unfinished.
- Kill the throat-clearing openers ("In recent years...", "With the advent of..."); UIST introductions start inside the problem.
- Define each term of art once, then trust the reader — the audience builds interfaces for a living.
Revision passes
- Artifact-first pass — can a reader say what you built after page 1?
- Specificity pass — highlight every number without a measurement condition.
- Claim-evidence pass — table every "can/enables/supports" against its proof.
- Video-consistency pass — nothing in the paper that the video contradicts.
- Cold read — a labmate outside the project reads the walkthrough and narrates the system back; misnarrations mark the unclear paragraphs.
Output format
[Arc audit] weakest section of the eight + why
[Implementation depth] re-implementable / partially / opaque
[Unbacked claims] <list of capability claims lacking figure/measurement/app>
[Page budget] body pages vs limit, with the two cheapest cuts
[Rewrite order] <top three passes to run first>© 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 UIST-Skills/skills/uist-writing-style of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uist 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 |
|---|---|---|---|---|---|---|
| Uist Writing Style this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | 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 Uist Writing Style
What does Uist Writing Style do?
A skill your agent uses when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth…. Uist Writing Style is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when drafting or revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism), writing an implementation section with real technical depth, pairing every capability claim with a figure or measurement, and fitting the argument inside the 10-page or 5-page two-column limit.
When should I use Uist Writing Style?
Uist Writing Style fits situations like: revising a UIST paper — structuring the systems-paper arc (walkthrough before mechanism); writing an implementation section with real technical depth; pairing every capability claim with a figure; fitting the argument inside the 10-page.
How do I install Uist Writing Style in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-writing-style -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-writing-style in your project. Claude Code loads it when a task matches its description.
How do I install Uist Writing Style in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-writing-style -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-writing-style in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-writing-style in your project. Codex loads it when a task matches its description.
Can I use Uist 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 uist-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/uist-writing-style, .gemini/skills/uist-writing-style, .github/skills/uist-writing-style and .opencode/skills/uist-writing-style in your project.
What does Uist Writing Style need to run?
SKILL.md names no scripts, command-line tools or credentials: Uist Writing Style is instructions for the agent only.
Does Uist 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 Uist 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 Uist Writing Style use?
Uist 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 Uist Writing Style use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Uist Writing Style?
Skills that share tags, products or a category with Uist 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 Uist 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.