Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
A skill your agent uses when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions…
Install Usenixsec Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-related-work --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-related-work .claude/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .claude/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-related-work --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-related-work .agents/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .agents/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-related-work --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-related-work .cursor/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .cursor/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills usenixsec-related-work --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-related-work .gemini/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .gemini/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .github/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/usenixsec-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/USENIX-Security-Skills/skills/usenixsec-related-work into .opencode/skills/usenixsec-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "usenixsec-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 648 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions…
- Works in 3 steps: Threat-model delta — "X defends against… → Scale/vantage delta — "prior… → Evidence delta — "Y's evaluation is…
- Positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences
- SKILL.md covers The coverage map reviewers apply, Freshness under a two-cycle…, Differentiation that survives… and Double-blind citation mechanics, plus 3 more sections
- Reaches usenix.org
What it does
Usenixsec Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions across the multi-cycle calendar, citing your own work double-blind, and using USENIX's open-access proceedings for verification.
Its SKILL.md is about 1.4k 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 Research & Science, covering Literature review. 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
- Positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences
- Handling concurrent submissions across the multi-cycle calendar
- Citing your own work double-blind
- Using USENIXs open-access proceedings for verification
Example prompts
- “/usenixsec-related-work”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Threat-model delta — "X defends against a network adversary; we handle a
- Scale/vantage delta — "prior measurements covered one ccTLD from a single
- Evidence delta — "Y's evaluation is simulation-only; we demonstrate the
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bibtex).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
usenix.org
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 Related Work loads about 1.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 648 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). 648 words, ~1,405 tokens.
Download SKILL.mdSave it as
.claude/skills/usenixsec-related-work/SKILL.md (or your agent's skills folder).- name
- usenixsec-related-work
- description
- Use when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions across the multi-cycle calendar, citing your own work double-blind, and using USENIX's open-access proceedings for verification.
USENIX Security Related Work
Related work at USENIX Security is an adversarial exercise: the committee contains people who wrote the nearest prior papers, and the multi-cycle Big-Four calendar means the nearest prior paper may be four months old. This skill covers coverage, differentiation, and the venue's citation mechanics.
The coverage map reviewers apply
| Lane | Where it lives | The question your text must answer |
|---|---|---|
| Big-Four security | USENIX Security, IEEE S&P, ACM CCS, NDSS | Same problem, same class of technique — what's new here? |
| Specialty security | PETS, SOUPS, RAID, ACSAC, WOOT, DIMVA, ESORICS | Did the niche community already do this at smaller scale? |
| Adjacent systems/ML | OSDI/SOSP, SIGCOMM/IMC, NeurIPS/ICML | Is the "security" contribution a re-badged systems or ML result? |
| Industry/offense track record | Black Hat/DEF CON talks, vendor blogs, CVE history | Do practitioners already know this? (Reviewers here often do) |
| Preprints and the cycle pipeline | arXiv, prior cycles' accepted-paper lists | What landed in the last 6–12 months that you must acknowledge? |
The fourth lane is distinctive: at this venue, an attack "known in the community" via a conference talk or advisory — even without an academic paper — weakens a novelty claim, and reviewers will cite the talk. Search offensive-industry sources, not just DBLP.
Freshness under a two-cycle regime
With USENIX Security itself, CCS, NDSS, and S&P all running multiple deadlines, the relevant literature refreshes roughly every quarter. Concretely:
- Sweep the accepted-papers pages of every Big-Four cycle that concluded after your last literature pass (e.g., a Sec '27 Cycle-1 submission in Aug 2026 should have digested Sec '26 Cycle-2 acceptances announced May 2026).
- USENIX helps you here: its proceedings are open access on usenix.org, so verification against the actual PDF costs nothing. Do the same via each venue's accepted-paper listings.
- Genuinely concurrent work (public after your submission, or within the same cycle window) merits acknowledgment, not differentiation-by-contortion. Reviewers know the calendar; say "concurrently and independently" and state the factual differences.
Differentiation that survives expert readers
Comparison tables of checkmarks read as advertising. The pattern that works here is mechanism-level: state what the prior system assumed or measured, then the delta. Three useful framings:
- Threat-model delta — "X defends against a network adversary; we handle a co-resident one, which breaks X's core assumption (shared cache is trusted)."
- Scale/vantage delta — "prior measurements covered one ccTLD from a single vantage; we cover 214 TLDs from 14 vantage points, and Section 6 shows the single-vantage view misestimates prevalence by 3×."
- Evidence delta — "Y's evaluation is simulation-only; we demonstrate the attack end-to-end on production hardware."
If the honest delta is "same idea, better engineering," consider whether the
contribution framing should change before the related-work section does (see
usenixsec-topic-selection).
Show full SKILL.md (210 more words)Show less
Double-blind citation mechanics
Cite your own prior work in the third person as if written by strangers; the '26 CFP names first-person self-reference as an anonymity violation. When a paper builds so directly on your unpublished or just-published system that third person fails, the mitigation hierarchy is: cite an anonymized tech report in the artifact mirror; failing that, consult the chairs — never silently omit a paper reviewers will know exists, since a missing obvious citation both distorts positioning and fingerprints the authors.
@inproceedings{example-sec24,
author = {Doe, Jane and Roe, Riley},
title = {Sample: What a USENIX Security Reference Looks Like},
booktitle = {33rd USENIX Security Symposium (USENIX Security 24)},
year = {2024},
publisher = {USENIX Association},
url = {https://www.usenix.org/conference/usenixsecurity24/presentation/...}
}Verify metadata against the usenix.org presentation page or DBLP's conf/uss
stream; both were consistent sources historically (DBLP direct fetch 403'd in this
environment on 2026-07-08 — cross-check via search rendering if needed).
Placement and length
Related work usually closes the body (≈1 page of the 13). Two exceptions worth making: an attack paper whose novelty hinges on a subtle difference from a known technique should differentiate early, in the introduction; SoK-style framing (if pursued at all — check the current CFP for whether the venue solicits it, 待核实) makes the literature the paper's subject rather than its perimeter.
Reverify each cycle
- Accepted-paper lists of all Big-Four cycles concluded since the last sweep.
- Whether the current CFP says anything about citing concurrent work or preprints.
- Anonymity wording around self-citation.
Output format
[Coverage] five lanes swept, with dates of the last sweep per lane
[Nearest neighbors] top 3–5 with mechanism-level deltas drafted
[Concurrent] same-window items + acknowledgment wording
[Self-citations] third-person rewrite check: pass / violations listed© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Usenixsec Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Preprint Search on bioRxivLigphiDonk/Oh-my--paper | 739 | 12 repos | ~3.7k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence |
Similar skills
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Deep Research Workflow
TokenRhythm/opensquilla
Runs multi-round research in three stages with a persisted state file, evidence tracking and a long-form report with per-claim citations.
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 Related Work
What does Usenixsec Related Work do?
A skill your agent uses when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions…. Usenixsec Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions across the multi-cycle calendar, citing your own work double-blind, and using USENIX's open-access proceedings for verification.
When should I use Usenixsec Related Work?
Usenixsec Related Work fits situations like: positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences; handling concurrent submissions across the multi-cycle calendar; citing your own work double-blind; using USENIXs open-access proceedings for verification.
How do I install Usenixsec Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-related-work -a claude-code`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/usenixsec-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Usenixsec Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill usenixsec-related-work -a codex`. Or copy the skill folder (USENIX-Security-Skills/skills/usenixsec-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/usenixsec-related-work in your project. Codex loads it when a task matches its description.
Can I use Usenixsec Related Work 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-related-work -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-related-work, .gemini/skills/usenixsec-related-work, .github/skills/usenixsec-related-work and .opencode/skills/usenixsec-related-work in your project.
What does Usenixsec Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Usenixsec Related Work is instructions for the agent only.
Does Usenixsec Related Work access the network?
SKILL.md names 1 domain. In commands or code: usenix.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Usenixsec Related Work 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 Related Work use?
Usenixsec Related Work 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 Related Work use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Related Work?
Skills that share tags, products or a category with Usenixsec Related Work: Nature Paper Card (Yuan1z0825/nature-skills, 47k stars), Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars), Literature Review (neflibata-feng/MyArxiv-Agent, 126 stars) and Preprint Search on bioRxiv (LigphiDonk/Oh-my--paper, 739 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Usenixsec Related Work?
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.