Venue
LeoYeAI/openclaw-master-skills
Music venue where AI agents stream concerts as mathematics. An agent skill from LeoYeAI/openclaw-master-skills.
A skill your agent uses when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the…
MITAuto-check passed
Install Uai Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-workflow .claude/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .claude/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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/UAI-Skills/skills/uai-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 uai-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-workflow .agents/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .agents/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-workflow .cursor/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .cursor/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 UAI-Skills/skills/uai-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 uai-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uai-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/UAI-Skills/skills/uai-workflow .gemini/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .gemini/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-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 uai-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/UAI-Skills/skills/uai-workflow .github/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .github/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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 uai-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 uai-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/UAI-Skills/skills/uai-workflow .opencode/skills/uai-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 "uai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UAI-Skills/skills/uai-workflow into .opencode/skills/uai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uai-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
uai-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.8k tokens
- SKILL.md length
- 796 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the…
- Planning a UAI cycle end to end
- SKILL.md covers The 2026 shape of a UAI year, Backward plan from the paper…, Role assignments that prevent… and Between decision and conference, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- From venue-fit confirmation through the winter submission deadline
What it does
Uai Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Planning a UAI cycle end to end
- From venue-fit confirmation through the winter submission deadline
- The spring review and author-response phases
- The June decision
Example prompts
- “/uai-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 (its code samples are yaml).
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
Uai Workflow loads about 1.8k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 796 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). 796 words, ~1,812 tokens.
Download SKILL.mdSave it as
.claude/skills/uai-workflow/SKILL.md (or your agent's skills folder).- name
- uai-workflow
- description
- Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.
UAI Workflow
Use this as the project-management layer over the other UAI skills. UAI is a conference run by the AUAI: there is no editor-in-chief and no rolling submission — one deadline per year, per-edition chairs, and PMLR publication funded by registration rather than author fees. The 2026 calendar below is the verified anchor (checked 2026-07-08); substitute the current year's official dates before planning anything.
The 2026 shape of a UAI year
| Phase | 2026 anchor | Owner-side work |
|---|---|---|
| Fit decision | months before | Confirm uncertainty is the contribution (uai-topic-selection) |
| Submission opens | Jan 25 | OpenReview profiles, conflicts, subject areas ready |
| Paper deadline | Feb 25, 23:59 AoE | Single PDF (8pp main + appendix), ≤15 MB, ZIP ≤50 MB |
| Bidding | Mar 2–9 | Nothing — routing was set by your abstract |
| Reviews written | Mar 21 – Apr 11 | Prepare response infrastructure; draft anticipated objections |
| Author response | Apr 23 – May 2 | Evidence-anchored replies (uai-author-response) |
| Reviewer–AC discussion | May 2–8 | Silence; the response argues for you |
| Notification | Jun 1 | Triage outcome; celebrate or re-route |
| Camera-ready | Jul 27 | PMLR files, public artifacts (uai-camera-ready) |
| Conference | Aug 17–21, Amsterdam | Tutorials Mon, main Tue–Thu, workshops Fri |
Backward plan from the paper deadline
Offsets assume a probabilistic-methods paper with theory and experiments; shift for your mix, and re-anchor to current official dates:
- T−10 weeks: contribution sentence frozen; identifiability/guarantee target named; ladder of experiments designed (exact-truth, stress, real).
- T−8: core theorem believed and sketched; assumption set labeled A1…An and no longer moving.
- T−6: exact-truth experiments done; the theorem's prediction visibly matches or the paper's story changes now, not at T−1.
- T−4: full draft in the UAI template; appendix skeleton mirrors main-text numbering; baselines tuned and logged.
- T−3: internal mock review against the four criteria (correctness, novelty, backing, clarity) by someone outside the project.
- T−2: stress and real-data experiments locked; determinism ledger and manifests in the artifact; supplementary ZIP assembled from a clean export.
- T−1: anonymity sweep of PDF and ZIP; page/size caps verified mechanically; OpenReview form fields drafted.
- T−0: upload early in the day AoE-wise; re-download and cold-read.
Role assignments that prevent the classic failures
# uai-cycle-owners.yaml — one name per row, no shared ownership
anonymity_sweep: # PDF + ZIP + metadata; leaks are unfixable after the deadline
evidence_map: # every claim -> exhibit; updated when any result changes
appendix_integrity: # body statements == appendix statements after every edit
artifact_build: # clean-export ZIP, manifest files, size cap
openreview_form: # profiles, conflicts, subject areas, abstract == PDF abstract
response_marshal: # archives submitted PDF; drafts objection bank before reviews
camera_ready: # PMLR forms, de-anonymization, public repo tag
presentation: # poster, spotlight, registration, travel/visa timelineThe two most damaging single points of failure at UAI specifically: an unowned anonymity sweep (appendices inside the reviewed PDF widen the leak surface), and an unowned appendix-integrity check (deadline-week edits to body theorems silently orphan their proofs).
Between decision and conference
- Accepted: the June-to-July window carries camera-ready, artifact publication, and registration simultaneously — assign them to different people on day one.
- Rejected: run the axis triage from
uai-review-processwithin a week while context is fresh; the natural re-route targets (AISTATS, NeurIPS/ICML, CLeaR, or a journal) have their own calendars, and reviews in hand are an asset that depreciates. - Either way: at least one author may be called to review for UAI — the volunteer agreement signed at submission — so protect reviewing bandwidth in March–April.
Show full SKILL.md (337 more words)Show less
The cycle archive
One deadline per year means institutional memory is the compounding asset. At each transition, file into a shared, dated directory:
- The exact uploaded PDF and ZIP (deadline day) — responses must quote these.
- The OpenReview form contents as submitted (screenshot or export).
- All reviews, your responses, and the meta-review (decision day).
- The camera-ready as published, plus the PMLR entry once the volume is live.
- A one-page retrospective: which criterion drew fire, which anticipated objection materialized, what the next cycle should do differently.
Groups that skip the retrospective re-learn the same reviewer objection annually.
Contingency table
| If this happens | Then | Because |
|---|---|---|
| Theorem breaks at T−3 | Demote it to a conjecture + empirical study, or pull the paper | A wrong proof fails correctness; a scoped claim can still pass backing |
| Key experiment unfinished at T−1 | Cut the claim, not the caveats | Claims without exhibits fail the backing criterion |
| Coauthor conflict list incomplete at deadline | Fix profiles before the form, even if tight | Conflict errors poison assignment invisibly |
| Reviews arrive harsher than expected | Run axis triage before drafting anything | Emotion-first responses waste the short window |
| Accepted but presenter cannot travel | Check the current remote-presentation rules immediately | 2026 said "physically or remotely", but details were 待核实 |
| Rejected with fixable-axis reviews | Target the next honest-fit deadline within the month | Review memory and momentum decay fast |
First-cycle notes
For a group's first UAI attempt: budget one extra week for OpenReview profile setup and conflict entry across all authors; expect the two-column template to shrink an apparently-fitting draft by half a page; and have the mock reviewer score the four posted criteria explicitly — first-time submissions most often lose on backing, not on correctness.
Standing warnings
- Never inherit dates from this file or from memory; the official important-dates page is the only calendar.
- Registration fees, in-person requirements, and remote-presentation options were not fully verifiable for 2026 at pack-check time (待核实) — confirm before booking travel or promising remote attendance.
- One-deadline venues punish schedule slips brutally: a week late here is a year late.
Output format
[Cycle position] fit / build / submitted / response / decided / camera-ready / conference
[Next hard date] <official date + source URL>
[Critical path] <three tasks gating the next transition>
[Owner gaps] <rows in the owner map without a name>
[Re-route plan] <standing answer to "if rejected, then where">© 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 UAI-Skills/skills/uai-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uai 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 |
|---|---|---|---|---|---|---|
| Uai Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| VenueLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Credit Cycle Analysissickn33/agentic-awesome-skills | 47k | 1 repos | ~4.2k | Automated safety check: Pass | MIT | |
| Table Fitasgeirtj/system_prompts_leaks | 69k | — | ~772 | Automated safety check: Pass | CC0-1.0 | |
| Furniture Fit Checkpascalorg/editor | 25k | — | ~5.1k | Automated safety check: Pass | MIT | |
| Fitness Programrevfactory/harness-100 | 1.3k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Credit Cycle Analysis
sickn33/agentic-awesome-skills
Debtor and creditor credit-cycle analysis: weighted collection or payment days, ageing buckets, credit limit utilisation and gap against benchmark.
Table Fit
asgeirtj/system_prompts_leaks
Keep a Markdown table readable in a narrow terminal of about 100 display columns - a wide table or one carrying prose in its cells wraps into unreadable ragged rows.
Furniture Fit Check
pascalorg/editor
Checks whether a sofa, table, bed or appliance fits in a measured Pascal room and reports only what the evidence supports, or asks for the missing measurements.
Fitness Program
revfactory/harness-100
A full pipeline where an agent team collaborates to generate everything from goal-based fitness program design to progress tracking templates.
Scientific Venue Templates
davila7/claude-code-templates
Supplies LaTeX templates and formatting rules for journals, conferences, posters, and grant proposals, then can check a draft against them.
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…
Questions about Uai Workflow
What does Uai Workflow do?
A skill your agent uses when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the…. Uai Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a UAI cycle end to end, from venue-fit confirmation through the winter submission deadline, the spring review and author-response phases, the June decision, the July PMLR camera-ready, and the August conference, as one backward-planned calendar with named owners for anonymity, evidence, and packaging tasks.
When should I use Uai Workflow?
Uai Workflow fits situations like: planning a UAI cycle end to end; from venue-fit confirmation through the winter submission deadline; the spring review and author-response phases; the June decision.
How do I install Uai Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-workflow -a claude-code`. Or copy the skill folder (UAI-Skills/skills/uai-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uai-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Uai Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uai-workflow -a codex`. Or copy the skill folder (UAI-Skills/skills/uai-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uai-workflow in your project. Codex loads it when a task matches its description.
Can I use Uai 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 uai-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/uai-workflow, .gemini/skills/uai-workflow, .github/skills/uai-workflow and .opencode/skills/uai-workflow in your project.
What does Uai Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Uai Workflow is instructions for the agent only.
Does Uai 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 Uai 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 Uai Workflow use?
Uai 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 Uai Workflow use?
About 1.8k tokens (SKILL.md is roughly 7.2k 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 Uai Workflow?
Skills that share tags, products or a category with Uai Workflow: Venue (LeoYeAI/openclaw-master-skills, 2.2k stars), Credit Cycle Analysis (sickn33/agentic-awesome-skills, 47k stars), Table Fit (asgeirtj/system_prompts_leaks, 69k stars) and Furniture Fit Check (pascalorg/editor, 25k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uai 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.