Google Calendar
codewhale-hq/Codewhale
Reads schedules, checks free and busy time, and creates or updates Google Calendar events through the Calendar API, with care around invites and recurring series.
A skill your agent uses when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification…
MITAuto-check passed
Install Ndss Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .claude/skills/ndss-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .claude/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .agents/skills/ndss-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .agents/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .cursor/skills/ndss-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .cursor/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path NDSS-Skills/skills/ndss-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .gemini/skills/ndss-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .gemini/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .github/skills/ndss-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .github/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ndss-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/NDSS-Skills/skills/ndss-workflow .opencode/skills/ndss-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ndss-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/NDSS-Skills/skills/ndss-workflow into .opencode/skills/ndss-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ndss-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ndss-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 571 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification…
- Works in 2 steps: Retargeting without revision is… → NDSS is a venue, not a fallback tier.…
- Planning an NDSS submission calendar — choosing between the summer and fall cycles
- SKILL.md covers The 2027 skeleton (verified…, Backward plan from a fall…, Choosing the cycle and The big-four year, seen from…, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Ndss Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning an NDSS submission calendar — choosing between the summer and fall cycles
- Backward-planning from the AoE deadline through early-reject
- The Seoul symposium
- Placing NDSS honestly inside the security big-four retargeting year
Example prompts
- “/ndss-workflow”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Retargeting without revision is re-rejection. Reviewer pools overlap heavily across
- NDSS is a venue, not a fallback tier. Its acceptance bar is a peer of the other
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 Workflow loads about 1.3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 571 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). 571 words, ~1,335 tokens.
Download SKILL.mdSave it as
.claude/skills/ndss-workflow/SKILL.md (or your agent's skills folder).- name
- ndss-workflow
- description
- Use when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.
NDSS Workflow
One symposium, two entrances. NDSS 2027 accepts papers through a summer cycle and a fall cycle, each a complete two-round review pipeline, both feeding the same week in Seoul (22-26 March 2027). Plan against the cycle you can actually win, not the one that arrives first.
The 2027 skeleton (verified 2026-07-08; always recheck the live CFP)
| Milestone | Summer cycle | Fall cycle |
|---|---|---|
| Paper deadline (AoE / UTC-12) | May 6, 2026 — passed | August 19, 2026 |
| Early-reject notification + Round-1 reviews | June 12, 2026 | September 25, 2026 |
| Rebuttal + interactive discussion | June 24-28, 2026 | October 8-10, 2026 |
| Final notification | July 22, 2026 | November 4, 2026 |
| Camera-ready (both cycles) | January 6, 2027 | January 6, 2027 |
| Symposium (Seoul) | March 22-26, 2027 | March 22-26, 2027 |
As of 2026-07-08 the summer cycle is between rebuttal and notification; the fall deadline is roughly six weeks out. Registration for Seoul opens in October 2026 (Internet Society announcement) — for many teams the 2027 edition also means visas and long-haul travel budgets that San Diego never required. Start that paperwork at acceptance, not at camera-ready.
Backward plan from a fall submission
Aug 19 paper deadline (AoE) ── freeze everything
Aug 12 full-draft freeze ── format, anonymity, ethics-section passes only
Aug 05 internal red-team read ── someone plays the Round-1 reviewer
Jul 29 evaluation freeze ── last new experiment; start writing results
Jul 15 disclosure clock check ── vendor notifications sent early enough that
"we disclosed" is true at submission time
Jul 08 (today) go/no-go ── fit test done, adversary model written,
headline experiment already runningThe item teams misplace is the disclosure clock: responsible disclosure has latency measured in weeks, and the CFP expects reporting (or a concrete plan) for high-impact vulnerabilities. A finding made on August 10 forces an uncomfortable choice; a finding made in July does not.
Choosing the cycle
- Enter the earliest cycle whose backward plan closes with the evaluation done, not projected. A thin submission is worse than a late one here, because a rejection blocks major-overlap resubmission in the other 2027 cycle.
- The rebuttal window is short and fixed (Oct 8-10 for fall). Check coauthor availability during those exact days before committing.
- A Major Revision outcome converts the calendar: you get reviewer-specified revision tasks and a resubmission window (dates 待核实 — confirm on notification). Budget the post-notification month as working time, not celebration time.
Show full SKILL.md (259 more words)Show less
The big-four year, seen from the NDSS seat
The four flagship deadlines interleave, and NDSS's late-summer fall deadline sits where papers rejected from the S&P and CCS spring/summer cycles and the USENIX Security year naturally land. Two honest rules for riding this calendar:
- Retargeting without revision is re-rejection. Reviewer pools overlap heavily across the big four; a resubmission that ignores its previous reviews often meets the same people. Fold in the fixes, and re-frame for NDSS's networked-adversary lens rather than doing a logo swap.
- NDSS is a venue, not a fallback tier. Its acceptance bar is a peer of the other three; a paper that was thin at S&P is thin here too. What legitimately changes is fit — protocol, web, DNS, and distributed-infrastructure work often reads better to an NDSS PC than it did wherever it bounced.
Running the year
- Track each paper as a state machine:
drafting → submitted → round-2 | early-reject → rebuttal → accept | minor-rev | major-rev | reject, with an owner and a next-action per state. The review-process skill details what each state means. - On early reject (with Round-1 reviews in hand): route to the next venue on the
routing table in
ndss-topic-selection, after folding in the reviews. The same-edition door is closed; the 2028 door is not. - On accept / minor revision: fork immediately into camera-ready (January 6 is far but
the artifact-evaluation opt-in is near — see
ndss-artifact-evaluation) and logistics (registration, visas, who presents). - Keep the per-author six-submission cap visible on the group's board each cycle; it binds collaborations with many shared authors sooner than people expect.
Output format
[Cycle chosen] summer / fall / next edition — one-line justification
[Backward plan] table of dated freezes ending at the AoE deadline
[Disclosure clock] green / yellow / red + earliest safe submission date
[Rebuttal window] coauthors confirmed available? yes/no
[Post-decision branches] accept / minor / major / reject → owner + next action each
[Logistics] Seoul registration, visa lead time, presenter© 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-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ndss Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Ndss Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Google Calendarcodewhale-hq/Codewhale | 41k | — | ~512 | Automated safety check: Pass | MIT | |
| Team Calendarsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Gws Calendar Agendagoogleworkspace/cli | 31k | 1 repos | ~389 | Automated safety check: Pass | Apache-2.0 | |
| Feishu Calendar Managerop7418/CodePilot | 6.5k | 1 repos | ~1.4k | Automated safety check: Pass | Custom licence | |
| WeCom Calendar SchedulerWecomTeam/wecom-cli | 3.2k | 1 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Team Calendar
sickn33/agentic-awesome-skills
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module.
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
Feishu Calendar Manager
op7418/CodePilot
Tool guidance for Feishu calendars: creating, listing, updating and searching events, managing attendees and replies, and checking free and busy time.
WeCom Calendar Scheduler
WecomTeam/wecom-cli
Books, views, searches, updates, cancels or checks free/busy time on WeCom (Enterprise WeChat) calendars and meeting rooms, routed away from online-meeting creation.
Dingtalk Calendar
DingTalk-Real-AI/dingtalk-workspace-cli
钉钉日历与会议室。Use when 用户说 约会议/查日程/订会议室/查闲忙/加参会人/改期/取消会议/今天的日程/本周日程/共同空闲。不做视频会议发起/邀请入会/会中控制（走 dingtalk-misc）、AI 听记（走 dingtalk-minutes）、待办任务（走 dingtalk-todo）。命令前缀：dws calendar。
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 Workflow
What does Ndss Workflow do?
A skill your agent uses when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification…. Ndss Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.
When should I use Ndss Workflow?
Ndss Workflow fits situations like: planning an NDSS submission calendar — choosing between the summer and fall cycles; backward-planning from the AoE deadline through early-reject; the Seoul symposium; placing NDSS honestly inside the security big-four retargeting year.
How do I install Ndss Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a claude-code`. Or copy the skill folder (NDSS-Skills/skills/ndss-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ndss-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ndss Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a codex`. Or copy the skill folder (NDSS-Skills/skills/ndss-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ndss-workflow in your project. Codex loads it when a task matches its description.
Can I use Ndss Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ndss-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ndss-workflow, .gemini/skills/ndss-workflow, .github/skills/ndss-workflow and .opencode/skills/ndss-workflow in your project.
What does Ndss Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Ndss Workflow is instructions for the agent only.
Does Ndss Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Ndss Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ndss Workflow use?
Ndss Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ndss Workflow use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Ndss Workflow?
Skills that share tags, products or a category with Ndss Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Team Calendar (sickn33/agentic-awesome-skills, 47k stars), Gws Calendar Agenda (googleworkspace/cli, 31k stars) and Feishu Calendar Manager (op7418/CodePilot, 6.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ndss Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.