Marketing Campaign
affaan-m/ECC
End-to-end marketing campaign planning and execution. An agent skill from affaan-m/ECC.
A skill your agent uses 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…
MITAuto-check passed
Install Icse Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-workflow .claude/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .claude/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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/ICSE-Skills/skills/icse-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 icse-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-workflow .agents/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .agents/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-workflow .cursor/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .cursor/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 ICSE-Skills/skills/icse-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 icse-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icse-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/ICSE-Skills/skills/icse-workflow .gemini/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .gemini/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-workflow .github/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .github/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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 icse-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 icse-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/ICSE-Skills/skills/icse-workflow .opencode/skills/icse-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 "icse-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSE-Skills/skills/icse-workflow into .opencode/skills/icse-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icse-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
icse-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 635 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 ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions…
- Planning an ICSE research-track campaign end to end
- SKILL.md covers The 2027-cycle master calendar, Working backward from June 30, Role assignments that prevent… and Branch plans after October 20, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the single-cycle calendar from the June abstract deadline through September response
What it does
Icse Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use 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.
Its SKILL.md is about 1.4k 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 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
Example prompts
- “/icse-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
Icse Workflow loads about 1.4k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 635 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). 635 words, ~1,421 tokens.
Download SKILL.mdSave it as
.claude/skills/icse-workflow/SKILL.md (or your agent's skills folder).- name
- icse-workflow
- description
- Use 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.
ICSE Workflow
An ICSE campaign is a ten-month pipeline with one entrance. The 2027 cycle (checked 2026-07-08 against the official dates pages) runs a single submission cycle — a change from the two-cycle 2025/2026 model — so a missed June deadline costs a full year, and the calendar below is the whole game.
The 2027-cycle master calendar
| Date (all AoE where applicable) | Milestone | Your workstream |
|---|---|---|
| Jun 23, 2026 | Abstract (mandatory) | Real title + abstract frozen |
| Jun 30, 2026 | Full paper deadline | 10+2 IEEE PDF, artifact link live |
| Jul–Aug 2026 | Reviews written | Prepare response infrastructure; rest |
| Sep 2026 | Author response window | Criterion-mapped replies (icse-author-response) |
| Oct 20, 2026 | Decisions: Accept / Major Revision / Reject | Branch: celebrate / sprint / reroute |
| Nov 17, 2026 | Major Revision due | Four-week revision sprint |
| Dec 18, 2026 | Final MR decisions | Terminal for the cycle |
| Early 2027 (待核实) | Artifact evaluation window | Badge submission (icse-artifact-evaluation) |
| 待核实 | Camera-ready due | +1 page allowance, IEEE production |
| Apr 25 – May 1, 2027 | ICSE in Dublin (core Apr 28–30) | Talk, artifact, networking plan |
Artifact-evaluation and camera-ready dates for 2027 were not posted at check time; the 2026 edition ran artifact registration/submission in early January, which is the planning anchor until real dates appear.
Working backward from June 30
A credible empirical-SE paper cannot be compressed into deadline month, because its long poles — subject recruitment, benchmark construction, multi-week tool runs, qualitative coding with a second rater — do not parallelize late. Plan backward:
Jun 30 freeze: PDF + anonymized replication package
Jun 16 full internal mock review against the four criteria
Jun 02 results complete; threats-to-validity written from real limitations
May 05 evaluation running at scale; paper skeleton has real numbers
Apr 07 study design locked (RQs, baselines, metrics, subjects); pilot done
Mar 2026 and earlier: idea vetted with icse-topic-selection; related work sweptThe two dates authors most often plan around wrongly: the abstract deadline is mandatory (June 23 — a week before the paper, not a formality), and the response window is September, which lands in teaching-start season for most groups — reserve the days now.
Role assignments that prevent deadline-week chaos
- Evidence owner — benchmarks, baselines, statistics; owns Jun 2 freeze.
- Artifact owner — replication package, anonymization, availability statement; owns the link that goes in the paper.
- Prose owner — the 10-page budget, the threats section, the criterion self-audit.
- Process owner — HotCRP fields, conflicts, abstract registration, calendar of every date above in the group calendar with AoE conversions.
One person can hold two hats; no hat may be unheld.
Show full SKILL.md (291 more words)Show less
Branch plans after October 20
- Accept: artifact-evaluation submission (badges are opt-in and post-acceptance), camera-ready with the extra page, Dublin logistics.
- Major Revision: the November sprint is pre-planned before October — which experiments could be extended, which machines are free in November. Groups that first think about feasibility on notification day lose a week of the four.
- Reject: reroute within weeks, not months. FSE and ASE deadlines typically land in spring/summer, ISSTA in autumn/winter; TSE/TOSEM/EMSE take extended versions year-round, and a journal acceptance can return to the ICSE stage via journal-first (2027 window: papers accepted Oct 11, 2025 – Oct 10, 2026 at TSE/TOSEM/EMSE). Check each venue's live dates — sibling calendars move annually.
Cadence between milestones
The calendar above names endpoints; groups that hit them run a steady between-milestone cadence: a weekly claims-vs-evidence review from April (which headline claim is still unevidenced, who unblocks it), a biweekly package build so the artifact never diverges more than two weeks from the paper, and a standing "deadline minus 14" rehearsal where the current draft is mock-reviewed against the four criteria by someone outside the author list. The mock review is the cheapest Major-Revision insurance available: it finds the missing-baseline and boilerplate-threats objections while there is still a month to fix them rather than four weeks in November.
Cycle-volatility warnings
- The single-cycle structure itself is the newest variable: 2025/2026 ran two cycles, 2027 runs one. Verify the cycle count first each year, because it changes every downstream date and the rerouting math.
- Response format, artifact deadlines, camera-ready dates, and registration rules were all unposted for 2027 at check time — 待核实 before promising them to coauthors.
- Do not let old two-cycle advice ("resubmit to cycle 2") leak into planning; that lane does not exist in 2027.
Output format
[Cycle position] months to next ICSE deadline; feasible? yes/no
[Backward plan] dated milestones from today to freeze
[Owners] evidence / artifact / prose / process
[Branch readiness] MR sprint pre-plan? reroute venue + date named?
[Calendar risks] deadlines colliding with teaching/travel; AoE conversions done© 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 ICSE-Skills/skills/icse-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icse 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 |
|---|---|---|---|---|---|---|
| Icse Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Marketing Campaignaffaan-m/ECC | 276k | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Campaign Analyticsalirezarezvani/claude-skills | 28k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Campaign Cleaner AutomationComposioHQ/awesome-claude-skills | 77k | 3 repos | ~764 | Automated safety check: Pass | None | |
| Ad Campaign Analyzersickn33/agentic-awesome-skills | 47k | 1 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Ad Campaign Analyzergithub/awesome-copilot | 40k | 2 repos | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
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.
Ad Campaign Analyzer
sickn33/agentic-awesome-skills
Analyze cross-channel campaign data, quantify uncertainty, and propose evidence-labeled budget tests without overstating causality.
- Official
Ad Campaign Analyzer
github/awesome-copilot
A skill your agent uses when the user shares ad campaign performance data and asks what to cut, scale, or test.
Executing Marketing Campaigns
davila7/claude-code-templates
Plans, creates, and optimizes marketing campaigns including content strategy, social media, email, and analytics.
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 Icse Workflow
What does Icse Workflow do?
A skill your agent uses 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…. Icse Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use 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.
When should I use Icse Workflow?
Icse Workflow fits situations like: 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.
How do I install Icse Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-workflow -a claude-code`. Or copy the skill folder (ICSE-Skills/skills/icse-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icse-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Icse Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-workflow -a codex`. Or copy the skill folder (ICSE-Skills/skills/icse-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icse-workflow in your project. Codex loads it when a task matches its description.
Can I use Icse 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 icse-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/icse-workflow, .gemini/skills/icse-workflow, .github/skills/icse-workflow and .opencode/skills/icse-workflow in your project.
What does Icse Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Icse Workflow is instructions for the agent only.
Does Icse 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 Icse 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 Icse Workflow use?
Icse 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 Icse Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.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 Icse Workflow?
Skills that share tags, products or a category with Icse Workflow: Marketing Campaign (affaan-m/ECC, 276k stars), Campaign Analytics (alirezarezvani/claude-skills, 28k stars), Campaign Cleaner Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Ad Campaign Analyzer (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icse 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.