Agent skill

Ieeesp Workflow

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows…

MITAuto-check passed

Install Ieeesp Workflow

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .claude/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .claude/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .agents/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .agents/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .cursor/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .cursor/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path IEEE-SP-Skills/skills/ieeesp-workflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .gemini/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .gemini/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .github/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .github/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills ieeesp-workflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/IEEE-SP-Skills/skills/ieeesp-workflow .opencode/skills/ieeesp-workflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "ieeesp-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IEEE-SP-Skills/skills/ieeesp-workflow into .opencode/skills/ieeesp-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ieeesp-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: ieeesp-workflow
GitHub stars: 1.2k
Token cost: ~1.3k tokens
SKILL.md length: 533 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows…

Planning an IEEE S&P (Oakland) submission calendar across the two-cycle year
SKILL.md covers The S&P 2027 cycle map…, Registration week is the real…, Backward schedule from a cycle and Branch plans for the three…, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Including registration-versus-paper deadlines

What it does

Ieeesp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.

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 IEEE S&P (Oakland) submission calendar across the two-cycle year
Including registration-versus-paper deadlines
The early-reject and rebuttal windows
Revise resubmission timing

Example prompts

“/ieeesp-workflow”

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

Ieeesp Workflow loads about 1.3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 533 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~76
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

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). 533 words, ~1,252 tokens.

Download SKILL.mdSave it as .claude/skills/ieeesp-workflow/SKILL.md (or your agent's skills folder).

name: ieeesp-workflow
description: Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.

IEEE S&P Workflow

Use this to run a project against S&P's calendar. Unlike single-deadline ML venues, each S&P symposium accepts papers through multiple submission cycles, each a self-contained mini-conference with its own HotCRP site, registration freeze, review rounds, and decision date. Planning means choosing a cycle, not "the deadline."

The S&P 2027 cycle map (checked 2026-07-08, all dates 待核实 before use)

Milestone	Cycle 1	Cycle 2
Abstract registration (title/abstract/authors/ORCIDs frozen)	Jun 5, 2026, 7:59:59 AM EDT	Nov 10, 2026
Full paper due	Jun 12, 2026	Nov 17, 2026
Early-reject notification	待核实	Jan 18, 2027
Reviews released to surviving papers	待核实	Feb 11, 2027
Rebuttal due	待核实	Feb 16, 2027
Decision (Accept / Revise / Reject)	待核实	Mar 5, 2027
Symposium (Montreal, Canada)	May 2027	May 2027

Two planning facts bite hardest. First, Cycle 1 for 2027 closed on June 12, 2026 — as of this pack's check date the open path is Cycle 2. Second, S&P states deadlines in a fixed clock time (7:59:59 AM EDT for Cycle 1), not AoE; a team assuming Anywhere-on-Earth loses most of a day.

Registration week is the real deadline

At S&P, the registration deadline is substantive: the final title, complete abstract, full author list with ORCIDs, and declared conflicts are locked on HotCRP one week before the paper is due, and none of it may change afterwards. ORCID records must match HotCRP names and emails or the paper is desk rejected. Treat registration week as the week author-list politics, ORCID housekeeping, and conflict declarations get resolved — not deadline night.

Backward schedule from a cycle

text

T-16w  Threat model + evidence plan frozen (ieeesp-topic-selection)
T-12w  Core exploit / adaptive evaluation / measurement running
T-8w   Ethics work: disclosure sent to vendors, IRB determination
       in hand — these have external latency you cannot compress
T-4w   Full draft; internal adversarial read by a non-author
T-1w   REGISTRATION: title, abstract, authors+ORCIDs, conflicts,
       Ethics Considerations field on HotCRP — then frozen
T-0    Paper upload (13 pages + ≤5 refs/appendix, compsoc template)
T+~9w  Early-reject notice; if surviving: reviews + 5-day rebuttal
T+~16w Decision: Accept (shepherded camera-ready) / Revise / Reject

The item teams misplace is the ethics latency at T-8w: responsible-disclosure clocks and IRB reviews run on other institutions' calendars, and the registration-time Ethics Considerations field must describe work already done, not intentions.

Show full SKILL.md (242 more words)Show less

Branch plans for the three outcomes

Accept — expect a draft meta-review plus a shepherd who checks concerns off as the camera-ready resolves them; budget real revision time, not a formatting pass (ieeesp-camera-ready).
Revise — a structured major revision with a summary of expectations; this is the venue's signature second chance. Plan it as a project with an owner and a deadline, not as "address comments" (ieeesp-review-process).
Reject — the one-year embargo runs from the original submission date, and anything ≥~40% overlapping counts as a resubmission. The productive branch is usually a sibling venue whose deadline falls inside the embargo window.

Choosing between cycles

Pick the later cycle when the adaptive evaluation or disclosure process is incomplete — an early reject costs the venue for a year of that paper's life, and first-round reviewers do not see rebuttals.
Pick the earlier cycle when the work is done and a Revise outcome would still land the paper in the same symposium year.
Never plan on submitting the same work to two S&P cycles back-to-back without checking the current CFP's resubmission wording — the embargo applies across cycles, not just across years.

Standing risks to assign owners

Risk	Owner action
Registration freeze missed	Calendar registration week, not paper week
Timezone misread (EDT vs AoE)	Convert official time on day one
Disclosure/IRB latency	Start at T-8w; log vendor contact dates
Embargo collision	Check prior S&P rejections before committing
Shepherd turnaround post-accept	Reserve author time in the decision month

Output format

text

[Target] S&P <year>, Cycle <n> (registration <date>, paper <date>)
[Today→registration] <n> weeks; feasibility: on-track / tight / unrealistic
[Ethics latency] disclosure started? IRB determination? <status>
[Embargo] clear / blocked until <date>
[Branch plans] accept: <owner> · revise: <owner> · reject: <next venue>

Files

Just SKILL.md in IEEE-SP-Skills/skills/ieeesp-workflow of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Ieeesp 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.

Ieeesp Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Ieeesp Workflow this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.3k	Automated safety check: Pass	MIT	12 days ago
Google Calendarcodewhale-hq/Codewhale	41k	—	~512	Automated safety check: Pass	MIT	today
Team Calendarsickn33/agentic-awesome-skills	47k	1 repos	~3.3k	Automated safety check: Pass	MIT	today
Gws Calendar Agendagoogleworkspace/cli	31k	1 repos	~389	Automated safety check: Pass	Apache-2.0	3 days ago
Feishu Calendar Managerop7418/CodePilot	6.5k	1 repos	~1.4k	Automated safety check: Pass	Custom licence	17 days ago
WeCom Calendar SchedulerWecomTeam/wecom-cli	3.2k	1 repos	~3.7k	Automated safety check: Pass	MIT	15 days ago

Similar skills

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.
41k GitHub stars~512 tokensUpdated today
Productivity & AutomationAuto-check passed
Team Calendar
sickn33/agentic-awesome-skills
Team calendar: event, type, date and time with time zone, attendees, organizer, location and source module.
47k GitHub starsUsed in 1 repo~3.3k tokens
Productivity & AutomationAuto-check passed
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
31k GitHub starsUsed in 1 repo~389 tokens
Documents & OfficeAuto-check passed
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.
6.5k GitHub starsUsed in 1 repo~1.4k tokens
Productivity & AutomationAuto-check passed
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.
3.2k GitHub starsUsed in 1 repo~3.7k tokens
Productivity & AutomationAuto-check passed
Dingtalk Calendar
DingTalk-Real-AI/dingtalk-workspace-cli
钉钉日历与会议室。Use when 用户说约会议/查日程/订会议室/查闲忙/加参会人/改期/取消会议/今天的日程/本周日程/共同空闲。不做视频会议发起/邀请入会/会中控制（走 dingtalk-misc）、AI 听记（走 dingtalk-minutes）、待办任务（走 dingtalk-todo）。命令前缀：dws calendar。
3.2k GitHub stars~2k tokensUpdated today
Auto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 12 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 12 days ago
Auto-check passed

Questions about Ieeesp Workflow

What does Ieeesp Workflow do?

A skill your agent uses when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows…. Ieeesp Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE S&P (Oakland) submission calendar across the two-cycle year, including registration-versus-paper deadlines, the early-reject and rebuttal windows, Revise resubmission timing, the one-year embargo clock, and choosing which cycle a project can realistically hit.

When should I use Ieeesp Workflow?

Ieeesp Workflow fits situations like: planning an IEEE S&P (Oakland) submission calendar across the two-cycle year; including registration-versus-paper deadlines; the early-reject and rebuttal windows; revise resubmission timing.

How do I install Ieeesp Workflow in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a claude-code`. Or copy the skill folder (IEEE-SP-Skills/skills/ieeesp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ieeesp-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Ieeesp Workflow in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ieeesp-workflow -a codex`. Or copy the skill folder (IEEE-SP-Skills/skills/ieeesp-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ieeesp-workflow in your project. Codex loads it when a task matches its description.

Can I use Ieeesp 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 ieeesp-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/ieeesp-workflow, .gemini/skills/ieeesp-workflow, .github/skills/ieeesp-workflow and .opencode/skills/ieeesp-workflow in your project.

What does Ieeesp Workflow need to run?

SKILL.md names no scripts, command-line tools or credentials: Ieeesp Workflow is instructions for the agent only.

Does Ieeesp 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 Ieeesp 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 Ieeesp Workflow use?

Ieeesp 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 Ieeesp Workflow use?

About 1.3k tokens (SKILL.md is roughly 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 Ieeesp Workflow?

Skills that share tags, products or a category with Ieeesp 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 Ieeesp 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.

Install Ieeesp Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

IEEE S&P Workflow

The S&P 2027 cycle map (checked 2026-07-08, all dates 待核实 before use)

Registration week is the real deadline

Backward schedule from a cycle

Branch plans for the three outcomes

Choosing between cycles

Standing risks to assign owners

Output format

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Ieeesp Workflow