Deepsec Documentation Guide
vercel-labs/deepsec
Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.
Agent skill
Usenixsec Review Process
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of…
Install Usenixsec Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-review-process --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/USENIX-Security-Skills/skills/usenixsec-review-process .claude/skills/usenixsec-review-process && 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 "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .claude/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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/USENIX-Security-Skills/skills/usenixsec-review-processType 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 usenixsec-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-review-process --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/USENIX-Security-Skills/skills/usenixsec-review-process .agents/skills/usenixsec-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .agents/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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 usenixsec-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-review-process --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/USENIX-Security-Skills/skills/usenixsec-review-process .cursor/skills/usenixsec-review-process && 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 "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .cursor/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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 USENIX-Security-Skills/skills/usenixsec-review-process--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 usenixsec-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-review-process --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/USENIX-Security-Skills/skills/usenixsec-review-process .gemini/skills/usenixsec-review-process && 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 "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .gemini/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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 usenixsec-review-processInstalls 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 usenixsec-review-process -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/USENIX-Security-Skills/skills/usenixsec-review-process .github/skills/usenixsec-review-process && 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 "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .github/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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 usenixsec-review-process -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 usenixsec-review-process --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/USENIX-Security-Skills/skills/usenixsec-review-process .opencode/skills/usenixsec-review-process && 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 "usenixsec-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-review-process into .opencode/skills/usenixsec-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-review-process", 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
usenixsec-review-process- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 555 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of…
- Works in 4 steps: Ethics adequacy is a gate, not a score.… → Threat-model realism. An attack needing… → Openness posture. Since the Open Science… → …
- Reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications
- SKILL.md covers The cycle pipeline, with '26…, The decision vocabulary…, What reviewers here weigh and Reading each email, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usenixsec Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of shepherd-approval acceptances, resubmission restrictions between cycles, and what each notification email means for planning.
Its SKILL.md is about 1.3k 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 Security. 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
- Reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications
- Multi-round reviewing
- The retirement of Major Revision in favor of shepherd-approval acceptances
- Resubmission restrictions between cycles
Example prompts
- “/usenixsec-review-process”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Ethics adequacy is a gate, not a score. Weak Ethical Considerations content
- Threat-model realism. An attack needing implausible attacker position, or a
- Openness posture. Since the Open Science policy, a vague availability story
- Measurement validity. Vantage-point, time-window, and ground-truth
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
Usenixsec Review Process loads about 1.3k tokens when it runs. Until then it costs about 82 tokens; SKILL.md has 555 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). 555 words, ~1,338 tokens.
Download SKILL.mdSave it as
.claude/skills/usenixsec-review-process/SKILL.md (or your agent's skills folder).- name
- usenixsec-review-process
- description
- Use when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of shepherd-approval acceptances, resubmission restrictions between cycles, and what each notification email means for planning.
USENIX Security Review Process
USENIX Security reviews in two annual cycles, each a self-contained pipeline from registration to notification. The '26 cycle mechanics below were read from usenix.org pages on 2026-07-08 (via search renderings; direct fetch 403'd), with the '25 reviewing-model page as documented history. The '27 mechanics under chairs Adam Doupé (Arizona State) and Andrei Sabelfeld (Chalmers) are only partially posted — treat everything here as one venue-generation's snapshot.
The cycle pipeline, with '26 dates as the worked example
| Stage | Cycle 1 ('26) | Cycle 2 ('26) | What is happening |
|---|---|---|---|
| Registration | Aug 19, 2025 | Jan 29, 2026 | HotCRP record frozen; bidding data set |
| Submission | Aug 26, 2025 | Feb 5, 2026 | Format/policy screening begins |
| Early reject | Oct 7, 2025 | Mar 17, 2026 | Bottom of the pool exits after first-round reads |
| Final notification | Dec 4, 2025 | May 14, 2026 | Accept / shepherd-approval / reject |
| Finals due | Jan 15, 2026 | Jun 11, 2026 | Shepherding + Phase-1 AE complete |
The '25 model (last fully published) shows the shape inside those windows: two first-round reviews; online discussion; survivors gain two more reviews in round two; authors respond; the committee discusses to a decision. Expect roughly that structure until the current cycle's reviewing-model page says otherwise (待核实 for '27).
The decision vocabulary changed — don't plan on 2025 rules
Through '25, USENIX Security ran an Accept / Invited Major Revision / Reject scheme, where a major revision returned to the same reviewers in a later cycle. The '26 CFP retired major revisions. The current outcomes:
- Accept — proceed to camera-ready and mandatory artifact-availability check.
- Accepted on Shepherd Approval — the committee wants the paper conditional on changes a two-week shepherding pass can hold: clarifications, explicit limitations, calibrated claims. Not a lane for new experiments.
- Early reject / reject — out of the cycle. Whether and when the work may return is governed by per-year resubmission restrictions; the '26 CFP delegated restrictions on its Cycle-2 rejects to the '27 chairs. Always check the current restriction text before queuing a resubmission — this is the venue's most frequently misremembered rule.
Strategic consequence: the paper must be finished at submission. The old major-revision safety net — submit at 85% and repair through revision — no longer exists; its replacement (shepherding) fixes prose, not evidence.
Show full SKILL.md (194 more words)Show less
What reviewers here weigh
Beyond ordinary top-venue novelty/rigor screens, this committee applies filters that surprise authors from adjacent fields:
- Ethics adequacy is a gate, not a score. Weak Ethical Considerations content can trigger required revisions mid-review or sink the paper regardless of technique (the ethics guidelines page is explicit that expectations bind).
- Threat-model realism. An attack needing implausible attacker position, or a defense evaluated only against non-adaptive adversaries, loses reviewers who ask "who does this actually affect?"
- Openness posture. Since the Open Science policy, a vague availability story is a review-visible weakness, not a post-acceptance detail.
- Measurement validity. Vantage-point, time-window, and ground-truth skepticism is a house specialty.
Reading each email
Early reject → 4 reviews were not spent on you; the pool's bottom tier.
Diagnose fit and framing, not just polish. Consider
usenixsec-topic-selection before re-targeting.
Reject (final) → full reviews attached; mine them for the resubmission and
check the current cross-cycle restriction before re-queuing.
Shepherd approval → acceptance-in-waiting; scope the change list within 48h
(see usenixsec-author-response).
Accept → the artifact clock is already running
(see usenixsec-camera-ready).Confidentiality and conduct
Submissions are confidential to the committee; reviewer identities are hidden; contacting reviewers or attempting to identify them is out of bounds. Conflicts declared at registration drive assignment — fabricating conflicts to dodge a skeptical expert is chair-level misconduct at USENIX as elsewhere.
Reverify each cycle
- The current reviewing-model description, response phase, and round structure.
- Decision categories and shepherding window ('27 待核实).
- Resubmission restrictions between cycles and across years.
- Early-reject and notification dates for the live cycle.
Output format
[Cycle position] stage now + next date that matters
[Decision model] outcomes in force this cycle (verified on: <date>)
[Exposure] ethics gate / threat-model realism / openness / measurement validity
[Plan] action per possible outcome, with resubmission-restriction check© 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 USENIX-Security-Skills/skills/usenixsec-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Usenixsec Review Process 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 |
|---|---|---|---|---|---|---|
| Usenixsec Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Deepsec Documentation Guidevercel-labs/deepsec | 8.1k | — | ~956 | Automated safety check: Pass | Apache-2.0 | |
| Skill Scannergetsentry/skills | 1k | 4 repos | ~2.5k | Automated safety check: Warn | Apache-2.0 | |
| Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit | 481 | 1 repos | ~3.3k | Automated safety check: Pass | None | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Shiro Attack CLISummerSec/ShiroAttack2 | 2.6k | — | ~945 | Automated safety check: Pass | MIT |
Similar skills
- Official
- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
Serenity Aleabitoreddit
yan-labs/serenity-aleabitoreddit
Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.
- Official
Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Shiro Attack CLI
SummerSec/ShiroAttack2
当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…
Cve Remediation
rundeck/rundeck
Verify if a CVE affects the project and remediate it. An agent skill from rundeck/rundeck.
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 Usenixsec Review Process
What does Usenixsec Review Process do?
A skill your agent uses when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of…. Usenixsec Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of shepherd-approval acceptances, resubmission restrictions between cycles, and what each notification email means for planning.
When should I use Usenixsec Review Process?
Usenixsec Review Process fits situations like: reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications; multi-round reviewing; the retirement of Major Revision in favor of shepherd-approval acceptances; resubmission restrictions between cycles.
How do I install Usenixsec Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-review-process -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Usenixsec Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-review-process -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-review-process in your project. Codex loads it when a task matches its description.
Can I use Usenixsec Review Process 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 usenixsec-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/usenixsec-review-process, .gemini/skills/usenixsec-review-process, .github/skills/usenixsec-review-process and .opencode/skills/usenixsec-review-process in your project.
What does Usenixsec Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Usenixsec Review Process is instructions for the agent only.
Does Usenixsec Review Process 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 Usenixsec Review Process 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 Usenixsec Review Process use?
Usenixsec Review Process 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 Usenixsec Review Process use?
About 1.3k tokens (SKILL.md is roughly 5.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 Usenixsec Review Process?
Skills that share tags, products or a category with Usenixsec Review Process: Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars), Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 481 stars) and Security Alert Triage (elastic/agent-skills, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usenixsec Review Process?
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.