Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current…
Install Nsdi Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-related-work .claude/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .claude/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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/NSDI-Skills/skills/nsdi-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 nsdi-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-related-work .agents/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .agents/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-related-work .cursor/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .cursor/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 NSDI-Skills/skills/nsdi-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 nsdi-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills nsdi-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/NSDI-Skills/skills/nsdi-related-work .gemini/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .gemini/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-related-work .github/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .github/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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 nsdi-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 nsdi-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/NSDI-Skills/skills/nsdi-related-work .opencode/skills/nsdi-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 "nsdi-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NSDI-Skills/skills/nsdi-related-work into .opencode/skills/nsdi-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nsdi-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
nsdi-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 784 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current…
- Works in 4 steps: At project start: lanes 1-3 in depth;… → Four weeks before the gate: re-sweep the… → At bibliography freeze: run the… → …
- Verifying venues against dblp and open-access USENIX proceedings
- SKILL.md covers The lanes an NSDI reviewer…, Verification: the venue must…, Positioning moves that work at… and Double-blind mechanics for…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nsdi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.
Its SKILL.md is about 1.7k 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, Citation management and Positioning and messaging. 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
- Verifying venues against dblp and open-access USENIX proceedings
- Handling self-citations and concurrent submissions under double-blind rules
Example prompts
- “/nsdi-related-work”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- At project start: lanes 1-3 in depth; identify the two or three systems the
- Four weeks before the gate: re-sweep the current edition's earlier cohort
- At bibliography freeze: run the venue-verification pass below; fix
- In a one-shot revision: re-check whether the reviewers' cited omissions have
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 bash).
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 Related Work loads about 1.7k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 784 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). 784 words, ~1,724 tokens.
Download SKILL.mdSave it as
.claude/skills/nsdi-related-work/SKILL.md (or your agent's skills folder).- name
- nsdi-related-work
- description
- Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.
NSDI Related Work
Related work at NSDI answers one reviewer question: what does this design let us do that the systems we already have do not? Coverage gaps read as either ignorance or evasion, and the venue's open-access record removes every excuse for both.
The lanes an NSDI reviewer expects swept
| Lane | Where it lives | What must be said about it |
|---|---|---|
| Direct competitors | NSDI, SIGCOMM, OSDI, SOSP | Mechanism-level delta, ideally measured head-to-head |
| Same problem, other stack layer | SIGCOMM (protocol), OSDI/SOSP (host), FAST (storage) | Why this layer is the right place to solve it |
| Same technique, other domain | broad systems + ML-systems venues | What the networked setting breaks or changes |
| Measurement/characterization basis | IMC, NSDI measurement papers | Which observed phenomena motivated the design |
| Deployed/industrial precedent | operational-track papers, provider tech reports | What production experience the design inherits or contradicts |
| Early/idea-stage neighbors | HotNets, frontiers-track papers | That the idea's grown-up form differs from the sketch |
Both cohorts of the current edition count as literature: NSDI posts spring
accepted-paper lists months before the symposium (e.g.,
usenix.org/conference/nsdi26/spring-accepted-papers), so "it wasn't published yet"
fails for a fall submission when the spring list was public at deadline time. Sweep
the sibling deadlines too — SIGCOMM's accepted list frequently contains the closest
neighbor of an NSDI submission.
Verification: the venue must be proven
Systems folklore misfiles its classics; citing Raft "at NSDI" or B4 "from NSDI"
signals secondhand reading (Raft is USENIX ATC 2014, B4 is SIGCOMM 2013 — see the
guard list in
../../resources/exemplars/library.md). Every
NSDI paper since the venue began is a free PDF on usenix.org, and dblp's
conf/nsdi stream gives the authoritative edition/pages. Verify before the
bibliography freezes:
# Cross-check claimed venues in the .bib against dblp keys / USENIX URLs
grep -E '^@' paper.bib | wc -l # inventory
grep -A3 -iE 'booktitle.*(nsdi|sigcomm|osdi|sosp)' paper.bib | head -40
# For each NSDI claim: the usenix.org/conference/nsdi<yy>/presentation/<key>
# page or the dblp record must exist. No render, no citation-as-NSDI.Read the PDF of any paper you compare against quantitatively. Comparing against a system's abstract is how "prior work cannot handle churn" ends up in front of the reviewer who wrote the churn section.
Positioning moves that work at this venue
- Delta by mechanism, not by adjective. "X batches at the NIC; we batch at the RPC layer, which preserves per-request deadlines" beats "unlike X, our approach is more flexible."
- Concede the overlap, then locate the divergence. NSDI reviewers usually know the neighbor papers personally; a generous one-clause summary of the competitor buys credibility for the distinction that follows.
- Use operational precedent as evidence, not decoration. If a provider's operational-track paper reports the failure mode your design removes, that citation is motivation-grade, not related-work filler.
- Position against the measurement literature. A design justified by workload properties should cite where those properties were measured — or measure them in §2.
Double-blind mechanics for citations
- Self-citations stay, in third person. "We extend Ballast [12]" reveals; "This work extends Ballast [12]" written as if by strangers does not. Omitting your own prior paper to hide identity is explicitly against the CFP.
- Concurrent NSDI submissions are cited with the CFP's fixed sentence: "Under submission. Details omitted for double-blind reviewing."
- Tech reports and arXiv versions of your own work: cite in third person like any prior art; do not link author-revealing artifacts in the text.
- Operational-track nuance: the anonymization exception covers your paper's system and company names — it does not license identifying the author list through possessive phrasing.
Show full SKILL.md (264 more words)Show less
Sequencing the sweep across the two-deadline year
Because NSDI publishes cohort lists mid-cycle, the sweep has a rhythm:
- At project start: lanes 1-3 in depth; identify the two or three systems the
paper must beat or distinguish, since they shape the evaluation
(
nsdi-experiments). - Four weeks before the gate: re-sweep the current edition's earlier cohort list and the most recent SIGCOMM/OSDI/SOSP programs; new neighbors get a mechanism-delta sentence, not a panicked rewrite.
- At bibliography freeze: run the venue-verification pass below; fix misattributions before reviewers find them.
- In a one-shot revision: re-check whether the reviewers' cited omissions have
themselves been published since — the same reviewers will notice both presence
and absence (
nsdi-author-response).
Failure patterns
- The wall of one-line citations ("Much work has studied datacenter transport [3-19]") — coverage theater with no deltas.
- Comparing only against academic prototypes when a widely deployed system solves an adjacent problem — reviewers from industry will supply the omission.
- Treating a spring-cohort paper of the same edition as invisible.
- Venue misattribution in the bibliography — cheap to fix, expensive in credibility.
- A related-work section that never mentions the paper's own limits relative to prior work; positioning is bidirectional.
Where the section lives
NSDI drafts split positioning across two homes, both inside the 12 pages: a short contrast in the introduction (the two nearest neighbors, one delta sentence each) and the fuller section — conventionally late, before or after discussion — carrying the lane-by-lane sweep. Whichever home a comparison occupies, the quantitative version belongs in the evaluation: a related-work sentence claiming superiority that §6 never measures is a self-inflicted reviewer question.
Output format
[Lane coverage] table lane -> covered / gap (paper to add)
[Nearest neighbor] <paper, venue-verified> + mechanism delta
[Cohort sweep] current-edition spring list checked? sibling deadlines?
[Verification] # citations venue-proven / total NSDI-venue claims
[Blind check] self-cites third-person? concurrent-submission wording?
[Fix list] ordered corrections before bibliography freeze© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Nsdi 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 |
|---|---|---|---|---|---|---|
| Nsdi Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| 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 |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
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.
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 Nsdi Related Work
What does Nsdi Related Work do?
A skill your agent uses when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current…. Nsdi Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when positioning an NSDI submission against the networked-systems literature — covering the NSDI/SIGCOMM/OSDI/SOSP lanes plus both accepted-paper cohorts of the current edition, verifying venues against dblp and open-access USENIX proceedings, and handling self-citations and concurrent submissions under double-blind rules.
When should I use Nsdi Related Work?
Nsdi Related Work fits situations like: verifying venues against dblp and open-access USENIX proceedings; handling self-citations and concurrent submissions under double-blind rules.
How do I install Nsdi Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-related-work -a claude-code`. Or copy the skill folder (NSDI-Skills/skills/nsdi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/nsdi-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Nsdi Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill nsdi-related-work -a codex`. Or copy the skill folder (NSDI-Skills/skills/nsdi-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/nsdi-related-work in your project. Codex loads it when a task matches its description.
Can I use Nsdi 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 nsdi-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/nsdi-related-work, .gemini/skills/nsdi-related-work, .github/skills/nsdi-related-work and .opencode/skills/nsdi-related-work in your project.
What does Nsdi Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Nsdi Related Work is instructions for the agent only.
Does Nsdi Related Work 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 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 Nsdi Related Work use?
Nsdi 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 Nsdi Related Work use?
About 1.7k tokens (SKILL.md is roughly 6.9k 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 Related Work?
Skills that share tags, products or a category with Nsdi Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nsdi 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.