Usenix Security Symposium
franklee16/academic-research-skills
A skill your agent uses when targeting USENIX Security Symposium (USENIX Security) or deciding whether a computer-science manuscript fits this venue.
A skill your agent uses when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle…
MITAuto-check passed
Install Usenixsec Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .claude/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .claude/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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/USENIX-Security-Skills/skills/usenixsec-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 usenixsec-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .agents/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .agents/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .cursor/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .cursor/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 USENIX-Security-Skills/skills/usenixsec-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 usenixsec-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .gemini/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .gemini/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-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 usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .github/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .github/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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 usenixsec-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 usenixsec-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/USENIX-Security-Skills/skills/usenixsec-workflow .opencode/skills/usenixsec-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 "usenixsec-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-workflow into .opencode/skills/usenixsec-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-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
usenixsec-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 576 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 USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle…
- Works in 4 steps: pick the cycle → backward-plan from the registration date → assign the venue-specific risks → …
- Planning a USENIX Security Symposium project end to end — choosing between the two annual cycles
- SKILL.md covers Step 1: pick the cycle, Step 2: backward-plan from the…, Step 3: assign the… and Step 4: run the…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Usenixsec Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
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.
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 USENIX Security Symposium project end to end — choosing between the two annual cycles
- Mapping the registration-to-camera-ready calendar for a chosen cycle
- Sequencing artifact and ethics work early
- Coordinating a team across the multi-deadline Big-Four calendar
Example prompts
- “/usenixsec-workflow”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
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 Workflow loads about 1.3k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 576 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). 576 words, ~1,323 tokens.
Download SKILL.mdSave it as
.claude/skills/usenixsec-workflow/SKILL.md (or your agent's skills folder).- name
- usenixsec-workflow
- description
- Use when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
USENIX Security Workflow
USENIX Security runs two independent submission cycles per year, so "when do we submit?" is a real strategic choice, not a fixed date. This skill turns a target cycle into a dated backward plan and assigns owners to the venue-specific risks. Dates below are the '26/'27 cycle values read on 2026-07-08 (via search renderings; usenix.org direct fetch 403'd) — reconfirm against the live CFP.
Step 1: pick the cycle
| Consideration | Favors the earlier cycle | Favors the later cycle |
|---|---|---|
| Readiness | Evaluation truly done now | Needs one more experiment done right |
| Conference lead time | Cycle-1 accepts publish ~7 months pre-symposium | Cycle-2 accepts closer to the event |
| Competing deadlines | Avoids clashing with a CCS/S&P/NDSS date | Room to route a reject to the next venue |
| Resubmission runway | Reject still leaves the same-year second cycle open* | Reject pushes to next year |
*Subject to the cycle's resubmission-restriction text — the '26 CFP delegated
Cycle-2 reject restrictions to the '27 chairs, so verify before assuming a reject
can re-enter (see usenixsec-review-process).
Reference calendar (verify per cycle):
| Milestone | Sec '26 C1 | Sec '26 C2 | Sec '27 C1 | Sec '27 C2 |
|---|---|---|---|---|
| Registration | Aug 19 '25 | Jan 29 '26 | Aug 18 '26 | Jan 19 '27 |
| Submission | Aug 26 '25 | Feb 5 '26 | Aug 25 '26 | Jan 26 '27 |
| Early reject | Oct 7 '25 | Mar 17 '26 | 待核实 | 待核实 |
| Notification | Dec 4 '25 | May 14 '26 | 待核实 | 待核实 |
| Finals | Jan 15 '26 | Jun 11 '26 | 待核实 | 待核实 |
| Symposium | Aug 12–14 '26 (Baltimore) | Aug 11–13 '27 (Denver) |
Step 2: backward-plan from the registration date
Registration, not submission, is the first hard wall (it freezes title, abstract, authors, conflicts a week early). Plan backward from it:
T-12 wk Topic/venue fit locked (usenixsec-topic-selection); threat model drafted
T-10 wk Core experiments running; artifact repo scaffolded from day one
T-8 wk Related-work sweep of all Big-Four cycles closed since last pass
T-6 wk Adaptive-attacker / base-rate experiments (the ones that get demanded)
T-4 wk Full draft; Ethical Considerations + Open Science appendices written
T-3 wk Internal review + cold-reader pass on intro/threat model
T-2 wk Anonymization sweep; artifact anonymous mirror live and tested
T-1 wk REGISTRATION: freeze metadata; final polish only after this
T-0 Submit; re-download from HotCRP and read coldThe two moves teams most often leave too late: the adaptive-attacker experiment (defenses) and the ethics/disclosure timeline (live-system work). Both must start weeks before the deadline — a disclosure clock especially cannot be compressed, since vendors set the pace.
Show full SKILL.md (264 more words)Show less
Step 3: assign the venue-specific risks
| Risk | Owner | Early mitigation |
|---|---|---|
| Ethics/disclosure not started | PI | Open the disclosure and IRB threads at project start |
| Artifact not reproducible | Eng lead | Build the repo alongside the code, not after the paper |
| Threat model drifts from eval | First author | Adversary-consistency review at T-3 wk |
| Anonymity leak in artifact | Eng lead | Anonymous mirror built and log-out-tested by T-2 wk |
| Missed a fresh Big-Four paper | Reader | Dated literature sweep at T-8, re-sweep at T-2 |
Step 4: run the post-submission and post-decision phases
- Waiting: expect the early-reject gate first (a survivable-but-quiet signal), then full notification. Do not start the next paper assuming acceptance, but do keep the artifact repo warm — acceptance starts the Phase-1 clock immediately.
- Shepherd approval: scope the change list within 48 hours; it fits a two-week
window and no more (see
usenixsec-author-response). - Accept: run camera-ready and Phase-1 artifact availability in parallel — they
share a deadline (see
usenixsec-camera-ready). - Reject: mine the reviews, check the resubmission restriction, decide between the next USENIX cycle and a sibling venue with an open deadline.
Coordinating across the Big-Four calendar
Because USENIX Security, CCS, S&P, and NDSS each run multiple deadlines, a lab can keep a paper in motion nearly year-round — but a paper may sit under review at only one archival venue at a time. Maintain a shared deadline board and a one-in-one-out rule per paper; the dual-submission bar is real and enforced.
Reverify each cycle
- All dates in the table above ('27 review/notification/finals are 待核实).
- Symposium location and dates for your target year.
- Resubmission restrictions gating cycle-to-cycle and year-to-year moves.
Output format
[Cycle chosen] which cycle + why (readiness / lead time / clash / runway)
[Backward plan] dated milestones from registration wall
[Risk owners] the five venue risks assigned + early mitigations underway
[Post-decision] branch plan for accept / shepherd / reject© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Usenixsec 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 |
|---|---|---|---|---|---|---|
| Usenixsec Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Usenix Security Symposiumfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| Usenix Symposium On Networked Systems Design And Implementationfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| Usenix Symposium On Operating Systems Design And Implementationfranklee16/academic-research-skills | 223 | 1 repos | ~1.9k | Automated safety check: Pass | None | |
| Choosing Trend Or Slope ViewPostHog/posthog | 40k | — | ~947 | Automated safety check: Pass | Custom licence | |
| Choosing Causalpy Methodsbrycewang-stanford/Auto-Empirical-Research-Skills | 4.5k | — | ~807 | Automated safety check: Pass | Custom licence |
Similar skills
Usenix Symposium On Networked Systems Design And Implementation
franklee16/academic-research-skills
A skill your agent uses when targeting USENIX Symposium on Networked Systems Design and Implementation (NSDI) or deciding whether a computer-science manuscript fits this venue.
Usenix Symposium On Operating Systems Design And Implementation
franklee16/academic-research-skills
A skill your agent uses when targeting USENIX Symposium on Operating Systems Design and Implementation (OSDI) or deciding whether a computer-science manuscript fits this venue.
- Official
Choosing Trend Or Slope View
PostHog/posthog
Clarify how to visualize change over a time range before building a trend.
Choosing Causalpy Methods
brycewang-stanford/Auto-Empirical-Research-Skills
Choose the appropriate CausalPy experiment class from a causal question, data structure, treatment assignment, and identification assumptions.
Symposium
symposium-dev/symposium
Critical information that will help you with Rust development or information about Rust crates.
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 Usenixsec Workflow
What does Usenixsec Workflow do?
A skill your agent uses when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle…. Usenixsec Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
When should I use Usenixsec Workflow?
Usenixsec Workflow fits situations like: planning a USENIX Security Symposium project end to end — choosing between the two annual cycles; mapping the registration-to-camera-ready calendar for a chosen cycle; sequencing artifact and ethics work early; coordinating a team across the multi-deadline Big-Four calendar.
How do I install Usenixsec Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-workflow -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Usenixsec Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-workflow -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-workflow in your project. Codex loads it when a task matches its description.
Can I use Usenixsec 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 usenixsec-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/usenixsec-workflow, .gemini/skills/usenixsec-workflow, .github/skills/usenixsec-workflow and .opencode/skills/usenixsec-workflow in your project.
What does Usenixsec Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Usenixsec Workflow is instructions for the agent only.
Does Usenixsec 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 Usenixsec 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 Usenixsec Workflow use?
Usenixsec 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 Usenixsec Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.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 Usenixsec Workflow?
Skills that share tags, products or a category with Usenixsec Workflow: Usenix Security Symposium (franklee16/academic-research-skills, 223 stars), Usenix Symposium On Networked Systems Design And Implementation (franklee16/academic-research-skills, 223 stars), Usenix Symposium On Operating Systems Design And Implementation (franklee16/academic-research-skills, 223 stars) and Choosing Trend Or Slope View (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usenixsec 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.