Convert
remotion-dev/remotion
Start the local @remotion/convert app and open it in the Codex browser.
A skill your agent uses when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding…
MITAuto-check passed
Install Ndss Camera Ready
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-camera-ready -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-camera-ready --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/NDSS-Skills/skills/ndss-camera-ready .claude/skills/ndss-camera-ready && 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 "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .claude/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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/NDSS-Skills/skills/ndss-camera-readyType 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 ndss-camera-ready -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-camera-ready --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/NDSS-Skills/skills/ndss-camera-ready .agents/skills/ndss-camera-ready && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .agents/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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 ndss-camera-ready -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-camera-ready --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/NDSS-Skills/skills/ndss-camera-ready .cursor/skills/ndss-camera-ready && 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 "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .cursor/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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 NDSS-Skills/skills/ndss-camera-ready--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 ndss-camera-ready -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-camera-ready --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/NDSS-Skills/skills/ndss-camera-ready .gemini/skills/ndss-camera-ready && 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 "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .gemini/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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 ndss-camera-readyInstalls 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 ndss-camera-ready -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/NDSS-Skills/skills/ndss-camera-ready .github/skills/ndss-camera-ready && 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 "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .github/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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 ndss-camera-ready -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 ndss-camera-ready --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/NDSS-Skills/skills/ndss-camera-ready .opencode/skills/ndss-camera-ready && 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 "ndss-camera-ready" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-camera-ready into .opencode/skills/ndss-camera-ready/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-camera-ready", 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
ndss-camera-ready- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 442 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding…
- Converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions
- SKILL.md covers First, clear the decision's…, De-anonymize deliberately, Add earned artifact badges and Final production checklist, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Restoring disclosure specifics
What it does
Ndss Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding earned artifact badges, and meeting the Internet Society proceedings and camera-ready requirements by the January deadline.
Its SKILL.md is about 1.1k 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
- Converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions
- Restoring disclosure specifics
- Adding earned artifact badges
- Meeting the Internet Society proceedings and camera-ready requirements by the January deadline
Example prompts
- “/ndss-camera-ready”
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
Ndss Camera Ready loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 442 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). 442 words, ~1,134 tokens.
Download SKILL.mdSave it as
.claude/skills/ndss-camera-ready/SKILL.md (or your agent's skills folder).- name
- ndss-camera-ready
- description
- Use when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding earned artifact badges, and meeting the Internet Society proceedings and camera-ready requirements by the January deadline.
NDSS Camera-Ready
Acceptance at NDSS produces a paper the whole world reads for free: proceedings and talk videos are open access under the Internet Society, with no reader paywall and authors free to self-post. The camera-ready is therefore a public artifact, not an archival formality — and for many papers it must first discharge a revision condition. The 2027 camera-ready deadline is January 6, 2027 (CFP, checked 2026-07-08).
First, clear the decision's conditions
| Decision | Precondition to camera-ready |
|---|---|
| Accept | None — proceed to the checklist |
| Minor Revision | Make exactly the requested changes; a shepherd or the chairs confirm they are satisfactory |
| Major Revision (now accepted) | The re-review already judged the revision-task list fulfilled; carry those changes into the final version faithfully — do not quietly walk any of them back |
Treat any shepherd or revision-task list as binding text. Diff your final PDF against the committed changes item by item; a reviewer who wrote a task will look for it in the published paper, and its absence is the failure mode that follows a paper into print.
De-anonymize deliberately
Submission was double-blind; the camera-ready reverses it, and reversal is where mistakes enter:
- Add authors, affiliations, ORCIDs, and acknowledgments/funding in the template's fields.
- Restore the disclosure specifics that anonymity forced you to blur: real vendor names, CVE identifiers, advisory URLs, coordinated-disclosure dates. The open-access paper is part of the public disclosure record — get these exact.
- Replace anonymized artifact links with the archival DOI (see
ndss-artifact-evaluation). - Restore internal system/tool names, cited correctly.
- Verify every reference now that self-citation can be first-person and complete.
Show full SKILL.md (185 more words)Show less
Add earned artifact badges
If artifact evaluation passed, place the earned badges (Available / Functional / Reproduced)
on the first page using the provided badge style (ndssbadges.sty in the 2026 tooling) and
add the 2-page artifact appendix. Badges you did not earn do not appear — the committee's
report is the source of truth, not your ambition.
Final production checklist
[ ] Revision/shepherd conditions all discharged (item-by-item diff)
[ ] Current NDSS camera-ready template; body still within the limit after de-anon growth
[ ] Authors, affiliations, ORCIDs, acknowledgments, funding present and correct
[ ] Disclosure specifics restored and accurate (vendors, CVEs, dates, advisories)
[ ] Ethics Considerations section retained and consistent with the published claims
[ ] Artifact badges placed (if earned) + 2-page artifact appendix added
[ ] References complete; DOIs where available; self-citations de-anonymized
[ ] Fonts embedded; PDF compiles clean on another machine; metadata now correct
[ ] Copyright/publication forms submitted per Internet Society instructions
[ ] Presenter identified; Seoul registration and travel underway (visas!)The open-access consequence
Because there is no paywall between your paper and the field, two things follow. First, errors are permanent and public — the timeline, the vendor name, the availability statement will be read by the affected vendors and by future citers. Second, self-archiving is explicitly permitted, so post the camera-ready on your own pages and repositories once proceedings publish; there is no embargo to wait out.
Present in Seoul
NDSS 2027 meets in Seoul, 22-26 March 2027 — the venue's first move off its long San Diego February footing. Confirm attendance/presentation requirements on the current logistics page (registration opened October 2026), and plan the talk for a room that will read the free paper afterward: lead with the adversary and the finding, not the related work.
Output format
[Conditions] revision/shepherd items — each discharged? outstanding listed
[De-anonymization] authors / disclosure specifics / artifact link / tool names — done or gaps
[Badges] earned set placed? artifact appendix added?
[Production] checklist failures blocking submission
[Logistics] presenter, registration, visa lead time© 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 NDSS-Skills/skills/ndss-camera-ready of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ndss Camera Ready 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 |
|---|---|---|---|---|---|---|
| Ndss Camera Ready this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Convertremotion-dev/remotion | 63k | — | ~247 | Automated safety check: Pass | Custom licence | |
| QA Acceptancepaperclipai/paperclip | 99k | — | ~964 | Automated safety check: Pass | MIT | |
| Acceptance Orchestratorsickn33/agentic-awesome-skills | 47k | 2 repos | ~943 | Automated safety check: Pass | MIT | |
| Acceptance Evidence for Deliverieslobehub/lobehub | 83k | — | ~9.7k | Automated safety check: Pass | Apache-2.0 | |
| Word to Markdown Convertergithub/awesome-copilot | 40k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
QA Acceptance
paperclipai/paperclip
Produce QA acceptance criteria and a manual validation plan for a feature change — golden path, edge cases, error states, performance limits, and explicit pass/fail evidence.
Acceptance Orchestrator
sickn33/agentic-awesome-skills
A skill your agent uses when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
Acceptance Evidence for Deliveries
lobehub/lobehub
Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.
- Official
Word to Markdown Converter
github/awesome-copilot
Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.
Change, Accept or Leave Framework
kangarooking/cangjie-skill
Helps someone stuck ruminating over an unchangeable situation decide whether to change it, accept it, or leave it, drawn from a chapter of Navalism-style writing.
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 Ndss Camera Ready
What does Ndss Camera Ready do?
A skill your agent uses when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding…. Ndss Camera Ready is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions, de-anonymizing, restoring disclosure specifics, adding earned artifact badges, and meeting the Internet Society proceedings and camera-ready requirements by the January deadline.
When should I use Ndss Camera Ready?
Ndss Camera Ready fits situations like: converting an accepted NDSS paper into the final open-access version — satisfying Minor/Major Revision conditions; restoring disclosure specifics; adding earned artifact badges; meeting the Internet Society proceedings and camera-ready requirements by the January deadline.
How do I install Ndss Camera Ready in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-camera-ready -a claude-code`. Or copy the skill folder (NDSS-Skills/skills/ndss-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ndss-camera-ready in your project. Claude Code loads it when a task matches its description.
How do I install Ndss Camera Ready in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-camera-ready -a codex`. Or copy the skill folder (NDSS-Skills/skills/ndss-camera-ready in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ndss-camera-ready in your project. Codex loads it when a task matches its description.
Can I use Ndss Camera Ready 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 ndss-camera-ready -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ndss-camera-ready, .gemini/skills/ndss-camera-ready, .github/skills/ndss-camera-ready and .opencode/skills/ndss-camera-ready in your project.
What does Ndss Camera Ready need to run?
SKILL.md names no scripts, command-line tools or credentials: Ndss Camera Ready is instructions for the agent only.
Does Ndss Camera Ready 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 Ndss Camera Ready 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 Ndss Camera Ready use?
Ndss Camera Ready 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 Ndss Camera Ready use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 Ndss Camera Ready?
Skills that share tags, products or a category with Ndss Camera Ready: Convert (remotion-dev/remotion, 63k stars), QA Acceptance (paperclipai/paperclip, 99k stars), Acceptance Orchestrator (sickn33/agentic-awesome-skills, 47k stars) and Acceptance Evidence for Deliveries (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ndss Camera Ready?
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.