HyperFrames Animation
heygen-com/hyperframes
Collects motion rules, scene blueprints, transitions and runtime adapters for HyperFrames video compositions, with GSAP as the default animation runtime.
A skill your agent uses when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional…
Install Uist Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-workflow .claude/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .claude/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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/UIST-Skills/skills/uist-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 uist-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-workflow .agents/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .agents/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-workflow .cursor/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .cursor/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 UIST-Skills/skills/uist-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 uist-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills uist-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/UIST-Skills/skills/uist-workflow .gemini/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .gemini/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-workflow .github/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .github/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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 uist-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 uist-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/UIST-Skills/skills/uist-workflow .opencode/skills/uist-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 "uist-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/UIST-Skills/skills/uist-workflow into .opencode/skills/uist-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uist-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
uist-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 730 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 UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional…
- Works in 5 steps: T minus 0-1 weeks — submission… → T minus 1-3 weeks — video figure… → T minus 3-6 weeks — evaluation.… → …
- Planning a UIST cycle end to end — the late-March abstract and paper deadlines
- SKILL.md covers The 2026 reference calendar, Backwards plan for a systems…, Owners and risk register and The two parallel lanes, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Uist Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.
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 Media & Creative, covering Video production. 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 UIST cycle end to end — the late-March abstract and paper deadlines
- The ten-week build-freeze before video production
- The rebuttal window
- Conditional acceptance
Example prompts
- “/uist-workflow”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- T minus 0-1 weeks — submission mechanics. PCS uploads, anonymity sweeps,
- T minus 1-3 weeks — video figure production. Scripting, capture, edit,
- T minus 3-6 weeks — evaluation. Technical benchmarks and any user study; IRB
- T minus 6-10 weeks — feature freeze. Everything demonstrated in the paper
- T minus 10+ weeks — build. Include one full hardware re-spin or one major
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 Workflow loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 730 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). 730 words, ~1,585 tokens.
Download SKILL.mdSave it as
.claude/skills/uist-workflow/SKILL.md (or your agent's skills folder).- name
- uist-workflow
- description
- Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.
UIST Workflow
A UIST year is engineered backwards from two fixed points: the paper deadline in late
March and the conference in the fall. Between them sits a pipeline with almost no
slack for hardware failures, video production, or study scheduling. This skill turns
the cycle into a managed project. All dates below are the verified 2026 numbers
(checked 2026-07-08); reopen uist.acm.org/<year>/cfp/ before committing a calendar.
The 2026 reference calendar
| Date (2026) | Event | Author obligation |
|---|---|---|
| Mar 24 | Abstract deadline (AoE) | Title, abstract, authors, track metadata in PCS |
| Mar 31 | Paper deadline (AoE) | PDF + video figure + supplementary, all anonymous |
| May 28 - Jun 5 | Rebuttal window | 5,000-character self-contained response |
| Jun 27 | Notification | Decisions are conditional on rebuttal-promised changes |
| Jul 24 | Camera-ready | TAPS source, alt text, final video, +10% page allowance |
| Nov 2 | Doctoral Symposium (in person) | Separate track, separate deadline |
| Nov 2-5 | Conference, Detroit | Talk + (typically) live demo of the system |
As of 2026-07-08 the live obligations are the camera-ready chain for accepted papers and the adjunct tracks (Demos, Posters — deadlines 待核实, read the CFP) for everyone else; new submissions target the 2027 cycle.
Backwards plan for a systems paper
Work in reverse from the paper deadline; the ordering below is where UIST projects actually fail, not a generic writing schedule:
- T minus 0-1 weeks — submission mechanics. PCS uploads, anonymity sweeps,
abstract-field consistency (see
uist-submission). - T minus 1-3 weeks — video figure production. Scripting, capture, edit,
captions, anonymization. The video cannot be shot until the system is stable, and
it competes with the writing for the same people (see
uist-supplementary). - T minus 3-6 weeks — evaluation. Technical benchmarks and any user study; IRB approval must predate this window, so file it in the fall.
- T minus 6-10 weeks — feature freeze. Everything demonstrated in the paper must exist by here. Features added after freeze belong to the next paper.
- T minus 10+ weeks — build. Include one full hardware re-spin or one major refactor in the estimate, because there will be one.
Owners and risk register
Assign names, not roles, and write the mitigation before the risk fires:
RISK OWNER MITIGATION
Hardware breaks in video week <name> Build two units; film B-roll early
Study participants no-show <name> Over-recruit 30%; pilot in freeze week
Video render/caption pipeline <name> Dry-run export at T-3w with dummy edit
Page-limit overflow (10pp body) <name> Appendix plan agreed at T-4w
Rebuttal week hits a holiday <name> Pre-draft objection playbook (uist-author-response)
Camera-ready owner on vacation <name> TAPS + alt-text buddy named at notificationThe two parallel lanes
UIST is one conference with two archival containers, and a healthy group uses both:
- Papers lane (main proceedings): the full pipeline above.
- Adjunct lane (Demos, Posters — separate chairs, separate deadlines, adjunct proceedings): a rejected paper's system can still appear at the conference as a demo; early-stage work can test community reaction as a poster; the same work must not be submitted to both Demos and Posters (the 2026 rule converts it to a demo and drops the poster). Decide the fallback lane on notification day, not after the adjunct deadlines pass.
Show full SKILL.md (288 more words)Show less
Planning UIST 2027 from a mid-2026 vantage
For teams reading this in the live window (post-notification 2026), the next Papers deadline is roughly nine months out and the calendar is not yet published (待核实 — watch the 2027 site from its first announcement). Provisional planning rules that survive cycle drift:
- Assume the abstract/paper pair lands in late March ± a few weeks and the conference in the fall; anchor the feature-freeze ten weeks before the assumed deadline and adjust when the real dates post.
- Anything involving human subjects needs ethics approval filed by roughly December; anything involving custom hardware needs its final revision ordered by January (fab and shipping queues do not respect AoE).
- Book video-production capacity — the person, the rig, the edit suite — for the two pre-deadline weeks now; it is the least substitutable resource in the pipeline.
- Draft the contribution list before the spring: if you cannot write three capability claims in January, the project is a 2028 paper wearing a 2027 badge.
The month-by-month cadence (generic UIST year)
| Months before deadline | Focus |
|---|---|
| 9-7 | Routing decision, system architecture, ethics filing |
| 7-4 | Core build; related-work sweep running in parallel |
| 4-2.5 | Feature freeze; evaluation harness and pilots |
| 2.5-1 | Studies and technical characterization; paper skeleton |
| 1-0.5 | Video production; full drafts circulating |
| 0.5-0 | Submission mechanics only — nothing new enters the paper |
Between cycles
- File a post-mortem within two weeks of notification while reviews are fresh: which review criticism was predictable at freeze time?
- Convert the submission's infrastructure — build scripts, benchmark harnesses, capture rigs — into reusable lab property; UIST groups compound or burn out on exactly this.
- Watch the next edition's site from its first announcement: dates shift by weeks between editions and the length rules have changed across recent cycles.
Output format
[Cycle target] UIST <year> papers / demos / posters / DS
[Today's phase] build / freeze / evaluation / video / submission / review / rebuttal / camera-ready / conference prep
[Critical path] <the single task that moves the finish date>
[Risk register] top three, each with named owner
[Next fixed date] <date + obligation>© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Uist 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 |
|---|---|---|---|---|---|---|
| Uist Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| HyperFrames Animationheygen-com/hyperframes | 59k | 3 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills | 8.4k | 6 repos | ~3.2k | Automated safety check: Notes | Apache-2.0 | |
| Faceless Explainer Videoheygen-com/hyperframes | 59k | 3 repos | ~7.7k | Automated safety check: Notes | Apache-2.0 | |
| Video Understandcalesthio/OpenMontage | 66k | — | ~841 | Automated safety check: Pass | AGPL-3.0 | |
| Video ShotcraftVincentwei1021/video-shotcraft | 11k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Stitch to Remotion Walkthrough Videos
google-labs-code/stitch-skills
Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.
Faceless Explainer Video
heygen-com/hyperframes
Turns an article, notes or a topic brief into an explainer video whose visuals are invented per scene, built frame by frame in HyperFrames with no footage.
Video Understand
calesthio/OpenMontage
Understand video content locally using ffmpeg frame extraction and Whisper transcription.
Video Shotcraft
Vincentwei1021/video-shotcraft
Makes cinematic product videos with Remotion from shot recipe cards, a ready template, real page screenshots, camera moves and sound design, or builds a single animated shot.
Figma to HyperFrames
heygen-com/hyperframes
Imports Figma assets, brand tokens, components and motion into a HyperFrames video composition, using the Figma REST API with a connector or native export for shaders.
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 Workflow
What does Uist Workflow do?
A skill your agent uses when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional…. Uist Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a UIST cycle end to end — the late-March abstract and paper deadlines, the ten-week build-freeze before video production, the rebuttal window, conditional acceptance, the July camera-ready, adjunct-track parallel lanes, and the November conference — with owners and risk buffers.
When should I use Uist Workflow?
Uist Workflow fits situations like: planning a UIST cycle end to end — the late-March abstract and paper deadlines; the ten-week build-freeze before video production; the rebuttal window; conditional acceptance.
How do I install Uist Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-workflow -a claude-code`. Or copy the skill folder (UIST-Skills/skills/uist-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/uist-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Uist Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill uist-workflow -a codex`. Or copy the skill folder (UIST-Skills/skills/uist-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/uist-workflow in your project. Codex loads it when a task matches its description.
Can I use Uist 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 uist-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/uist-workflow, .gemini/skills/uist-workflow, .github/skills/uist-workflow and .opencode/skills/uist-workflow in your project.
What does Uist Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Uist Workflow is instructions for the agent only.
Does Uist 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 Uist 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 Uist Workflow use?
Uist 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 Uist Workflow 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 Uist Workflow?
Skills that share tags, products or a category with Uist Workflow: HyperFrames Animation (heygen-com/hyperframes, 59k stars), Stitch to Remotion Walkthrough Videos (google-labs-code/stitch-skills, 8.4k stars), Faceless Explainer Video (heygen-com/hyperframes, 59k stars) and Video Understand (calesthio/OpenMontage, 66k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uist 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.