isca-workflow
From the author
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.
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-workflow -a claude-code
Installs to .claude/skills/isca-workflow/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 88
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- icse-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.Productivity★ 1.3K
- icra-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.Productivity★ 1.3K
- issta-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ISSTA project timeline from venue fit through the January research-paper deadline, the March author response, the April first decision, the May Major-Revision sprint, the June final decision, artifact evaluation, and the October symposium, with backward-planning offsets for a testing/analysis tool paper and its artifact.Productivity★ 1.3K
- hpca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.Productivity★ 1.3K
- itcs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.Productivity★ 1.3K
- colm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a COLM submission campaign across the calendar — working backward from the late-March abstract and paper deadlines through the May-June rebuttal, July decisions, August camera-ready, and October conference, coordinating co-authors, compute, and reciprocal-reviewing duties, and slotting COLM into a multi-venue LM-research pipeline.Productivity★ 1.3K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in