Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
A skill your agent uses to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal…
Install Ecai Workflow
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-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/ECAI-Skills/skills/ecai-workflow .claude/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .claude/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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/ECAI-Skills/skills/ecai-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 ecai-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-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/ECAI-Skills/skills/ecai-workflow .agents/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .agents/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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 ecai-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-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/ECAI-Skills/skills/ecai-workflow .cursor/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .cursor/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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 ECAI-Skills/skills/ecai-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 ecai-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-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/ECAI-Skills/skills/ecai-workflow .gemini/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .gemini/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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 ecai-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 ecai-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/ECAI-Skills/skills/ecai-workflow .github/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .github/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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 ecai-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 ecai-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/ECAI-Skills/skills/ecai-workflow .opencode/skills/ecai-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 "ecai-workflow" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-workflow into .opencode/skills/ecai-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-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
ecai-workflow- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 458 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal…
- Plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step
- SKILL.md covers The IJCAI-ECAI 2026 calendar…, Backward plan from the paper…, After submission and Parallel tracks to run early, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Summary-reject phase
What it does
Ecai Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.
Its SKILL.md is about 1.3k 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
- Plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step
- Summary-reject phase
- Rebuttal window
- The open-access camera-ready
Example prompts
- “/ecai-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
Ecai Workflow loads about 1.3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 458 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). 458 words, ~1,255 tokens.
Download SKILL.mdSave it as
.claude/skills/ecai-workflow/SKILL.md (or your agent's skills folder).- name
- ecai-workflow
- description
- Use to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.
ECAI Workflow
Plan the ECAI year backward from the paper deadline, because ECAI is a single-round process with a two-deadline front (abstract, then paper) and no revision round to catch a gap later. First fix which regime the edition is in — it changes the calendar owner, the template, and whether PAIS is available:
- Standalone ECAI (e.g. 2024): EurAI + a host society; FAIA/
ecai.cls; PAIS co-located. - IJCAI-ECAI 2026: joint with IJCAI in Bremen (15-21 Aug 2026); IJCAI process/template/proceedings.
The IJCAI-ECAI 2026 calendar (verify on the live page)
Abstract deadline .............. 12 January 2026 (AoE) <- title/abstract/authors/topics locked
Full paper deadline ............ 19 January 2026 (AoE) <- anonymized PDF + supplement
Summary-reject notification .... 4 March 2026 <- early filter; below-bar/out-of-scope out
Author response (rebuttal) ..... 7-10 April 2026 <- one short window, factual corrections
Final notification ............. 29 April 2026 <- accept / reject (no revision round)
Camera-ready ................... (per author kit) <- de-anonymize, open-access production
Conference ..................... 15-21 August 2026, BremenFor a standalone ECAI the shape is the same (registration ~1 week before the PDF; double-blind review with a rebuttal; open-access FAIA proceedings) but the dates and organizer differ — read the current call.
Backward plan from the paper deadline
- Deadline − 12 weeks: decide ECAI vs IJCAI/AAAI and main track vs PAIS
(
ecai-topic-selection). Routing before writing is the highest-leverage move, because the 7-page budget and the venue's breadth shape the paper. - − 10 weeks: lock the contribution and the evidence type (proof vs experiment) per claim
shape (
ecai-experiments); name threats/assumptions now — you cannot add them in a later round. - − 8 weeks: draft the body to the first-page arc and the 7-page budget
(
ecai-writing-style); start the anonymized supplement (ecai-reproducibility). - − 4 weeks: finish full proofs / complete experiments with seeds and spread; write delta-first
related work (
ecai-related-work). - − 2 weeks: internal review; run the double-blind sweep and the body/supplement split
(
ecai-supplementary). - Abstract deadline: register title/abstract/authors/topics with the real text.
- Paper deadline: run
ecai-submissionend to end on the final PDF, supplement, template, and per-author cap.
Show full SKILL.md (204 more words)Show less
After submission
- Summary-reject phase: nothing to do but ensure you did not invite it — scope, formatting, anonymity, and page budget must have been correct at upload.
- Rebuttal window:
ecai-author-response— one short, precise, double-blind reply; fix factual misreadings and supply asked-for numbers; promise only minor camera-ready edits. - Notification:
- Accept →
ecai-camera-ready(de-anonymize, correct template/publisher regime, open-access forms, DOI/citation, register to present) and make the supplement a permanent open release (ecai-artifact-evaluation). - Reject → revise substantively and reroute (AAAI/IJCAI/specialist venue) or aim at the next
ECAI; there is no appeal that reopens the decision (
ecai-review-process).
- Accept →
Parallel tracks to run early
- Reproducibility is not a last-minute task. Seeds, cached outputs, and full proofs must be
produced as you do the work; they cannot be retrofitted at the deadline (
ecai-reproducibility). - PAIS decision is a fork, not an afterthought. A deployed-application paper aimed at PAIS leads with real-world impact and has its own call — decide before the abstract deadline.
- Per-author submission cap (IJCAI-ECAI 2026: 8) — coordinate across your group early so you do not have to withdraw a paper at the deadline.
Milestone checklist
[ ] Regime fixed: standalone ECAI (FAIA/PAIS) or joint IJCAI-ECAI (IJCAI)
[ ] Track chosen: main track vs PAIS
[ ] Evidence type set per claim (proof vs experiment); threats/assumptions named
[ ] Body drafted to 7-page arc; supplement started and anonymized
[ ] Abstract registered by the earlier deadline
[ ] Double-blind sweep + body/supplement split done before paper upload
[ ] Rebuttal plan ready for the response window
[ ] Camera-ready path (template/publisher/forms/DOI/registration) mappedReverify each cycle
Regime (standalone vs joint), all dates and AoE cutoffs, the per-author cap, the ethics/AI policy, and the camera-ready production instructions — none are stable across editions.
© 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 ECAI-Skills/skills/ecai-workflow of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ecai 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 |
|---|---|---|---|---|---|---|
| Ecai Workflow this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.8k | 15 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 46k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Read arXiv Paperkarpathy/nanochat | 58k | 2 repos | ~494 | Automated safety check: Pass | MIT | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | 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.
Read arXiv Paper
karpathy/nanochat
Fetches the TeX source of an arXiv paper from its URL, reads it and writes a markdown summary tied to the nanochat project.
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.
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 Ecai Workflow
What does Ecai Workflow do?
A skill your agent uses to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal…. Ecai Workflow is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step, summary-reject phase, rebuttal window, notification, and the open-access camera-ready, adapting to whether the edition is a standalone ECAI (FAIA/PAIS) or the joint IJCAI-ECAI 2026.
When should I use Ecai Workflow?
Ecai Workflow fits situations like: plan an ECAI campaign end to end — run the single-round year backward from the paper deadline through the abstract/registration step; summary-reject phase; rebuttal window; the open-access camera-ready.
How do I install Ecai Workflow in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-workflow -a claude-code`. Or copy the skill folder (ECAI-Skills/skills/ecai-workflow in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ecai-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Ecai Workflow in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-workflow -a codex`. Or copy the skill folder (ECAI-Skills/skills/ecai-workflow in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ecai-workflow in your project. Codex loads it when a task matches its description.
Can I use Ecai 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 ecai-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/ecai-workflow, .gemini/skills/ecai-workflow, .github/skills/ecai-workflow and .opencode/skills/ecai-workflow in your project.
What does Ecai Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Ecai Workflow is instructions for the agent only.
Does Ecai 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 Ecai 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 Ecai Workflow use?
Ecai 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 Ecai Workflow use?
About 1.3k tokens (SKILL.md is roughly 5k 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 Ecai Workflow?
Skills that share tags, products or a category with Ecai Workflow: Hypothesis Generation (spacering-net/codeg, 3.8k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars), Nature Paper Card (Yuan1z0825/nature-skills, 46k stars) and Read arXiv Paper (karpathy/nanochat, 58k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ecai 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.