Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal…
Install Icsme Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-workflow .claude/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .claude/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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/ICSME-Skills/skills/icsme-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 icsme-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-workflow .agents/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .agents/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-workflow .cursor/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .cursor/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 ICSME-Skills/skills/icsme-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 icsme-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-workflow .gemini/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .gemini/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-workflow .github/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .github/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-workflow .opencode/skills/icsme-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 "icsme-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-workflow into .opencode/skills/icsme-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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
icsme-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 664 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 IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal…
- Planning an IEEE ICSME project timeline from venue and track choice through abstract registration
- SKILL.md covers Milestones, Backward plan from the paper…, The single-round calendar… and Failure modes by stage, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Paper submission
What it does
Icsme Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.
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.
It sits in Research & Science. 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 ICSME project timeline from venue and track choice through abstract registration
- Paper submission
- The early-decision cut and author-response rebuttal
- IEEE Xplore camera-ready
Example prompts
- “/icsme-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
Icsme Workflow loads about 1.4k tokens when it runs. Until then it costs about 103 tokens; SKILL.md has 664 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). 664 words, ~1,423 tokens.
Download SKILL.mdSave it as
.claude/skills/icsme-workflow/SKILL.md (or your agent's skills folder).- name
- icsme-workflow
- description
- Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.
ICSME Workflow
Use this as the project-management skill for an ICSME submission. Replace every date with the current official timetable and work backwards from the EasyChair abstract cutoff — which precedes the paper deadline. ICSME runs a single annual research round with no journal-style Major Revision: a paper is accepted or rejected in one cycle, so front-load the evidence and plan the author-response rebuttal, not a revise-and-resubmit.
ICSME is an IEEE conference with no standing editor-in-chief and no APC: proceedings go to IEEE Xplore and the cost model is registration. Rotating leadership is the per-edition General and Program Co-Chairs (ICSME 2026 committee roster 待核实 on the access date); re-check the organizing-committee page rather than carrying names forward. ICSME 2026 is the 42nd edition in Benevento, Italy (University of Sannio), 14-18 September 2026, co-located with SCAM and VISSOFT.
Milestones
- Venue and track fit: confirm ICSME over ICSE/FSE/SANER/MSR and pick the track — research,
Journal-First, Registered Reports, RENE, NIER, tool-demo, or industry (
icsme-topic-selection). - Evidence lock: freeze research questions, subject systems and their change history, baselines, statistics, threats, and the artifact contents.
- Abstract registration: submit real title, abstract, authors, and topics by the earlier abstract deadline (ICSME 2026: 27 Feb 2026).
- Paper submission: upload the anonymized PDF and data-availability statement (ICSME 2026: 6 Mar 2026).
- Early-decision cut: at the response period's start, some papers are already Accept or Reject; the rest are "Response Recommended" (ICSME 2026 early decisions: 3 May 2026).
- Author response: if invited, answer the PC's specific questions with existing evidence.
- Notification: final accept/reject (ICSME 2026: 29 May 2026); archive reviews and the response.
- Acceptance: prepare the IEEE Xplore camera-ready, submit to the ROSE-Festival artifact track for IEEE badges, register, and present.
Backward plan from the paper deadline
| Weeks out (heuristic) | Maintenance/evolution milestone |
|---|---|
| 10+ | Research questions fixed; subject systems and their change-history window chosen |
| 8 | Mining / data collection complete; repository SHAs and extraction dates logged |
| 6 | Analysis done; effect sizes and tests computed; threats drafted alongside results |
| 4 | Full draft in IEEEtran conference format; artifact assembled and anonymized |
| 3 | Internal mock review by a maintenance-empiricist reader |
| 2 | Threats hardened, related-work delta sharpened, 10-page budget met |
| 1 | Anonymity sweep on PDF and artifact; data-availability statement final |
| 0 | Abstract registered by its earlier cutoff, then paper + artifact link on EasyChair |
These offsets are planning heuristics only — anchor every one to the current Important Dates page, never to a previous cycle's calendar.
Show full SKILL.md (268 more words)Show less
The single-round calendar reality
ICSME runs one annual research round; the author-response rebuttal is the only mid-cycle lever, and there is no Major Revision to fall back on. Planning consequences:
- A rejected paper waits a full year at ICSME. Before idling, check whether a sibling (SANER, ICSE, FSE) has a nearer deadline, or whether the work is better routed to TSE/EMSE and returned later via the Journal-First track.
- A not-yet-finished study may fit Registered Reports (protocol reviewed first) rather than being rushed into the research track and rejected on thin evidence.
- A replication or negative result has a dedicated home in RENE — do not force it into the research track where novelty framing will hurt it.
Failure modes by stage
- Mining still running at week 4 forces last-minute analysis nobody has audited — the classic soundness reject for an evolution study.
- Naming your own subject system or public corpus breaks double-anonymity when the artifact is left to the final week.
- Skipping the mock review forfeits the one chance to hear "your baseline maintainer study is confounded" from a friend instead of a reviewer.
- Treating the author response as a debate wastes the single rebuttal ICSME gives you; answer the PC's specific questions with evidence, not argument.
Coordination notes
- Assign one owner for the data-availability / artifact and another for the anonymity sweep; shared ownership is how both slip under double-anonymity.
- Archive the exact submitted PDF and artifact; the response period must quote the paper precisely and stay anonymous.
- The ROSE-Festival artifact submission is a separate, post-acceptance deadline shared with SCAM and VISSOFT — calendar it apart from the camera-ready.
Output format
[Current stage] idea / evidence / abstract / submitted / response period / accepted
[Track] research / journal-first / registered report / RENE / NIER / tool-demo / industry
[Next official deadline] <date and source, or unknown>
[Critical path] <three tasks that determine readiness>
[Risk register] <page budget / anonymity / evidence / threats / artifact / presentation>
[Owner map] <task -> person or role>© 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 ICSME-Skills/skills/icsme-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icsme 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 |
|---|---|---|---|---|---|---|
| Icsme Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
Nature Paper Card
Yuan1z0825/nature-skills
Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.
Content Research Writer
weapp-tailwindcss/weapp-tailwindcss
Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.
Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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…
Related
Categories
Questions about Icsme Workflow
What does Icsme Workflow do?
A skill your agent uses when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal…. Icsme Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when planning an IEEE ICSME project timeline from venue and track choice through abstract registration, paper submission, the early-decision cut and author-response rebuttal, notification, IEEE Xplore camera-ready, the ROSE-Festival artifact evaluation, and presentation, with backward-planning offsets for a maintenance/evolution paper and honest handling of the single-annual-round calendar.
When should I use Icsme Workflow?
Icsme Workflow fits situations like: planning an IEEE ICSME project timeline from venue and track choice through abstract registration; paper submission; the early-decision cut and author-response rebuttal; IEEE Xplore camera-ready.
How do I install Icsme Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-workflow -a claude-code`. Or copy the skill folder (ICSME-Skills/skills/icsme-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icsme-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Icsme Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-workflow -a codex`. Or copy the skill folder (ICSME-Skills/skills/icsme-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icsme-workflow in your project. Codex loads it when a task matches its description.
Can I use Icsme 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 icsme-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/icsme-workflow, .gemini/skills/icsme-workflow, .github/skills/icsme-workflow and .opencode/skills/icsme-workflow in your project.
What does Icsme Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Icsme Workflow is instructions for the agent only.
Does Icsme 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 Icsme 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 Icsme Workflow use?
Icsme 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 Icsme 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 Icsme Workflow?
Skills that share tags, products or a category with Icsme Workflow: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icsme 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.