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 full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing…
MITAuto-check passed
Install Isca Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-workflow .claude/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .claude/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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/ISCA-Skills/skills/isca-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 isca-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-workflow .agents/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .agents/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-workflow .cursor/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .cursor/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 ISCA-Skills/skills/isca-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 isca-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-workflow .gemini/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .gemini/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-workflow .github/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .github/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-workflow .opencode/skills/isca-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 "isca-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-workflow into .opencode/skills/isca-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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
isca-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 733 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 full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing…
- Staffing the winter two-round review wait
- SKILL.md covers The verified 2026-cycle skeleton, Working backward from November, The winter: silence, then… and Branch plans after notification, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Preparing for the February-March rebuttal and revision window
What it does
Isca Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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
- Staffing the winter two-round review wait
- Preparing for the February-March rebuttal and revision window
- Branching to camera-ready
- The June conference
Example prompts
- “/isca-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 (its code samples are yaml).
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
Isca Workflow loads about 1.7k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 733 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). 733 words, ~1,680 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-workflow/SKILL.md (or your agent's skills folder).- name
- isca-workflow
- description
- Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.
ISCA Workflow
An ISCA year has one gate. Miss mid-November and the next identical opportunity is
twelve months away, which is why experienced groups treat the ISCA calendar as an
engineering schedule with the deadline as tape-out. This skill lays out that
schedule using the verified ISCA 2026 dates as the template; as of 2026-07-08 the
ISCA 2027 CFP was not yet posted, so every 2027 date below is an expectation to
confirm against iscaconf.org/isca2027/ the moment it exists (待核实).
The verified 2026-cycle skeleton
| Milestone | ISCA 2026 date (verified) | What it means operationally |
|---|---|---|
| Abstract registration | November 10, 2025 | Title, abstract, authors, conflicts locked in HotCRP; paper content still fluid |
| Full paper | November 17, 2025 | The reviewed PDF — one week after abstracts, so the abstract week is a writing week, not a buffer |
| Round 1 reviews due | December 19, 2025 | First reviewer wave completes before the holidays |
| Round 2 reviews due | February 13, 2026 | Additional reviews on papers that advanced |
| Rebuttal + revision | February 16 - March 6, 2026 | Authors see reviews, respond, and may revise — a three-week working window |
| Conference | June 27 - July 1, 2026 (Raleigh, NC) | Presentation; artifact badges resolved before publication |
Industry-track submissions ran about a month behind (abstracts December 5, papers December 12, 2025). Final notification date for 2026 was not captured in this pack's verification — 待核实.
Working backward from November
Count in weeks from the expected paper deadline (call it P, likely mid-November 2026 for ISCA 2027):
- P minus 16 weeks (late July): venue decision final (
isca-topic-selection); simulation or prototype infrastructure chosen and validated (isca-experiments); the one-sentence claim written on the whiteboard. - P minus 10 weeks: baseline configurations frozen and reproduced from scratch by a second person. Baseline drift discovered later invalidates every downstream number.
- P minus 6 weeks: main-result experiments complete. From here, compute goes to sensitivity studies and reviewer-anticipation runs, not to the headline.
- P minus 4 weeks: full draft exists — bad prose, complete structure. Internal "mock PC" read by two colleagues who did not build the system.
- P minus 1 week (abstract deadline): title/abstract/topics/conflicts final in HotCRP. The abstract steers reviewer assignment; write it for bidding, not as a placeholder.
- P: upload per
isca-submission, then freeze the artifact snapshot that matches the submitted numbers (isca-reproducibility).
The winter: silence, then three loud weeks
Between November and mid-February the authors' only jobs are (a) keep the
evaluation environment resurrectable and (b) pre-build rebuttal ammunition: the
five most likely objections, each with a ready experiment or a pointer into the
submitted PDF. The 2026 cycle then opened a combined rebuttal/revision period
(February 16 - March 6) — unusually long by conference standards precisely because
ISCA lets authors change the paper, not just argue about it. Staff those three
weeks like a sprint: compute reserved, coauthors on call, no conference travel
booked. Details of what to do inside the window live in isca-author-response.
Show full SKILL.md (261 more words)Show less
Branch plans after notification
- Accept: camera-ready under the edition's publisher workflow
(
isca-camera-ready), voluntary artifact submission (isca-artifact-evaluation), talk and travel for late June. - Reject with salvageable reviews: map every misunderstanding to the sentence that permitted it; decide MICRO (spring gate) vs HPCA (summer gate) within two weeks while the reviews are fresh.
- Reject with a fit objection: rerun
isca-topic-selectionhonestly — the committee may have told you the paper's true venue.
Team ledger
Keep a single tracking file in the paper repo; every risk has one owner.
# isca-campaign.yaml
target: ISCA 2027 # 54th by arithmetic - ordinal 待核实
gate:
abstract: TBD-2026-11 # confirm on iscaconf.org/isca2027 when live
paper: TBD-2026-11
source: "not yet posted as of 2026-07-08"
owners:
claim_and_story: <name> # one sentence, defended weekly
simulation_infra: <name> # versions pinned, configs archived
baselines: <name> # frozen P-10w, independently reproduced
writing: <name> # draft complete P-4w
submission_admin: <name> # HotCRP, conflicts, template, metadata
rebuttal_reserve: <name> # compute + calendar hold, mid-Feb to early Mar
checks:
- abstract written for reviewer bidding, not filler
- artifact snapshot tagged at submission commit
- mock-PC read completed and objections filed
- fallback venue named with trigger conditionFailure modes this calendar prevents
- The November collision: abstract and paper a week apart means groups that planned "we'll write after the abstract" write the whole paper in seven days. The P-4w draft rule exists for this.
- The dead environment: rebuttal-window experiments that fail because the simulator tree no longer builds in February. Tag and containerize at submission.
- The unstaffed revision: ISCA's revision option is leverage only for teams that can produce new results in days; treat the window as scheduled work.
- The stale retarget: rejected papers resubmitted unchanged to MICRO carry their ISCA reviews' fingerprints; committees overlap. Budget a real revision.
Milestone-to-skill routing
| When you are at... | Open... |
|---|---|
| Venue decision (P-16w) | isca-topic-selection, exemplars library |
| Infrastructure setup | isca-experiments, isca-reproducibility |
| Drafting (P-6w to P-1w) | isca-writing-style, isca-related-work, isca-supplementary |
| Upload week | isca-submission (twice: abstract step, paper step) |
| Winter wait | isca-review-process |
| February window | isca-author-response |
| Post-decision | isca-camera-ready, isca-artifact-evaluation, or the retarget branch |
All dates above are the 2026-cycle record
(../../resources/official-source-map.md, checked 2026-07-08). Confirm the 2027
calendar, page rules, and review mechanics on the official site before acting on
any of them.
© 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 ISCA-Skills/skills/isca-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca 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 |
|---|---|---|---|---|---|---|
| Isca Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Google Calendarcodewhale-hq/Codewhale | 41k | — | ~512 | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 275k | 1 repos | ~1.3k | 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 | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
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.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Campaign Cleaner Automation
ComposioHQ/awesome-claude-skills
Automate Campaign Cleaner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.
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 Isca Workflow
What does Isca Workflow do?
A skill your agent uses when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing…. Isca Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.
When should I use Isca Workflow?
Isca Workflow fits situations like: staffing the winter two-round review wait; preparing for the February-March rebuttal and revision window; branching to camera-ready; the June conference.
How do I install Isca Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-workflow -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Isca Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-workflow -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-workflow in your project. Codex loads it when a task matches its description.
Can I use Isca 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 isca-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/isca-workflow, .gemini/skills/isca-workflow, .github/skills/isca-workflow and .opencode/skills/isca-workflow in your project.
What does Isca Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Isca Workflow is instructions for the agent only.
Does Isca 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 Isca 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 Isca Workflow use?
Isca 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 Isca Workflow use?
About 1.7k tokens (SKILL.md is roughly 6.7k 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 Isca Workflow?
Skills that share tags, products or a category with Isca Workflow: Google Calendar (codewhale-hq/Codewhale, 41k stars), Marketing Campaign (affaan-m/ECC, 275k stars), Team Calendar (sickn33/agentic-awesome-skills, 47k stars) and Gws Calendar Agenda (googleworkspace/cli, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Isca Workflow?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,219 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.