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 a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback…
MITAuto-check passed
Install Sigmod Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .claude/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .claude/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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/SIGMOD-Skills/skills/sigmod-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 sigmod-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .agents/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .agents/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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 sigmod-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .cursor/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .cursor/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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 SIGMOD-Skills/skills/sigmod-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 sigmod-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .gemini/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .gemini/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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 sigmod-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 sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .github/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .github/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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 sigmod-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 sigmod-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/SIGMOD-Skills/skills/sigmod-workflow .opencode/skills/sigmod-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 "sigmod-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SIGMOD-Skills/skills/sigmod-workflow into .opencode/skills/sigmod-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sigmod-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
sigmod-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 704 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback…
- Planning a SIGMOD project calendar under the PACMMOD round system
- SKILL.md covers The round as a five-act unit, Round selection under the…, Backward plan from a paper… and Team coordination specifics, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering round selection and hopping
What it does
Sigmod Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback and revision windows, embargo-aware contingencies, and coordinating a systems-building team against quarterly deadlines.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- Planning a SIGMOD project calendar under the PACMMOD round system
- Covering round selection and hopping
- Backward planning from abstract and paper cutoffs
- The feedback and revision windows
Example prompts
- “/sigmod-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
Sigmod Workflow loads about 1.5k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 704 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). 704 words, ~1,470 tokens.
Download SKILL.mdSave it as
.claude/skills/sigmod-workflow/SKILL.md (or your agent's skills folder).- name
- sigmod-workflow
- description
- Use when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback and revision windows, embargo-aware contingencies, and coordinating a systems-building team against quarterly deadlines.
SIGMOD Workflow
SIGMOD project management differs from single-deadline conferences in kind: with four research rounds a year feeding PACMMOD issues, the strategic variable is which round, and the punishment structure (a 12-month embargo on rejection, one month to execute a revision) rewards teams that plan the whole round, not just the deadline. Anchor every date below to the live important-dates page before acting; the quarterly pattern is durable, the dates are not.
The round as a five-act unit
Act 1 Abstract + COIs (deadline minus ~1 week)
Act 2 Paper deadline (the 17th of the round month, AoE, for 2027)
Act 3 Feedback phase (~2 months in; one-week reply window)
Act 4 First verdict (~3 months in: accept / reject / revision)
Act 5 Revision + final (+1 month to resubmit, ~+3 weeks to decide)Block engineer time for Acts 3 and 5 when you submit, not when they arrive:
the feedback week may need a fast counter-experiment, and the revision month
is a sprint that assumes the original evaluation was scripted end to end
(see sigmod-reproducibility).
Round selection under the embargo
| Situation | Recommended move |
|---|---|
| Evaluation complete, writing mature | Nearest round |
| Core result solid, one comparison missing | Next round; a missing baseline reads as reject, not revision |
| System working, evaluation thin | Skip two; thin evaluations burn the embargo |
| Racing a known competing group | Weigh nearest round against reject risk; PVLDB's monthly gate may beat waiting |
| Paper rejected last round | Different venue — the track is closed for ~3 rounds |
The asymmetry to internalize: submitting early costs a possible year; waiting costs three months. Under uncertainty, waiting is usually the cheaper mistake at this venue.
Backward plan from a paper cutoff
- T-16 weeks: freeze the system's architecture; feature work after this point invalidates measurements.
- T-10: evaluation matrix locked (workloads × baselines × sweeps); harness and seeds committed.
- T-6: full experiment pass complete once; draft carries real numbers, not placeholders.
- T-4: internal adversarial read by a colleague who builds systems; schedule their week now.
- T-2: rerun-from-scratch of every figure; repro ledger shows zero DEBT.
- T-1 week + a few days: abstract, authors, topics, COIs into CMT.
- T-0: PDF up; verify the uploaded file, not the local one.
Team coordination specifics
- Name one owner for the measurement harness and a different owner for the anonymity sweep; both jobs fail under shared custody.
- Keep a submissions ledger across the group: PACMMOD's exclusivity rule and the 10-papers-per-author annual cap are portfolio constraints, not per-paper ones.
- Archive the exact submitted PDF, the CMT confirmation, and the frozen artifact snapshot; the revision letter must quote and diff against them.
- Pre-agree the reject plan (PVLDB? ICDE? rework?) while everyone is calm; deciding it the day the verdict lands produces venue-shopping errors.
Interleaving multiple projects
Quarterly rounds let a group pipeline: project A in Round 1, its revision landing while project B targets Round 3. The trap is revision collision — two revisions in the same month exceed most teams' experiment bandwidth. When two papers are near-ready, split them across non-adjacent rounds deliberately rather than shipping both into one.
Show full SKILL.md (256 more words)Show less
Small-team and solo variants
The five-act structure assumes bench depth; without it, adjust:
- A solo author cannot staff a feedback week and a revision month on top of other obligations — prefer the round after the one that looks feasible, and treat the slack as the plan, not padding.
- Compress the evaluation matrix before compressing run hygiene; fewer workloads with clean provenance beat a wide matrix that cannot be regenerated during a revision.
- Recruit the adversarial reader early even when solo — the T-4 external read is the step small teams skip and most regret at verdict time.
- Consider whether PVLDB's monthly gate suits a solo pipeline better; a missed monthly deadline costs weeks, a failed SIGMOD round costs a year.
Conference layer
Publication and presentation decouple: your issue ships on the round's
schedule, and the talk happens at the next conference edition (SIGMOD 2027:
June 13–19, 2027, Huntington Beach; SIGMOD 2026 was May 31–June 5,
Bengaluru). Budget registration and travel when the acceptance lands, and
schedule the ARI artifact push (sigmod-artifact-evaluation) into the gap
between issue and conference.
Calendar-keeping discipline
Because every date in this skill perishes, institutionalize the refresh: at the start of each quarter, one team member re-opens the current important-dates page, diffs it against the team's planning calendar, and posts the delta. Rounds have shifted between cycles before; a plan anchored to a stale calendar fails silently until the abstract deadline passes. The same quarterly sweep should touch the ARI edition page and, for groups with industrial collaborations, the industrial-track CFP status.
Output format
[Target round] round + year, with selection rationale
[Stage now] pre-abstract / submitted / feedback / verdict / revision
[Backward plan] next three milestones with owners
[Bandwidth check] feedback + revision windows staffed yes/no
[Portfolio constraints] cap headroom, exclusivity conflicts, collisions
[Reject plan] pre-agreed next venue© 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 SIGMOD-Skills/skills/sigmod-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Sigmod 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 |
|---|---|---|---|---|---|---|
| Sigmod Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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.
Round Verification
SeemSeam/claude_codex_bridge
Verify a CCB execution round and produce a machine-readable round result artifact.
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 Sigmod Workflow
What does Sigmod Workflow do?
A skill your agent uses when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback…. Sigmod Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a SIGMOD project calendar under the PACMMOD round system, covering round selection and hopping, backward planning from abstract and paper cutoffs, the feedback and revision windows, embargo-aware contingencies, and coordinating a systems-building team against quarterly deadlines.
When should I use Sigmod Workflow?
Sigmod Workflow fits situations like: planning a SIGMOD project calendar under the PACMMOD round system; covering round selection and hopping; backward planning from abstract and paper cutoffs; the feedback and revision windows.
How do I install Sigmod Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-workflow -a claude-code`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/sigmod-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Sigmod Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill sigmod-workflow -a codex`. Or copy the skill folder (SIGMOD-Skills/skills/sigmod-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/sigmod-workflow in your project. Codex loads it when a task matches its description.
Can I use Sigmod 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 sigmod-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/sigmod-workflow, .gemini/skills/sigmod-workflow, .github/skills/sigmod-workflow and .opencode/skills/sigmod-workflow in your project.
What does Sigmod Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Sigmod Workflow is instructions for the agent only.
Does Sigmod 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 Sigmod 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 Sigmod Workflow use?
Sigmod 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 Sigmod Workflow use?
About 1.5k tokens (SKILL.md is roughly 5.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 Sigmod Workflow?
Skills that share tags, products or a category with Sigmod 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 Sigmod 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.