File Uploads
davila7/claude-code-templates
Expert at handling file uploads and cloud storage. An agent skill from davila7/claude-code-templates.
A skill your agent uses when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap…
MITAuto-check passed
Install Nsdi Submission
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-submission -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-submission --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-submission .claude/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .claude/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submissionType 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-submission -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-submission --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-submission .agents/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .agents/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submission -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-submission --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-submission .cursor/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .cursor/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submission--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-submission -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-submission --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-submission .gemini/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .gemini/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submissionInstalls 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-submission -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-submission .github/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .github/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submission -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-submission --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-submission .opencode/skills/nsdi-submission && 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-submission" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-submission into .opencode/skills/nsdi-submission/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-submission", 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-submission- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 692 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap…
- Works in 5 steps: T-8 days: fall HotCRP account, abstract… → T-7 (Sept 10): abstract registered;… → T-2: content freeze; Gates 1-2 executed… → …
- Running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site
- SKILL.md covers Gate 0: the right site, the…, Gate 1: format, Gate 2: blindness, per track and Gate 3: policy, plus 3 more sections
- Calls pdftotext
What it does
Nsdi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap with references and appendices outside it, track-dependent anonymization, the eight-paper author cap, and the resubmission-ban check.
Its SKILL.md is about 1.5k 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
- Running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site
- 11:59 pm US Eastern cutoffs
- The 12-page cap with references and appendices outside it
- Track-dependent anonymization
Example prompts
- “/nsdi-submission”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- T-8 days: fall HotCRP account, abstract fields drafted, conflicts entered.
- T-7 (Sept 10): abstract registered; track locked deliberately.
- T-2: content freeze; Gates 1-2 executed on the near-final PDF.
- T-1: coauthor sign-off; HotCRP title/abstract verbatim-match the PDF.
- T-0 (Sept 17): upload, status complete, then download the receipt copy and
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
Shell commands in SKILL.md call:
pdftotext
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 Submission loads about 1.5k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 692 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). 692 words, ~1,541 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-submission/SKILL.md (or your agent's skills folder).- name
- nsdi-submission
- description
- Use when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap with references and appendices outside it, track-dependent anonymization, the eight-paper author cap, and the resubmission-ban check.
NSDI Submission
The audit below is ordered by irreversibility: calendar errors first, then format,
then blindness, then policy. Numbers are the NSDI '27 cycle as rendered on
2026-07-08; the fall HotCRP /deadlines page outranks everything here.
Gate 0: the right site, the right clock
NSDI runs a separate HotCRP instance per deadline
(nsdi27spring.usenix.hotcrp.com, nsdi27fall...). Uploading to a stale spring site
bookmarked in March is a real failure mode. For the '27 fall gate:
- Abstracts (title, author list, track, conflicts): September 10, 2026.
- Full papers: September 17, 2026.
- Both 11:59 pm US EDT — an Eastern-US midnight, not AoE and not the Pacific cutoff NSDI '26 used. Same-named deadlines moved time zones between editions; compute each coauthor's local equivalent from the HotCRP page, not from memory.
The abstract gate is a prerequisite: no registered abstract, no paper upload a week later. Register even if 60% sure — withdrawing is free, materializing an unregistered paper is impossible.
Gate 1: format
| Item | '27 rule | Audit action |
|---|---|---|
| Body | ≤ 12 pages incl. footnotes, figures, tables | Count on the compiled PDF |
| References | extra pages allowed | Nothing else hiding among them |
| Appendices | extra pages allowed after references | Nothing load-bearing inside (nsdi-supplementary) |
| Template/fonts | current USENIX template, unmodified | Diff class options against the distributed file |
| Track | research / operational / frontiers | Matches the evidence actually in the paper |
Page-cap pressure at NSDI is figure pressure — figures count. The fix is content
triage, never \vspace surgery or font tricks; production chairs and reviewers both
notice geometry games.
Gate 2: blindness, per track
Baseline sweep for all tracks — no author names, affiliations, acknowledgments, or funding numbers; self-citations in third person; references never omitted for anonymity; concurrent NSDI submissions cited with the CFP's fixed sentence ("Under submission. Details omitted for double-blind reviewing.").
Then the fork:
- Research/frontiers: deployment context must not identify the institution by implication. A trace "from our global CDN" plus a author-count and a topology detail can triangulate to one company; neutralize to scale-descriptive terms.
- Operational systems: the CFP relaxes object anonymity — real system names, company names, and links may stay because judging real-world use requires them — while author names stay hidden. Do not import this exception into a research-track paper.
# Mechanical pass on the exact upload candidate
pdftotext final.pdf - | grep -nEi '(acknowledg|funded by|grant|@[a-z]+\.(com|edu))' | head
pdfinfo final.pdf | grep -Ei 'author|creator' # PDF metadata identity
grep -rnEi '(github\.com/[a-z0-9-]+|/home/|/Users/)' *.tex figures/ | head
# research track only: search for your institution's giveaway nouns
pdftotext final.pdf - | grep -niE 'ourcorp|internal-codename' | headMechanical passes catch strings; only a human pass catches implication. Have a non-author read the PDF asking one question: who wrote this?
Show full SKILL.md (313 more words)Show less
Gate 3: policy
- Dual submission / prior publication / plagiarism: prohibited by USENIX; concurrent review anywhere else is disqualifying, and the ban survives notification-date arithmetic ("they'd decide before NSDI" does not help).
- Resubmission ban: if this work was rejected (without a revision option) from
the immediately preceding NSDI deadline, it cannot enter this one. Check the
paper's own decision history — spring '27 reject means no fall '27 entry
(
nsdi-review-process). - One-shot revisions enter with their auxiliary packet complete
(
nsdi-author-response); an ordinary-looking resubmission that ignores its issue list is terminally rejected. - Author cap: at most eight submissions per author across all '27 deadlines — reconcile the group's ledger, counting spring entries.
- AI use: grammar-and-clarity assistance on human-written text is endorsed; anything more, ask the co-chairs before the deadline, not after.
- Ethics: measurement of real users or third-party infrastructure needs its handling addressed in the paper; the '27 CFP's exact ethics wording is 待核实 — read that section live.
HotCRP form fields deserve the same audit as the PDF
Reviewers meet the form before the paper: title and abstract must match the PDF verbatim (drift reads as sloppiness and can confuse bidding); topic selections route the paper toward the sub-community you want reviewing it — choose for the reviewer profile, not maximal coverage; the full author list is entered at abstract time for conflict computation even though the PDF hides it, and late author additions after review assignment are a co-chairs-level incident. Declare conflicts by the site's definitions, completely and no wider.
Final sequence
- T-8 days: fall HotCRP account, abstract fields drafted, conflicts entered.
- T-7 (Sept 10): abstract registered; track locked deliberately.
- T-2: content freeze; Gates 1-2 executed on the near-final PDF.
- T-1: coauthor sign-off; HotCRP title/abstract verbatim-match the PDF.
- T-0 (Sept 17): upload, status complete, then download the receipt copy and read it — the uploaded bytes, not the local file, are the submission.
Output format
[Clock] site URL + local-time cutoffs confirmed from /deadlines
[Gate 1] pages / template / track — pass or blocker
[Gate 2] mechanical findings + human-pass verdict (track-appropriate)
[Gate 3] dual-sub / ban / cap / AI / ethics — each cleared or flagged
[Receipt] uploaded PDF re-read? fields match?
[Blockers] ordered, with owner and time cost© 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-submission of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi Submission 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 Submission this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| File Uploadsdavila7/claude-code-templates | 33k | 4 repos | ~238 | Automated safety check: Pass | MIT | |
| File Upload Accessibilitythedaviddias/Front-End-Checklist | 74k | — | ~418 | Automated safety check: Pass | MIT | |
| Upload R2remotion-dev/remotion | 63k | — | ~535 | Automated safety check: Notes | Custom licence | |
| Hunt File Uploadsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Upload Element Previewsremotion-dev/remotion | 63k | — | ~265 | Automated safety check: Pass | Custom licence |
Similar skills
File Upload Accessibility
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Make file uploads accessible.
- Official
Upload R2
remotion-dev/remotion
Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs.
Hunt File Upload
sickn33/agentic-awesome-skills
Hunt file upload bugs
- Official
Upload Element Previews
remotion-dev/remotion
Upload a Remotion Element's preview assets to remotion.media and replace local preview URLs.
R2 Upload
zebbern/claude-code-guide
Upload files to Cloudflare R2, AWS S3, or any S3-compatible storage (like MinIO) and generate secure, time-limited presigned download links with configurable expiration, typically set to 5 minutes.
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 Submission
What does Nsdi Submission do?
A skill your agent uses when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap…. Nsdi Submission is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site, 11:59 pm US Eastern cutoffs, the 12-page cap with references and appendices outside it, track-dependent anonymization, the eight-paper author cap, and the resubmission-ban check.
When should I use Nsdi Submission?
Nsdi Submission fits situations like: running the final pre-upload audit of an NSDI submission — the abstract-then-paper week on the per-deadline HotCRP site; 11:59 pm US Eastern cutoffs; the 12-page cap with references and appendices outside it; track-dependent anonymization.
How do I install Nsdi Submission in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-submission -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-submission in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-submission in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Submission in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-submission -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-submission in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-submission in your project. Codex loads it when a task matches its description.
Can I use Nsdi Submission 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-submission -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-submission, .gemini/skills/nsdi-submission, .github/skills/nsdi-submission and .opencode/skills/nsdi-submission in your project.
What does Nsdi Submission need to run?
Going by SKILL.md and its folder, Nsdi Submission needs the command-line tools its instructions call (pdftotext).
Does Nsdi Submission 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 Submission 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 Submission use?
Nsdi Submission 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 Submission use?
About 1.5k tokens (SKILL.md is roughly 6.2k 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 Submission?
Skills that share tags, products or a category with Nsdi Submission: File Uploads (davila7/claude-code-templates, 33k stars), File Upload Accessibility (thedaviddias/Front-End-Checklist, 74k stars), Upload R2 (remotion-dev/remotion, 63k stars) and Hunt File Upload (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi Submission?
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.