Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community…
MITAuto-check passed
Install Nsdi Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-camera-ready --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/NSDI-Skills/skills/nsdi-camera-ready .claude/skills/nsdi-camera-ready && 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 "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .claude/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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/NSDI-Skills/skills/nsdi-camera-readyType 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 nsdi-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-camera-ready --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/NSDI-Skills/skills/nsdi-camera-ready .agents/skills/nsdi-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .agents/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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 nsdi-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-camera-ready --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/NSDI-Skills/skills/nsdi-camera-ready .cursor/skills/nsdi-camera-ready && 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 "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .cursor/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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 NSDI-Skills/skills/nsdi-camera-ready--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 nsdi-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-camera-ready --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/NSDI-Skills/skills/nsdi-camera-ready .gemini/skills/nsdi-camera-ready && 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 "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .gemini/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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 nsdi-camera-readyInstalls 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 nsdi-camera-ready -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/NSDI-Skills/skills/nsdi-camera-ready .github/skills/nsdi-camera-ready && 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 "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .github/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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 nsdi-camera-ready -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 nsdi-camera-ready --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/NSDI-Skills/skills/nsdi-camera-ready .opencode/skills/nsdi-camera-ready && 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 "nsdi-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-camera-ready into .opencode/skills/nsdi-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-camera-ready", 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
nsdi-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 695 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community…
- Works in 3 steps: Public release of the artifact… → Final PDF cites those live, permanent… → Artifact-badge evaluation proceeds on…
- Converting an NSDI acceptance into a published
- SKILL.md covers Deliverables and owners, The final PDF, One deadline, two prizes and Presenter and symposium duties, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nsdi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
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.
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
- Converting an NSDI acceptance into a published
- Presented paper — de-anonymizing within the same 12-page cap
- Meeting the final-papers deadline that also gates Community Award eligibility
- Designating the presenter
Example prompts
- “/nsdi-camera-ready”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Public release of the artifact repository/archive (with license and DOI) before
- Final PDF cites those live, permanent URLs.
- Artifact-badge evaluation proceeds on its own schedule; badge outcomes do not
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
Nsdi Camera Ready loads about 1.6k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 695 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). 695 words, ~1,612 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-camera-ready/SKILL.md (or your agent's skills folder).- name
- nsdi-camera-ready
- description
- Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
NSDI Camera-Ready
Acceptance starts a production pipeline with several deliverables owned by different people — the final PDF, the public artifact, the presenter designation, and the trip to the symposium. Facts below reflect the NSDI '26/'27 pages rendered on 2026-07-08; the '27 final-paper dates were not yet posted (待核实), so anchor every date to the notification email and the authors' instructions it links.
Deliverables and owners
| Deliverable | Owner to assign | Hard constraint |
|---|---|---|
| Final PDF | writing lead | same 12-page cap as submission |
| Public artifact release | artifact lead | before final-papers date for award eligibility |
| Production/copyright forms | corresponding author | per the authors' instructions |
| Presenter designation | presenting co-author | via the co-chairs' Presenter Information form |
| Travel, visa, registration | presenter | May 11-13, 2027, Providence, RI |
Assign these on notification day. Cohort timing matters here: a spring acceptance (notified July) has months of runway before the May symposium, while a fall acceptance (notified December) runs its production pipeline much closer to the event — same deliverables, tighter interleaving.
The final PDF
NSDI's cap is symmetric: final papers, like submissions, are limited to 12 pages including footnotes, figures, and tables, references and appendices beyond. There is no accepted-paper page bonus to spend, so camera-ready editing is substitution, not addition:
- De-anonymize: real names, affiliations, acknowledgments, funding — all inside the same 12 pages the anonymous version used, which usually costs a few lines; reclaim them from prose, not from evidence.
- Restore what blinding distorted: research-track papers that neutralized deployment context ("a large provider") may now name it — verify employer/legal sign-off on every restored detail, since this step is where confidentiality incidents happen.
- Real links replace anonymized ones: repository, DOI'd archive, dataset pages —
consistent with what the artifact ships (
nsdi-artifact-evaluation). - Honor the revision record: for papers accepted via one-shot revision, confirm every change promised in the change memo survived into the final text; shipping a final that quietly reverts a required fix betrays the reviewers who accepted on those terms.
- Then re-verify the page count — de-anonymization and shepherd-requested edits both nudge layout.
One deadline, two prizes
The final-papers deadline carries double weight at NSDI: it is the production cutoff, and it is the Community Award eligibility line — the award goes to the best paper whose code and/or dataset is public by that date. Sequence accordingly:
- Public release of the artifact repository/archive (with license and DOI) before the final-papers date.
- Final PDF cites those live, permanent URLs.
- Artifact-badge evaluation proceeds on its own schedule; badge outcomes do not retroactively fix a missed release date.
Show full SKILL.md (282 more words)Show less
Presenter and symposium duties
- Accepted papers designate one co-author as presenter via the Presenter Information form the program co-chairs distribute. Decide early — visa timelines for a US venue (Providence, RI for May 11-13, 2027) run months, and the presenter should ideally be the person who can answer testbed questions.
- Registration requirements, speaker discounts, and remote-presentation options for '27 are 待核实 — read the instructions-for-presenters page of the current edition rather than assuming either flexibility or rigidity.
- Spring-cohort papers surface on the public accepted-papers list well before the event; coordinate any press/blog timing with your institution against the venue's publication schedule, not against the symposium date alone.
Open access, and what it changes
USENIX proceedings are open access: the final PDF becomes a permanently free
download on usenix.org, joining a record where every prior NSDI paper is equally
free. Practical consequences:
- No paywalled-version hedging — the
usenix.orgPDF is the canonical citation target; sync any arXiv/preprint copy to the final text or clearly mark it stale. - The paper will be read far outside the reviewing community (operators, OSS users, hiring committees); the abstract and figure captions carry more weight than at paywalled venues.
- Slides and talk materials commonly join the presentation page; treat them as part of the paper's permanent public footprint.
Production checklist
[ ] Authors/affiliations restored; ORCID/name spellings confirmed by each coauthor
[ ] Acknowledgments + funding numbers complete (grant offices care)
[ ] 12-page cap re-verified after de-anonymization
[ ] Employer/legal sign-off on restored deployment details
[ ] Revision-memo promises intact in final text
[ ] Artifact public with license + DOI before final-papers date (award clock)
[ ] All URLs in the PDF resolve and are permanent
[ ] Copyright/production forms submitted per authors' instructions
[ ] Presenter designated via the form; travel/visa started
[ ] Metadata (title/abstract) identical across HotCRP, PDF, and artifact READMEAfter the symposium
The paper's public life is just beginning: keep the artifact's pinned dependencies buildable for at least the horizon on which one-shot-revision reviewers and follow-up work will consult it; route errata through the venue's published correction channel rather than silently editing preprint copies; and archive the talk recording/slides link alongside the repository README so the three public faces of the work — PDF, artifact, talk — reference each other.
Output format
[Deadline map] final-papers date + form dates (from notification email)
[PDF status] de-anonymized / cap verified / links live / memo honored
[Award clock] artifact public before final-papers date? y/n + date
[Presenter] designated? visa/travel risk level
[Open-access sync] preprint copies reconciled with canonical PDF
[Open items] owner -> item -> due date© 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 NSDI-Skills/skills/nsdi-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi Camera Ready 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 |
|---|---|---|---|---|---|---|
| Nsdi Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| Presentationsasgeirtj/system_prompts_leaks | 69k | — | ~858 | Automated safety check: Pass | CC0-1.0 | |
| AI Presenter VideoNousResearch/hermes-agent | 252k | — | ~2.3k | Automated safety check: Pass | MIT | |
| PresentationRightNow-AI/openfang | 18k | — | ~829 | Automated safety check: Pass | Apache-2.0 | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT |
Similar skills
- Official
Presentations
asgeirtj/system_prompts_leaks
Help choose a presentation's audience, story, outline, or use of evidence and visuals.
AI Presenter Video
NousResearch/hermes-agent
Produces a presenter-led video from a topic or script plus one authorized presenter image, with captions, lip-sync checks and acceptance reports.
Presentation
RightNow-AI/openfang
Presentation expert for slide structure, storytelling, visual design, and audience engagement
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
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 Nsdi Camera Ready
What does Nsdi Camera Ready do?
A skill your agent uses when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community…. Nsdi Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an NSDI acceptance into a published, presented paper — de-anonymizing within the same 12-page cap, meeting the final-papers deadline that also gates Community Award eligibility, designating the presenter, and landing in USENIX's open-access proceedings for the May symposium.
When should I use Nsdi Camera Ready?
Nsdi Camera Ready fits situations like: converting an NSDI acceptance into a published; presented paper — de-anonymizing within the same 12-page cap; meeting the final-papers deadline that also gates Community Award eligibility; designating the presenter.
How do I install Nsdi Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-camera-ready -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-camera-ready -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Nsdi Camera Ready 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 nsdi-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nsdi-camera-ready, .gemini/skills/nsdi-camera-ready, .github/skills/nsdi-camera-ready and .opencode/skills/nsdi-camera-ready in your project.
What does Nsdi Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Camera Ready is instructions for the agent only.
Does Nsdi Camera Ready 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 Nsdi Camera Ready 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 Nsdi Camera Ready use?
Nsdi Camera Ready 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 Nsdi Camera Ready use?
About 1.6k tokens (SKILL.md is roughly 6.4k 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 Nsdi Camera Ready?
Skills that share tags, products or a category with Nsdi Camera Ready: Convert (remotion-dev/remotion, 63k stars), Presentations (asgeirtj/system_prompts_leaks, 69k stars), AI Presenter Video (NousResearch/hermes-agent, 252k stars) and Presentation (RightNow-AI/openfang, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi Camera Ready?
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.