ECAI Skills

A 12-skill depth pack for ECAI (the European Conference on Artificial Intelligence, governed by EurAI): routing broad/symbolic and applied AI among the general-AI flagships, the abstract-then-full-paper two-deadline flow, double-blind EasyChair-style submission with a summary-reject phase and single-round rebuttal, the IOS Press Frontiers in Artificial Intelligence and Applications (FAIA) open-acc

by @brycewang-stanford 9 skills

Install

npx skillmds@latest add plugin:brycewang-stanford/ecai-skills

One command, no setup. In Claude Code it lands as a managed plugin you can enable, disable or remove with /plugin. On any other agent it installs the 9 skills into that agent's own folder.

Or inside Claude Code

In the Plugins tab, add this marketplace:

skillmds/skillmd
/plugin install brycewang-stanford-ecai-skills@skillmd

Adds the marketplace once; later plugins need the second line only.

Or install by hand

Download the plugin and unzip its skills/ folder into your agent's skills directory. Works with every agent, no CLI needed.

Download plugin Paths per agent

Just the markdown? SKILL.md files only.

This plugin

skills: 9
authors: 1

Published by a registry member. Review its skills before installing.

Skills in this plugin

▌
Ecai Submission · brycewang-stanford
Use when auditing an ECAI submission for readiness — the abstract-then-full-paper two-deadline flow, the tight 7-page body budget, double-blind anonymity, the correct template/publisher regime (ecai.cls/FAIA for a standalone ECAI vs ijcai.sty/IJCAI proceedings for the joint IJCAI-ECAI 2026), the per-author submission cap, the ethics statement, and desk-reject triage before the AoE cutoff.

1k repo stars
▌
Ecai Experiments · brycewang-stanford
Use when designing or auditing the evidence in an ECAI paper — choosing proof versus experiment by claim shape across ECAI's breadth (theory/KR, planning/search, ML, multi-agent, applied), fair baselines, seeds and spread, honest ablations, and provenance, all supporting a claim inside a 7-page body.

1k repo stars
▌
Ecai Related Work · brycewang-stanford
Use when writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic, learning, multi-agent, application) for a broad reviewer pool, writing delta-first positioning, keeping self-citations double-blind, and doing it within a tight reference budget (1 page standalone / 2 pages in IJCAI-ECAI 2026).

1k repo stars
▌
Ecai Supplementary · brycewang-stanford
Use when deciding what goes in the ECAI 7-page body versus the anonymized supplement — splitting content by decision-criticality so nothing a reviewer needs to judge the paper lives outside the tight body, given there is no unlimited in-paper appendix and no separate artifact track.

1k repo stars
▌
Ecai Writing Style · brycewang-stanford
Use when writing or tightening an ECAI paper body — leading with a general-AI contribution on the first page, matching evidence to claim (a theorem and construction, or a fair empirical comparison), and doing it inside a 7-page body where every paragraph must earn its space.

1k repo stars
▌
Ecai Review Process · brycewang-stanford
Use when reasoning about how an ECAI submission is evaluated — double-blind review, the summary-reject first phase, area chairs / senior PC, the single author-response (rebuttal) window, an accept/reject decision (no journal-style major-revision round), and how ECAI's process and its joint IJCAI-ECAI 2026 form differ from AAAI, IJCAI standalone, and AAMAS.

1k repo stars
▌
Ecai Reproducibility · brycewang-stanford
Use when building the reproducibility story for an ECAI paper — a complete proof appendix for theory/KR work, a seeded and cached package for empirical/ML work, provenance pinning for datasets and models, and an anonymized supplement that satisfies double-blind review inside ECAI's tight 7-page body with no separate artifact track.

1k repo stars
▌
Ecai Topic Selection · brycewang-stanford
Use before writing to decide whether a project belongs at ECAI versus IJCAI, AAAI, AAMAS, KR, or a pure-ML venue, and whether it should go to the ECAI main track or the co-located PAIS applications track — using contribution shape, the model-swap test, the European/general-AI fit, and the calendar (including the joint IJCAI-ECAI 2026 cycle).

1k repo stars
▌
Ecai Artifact Evaluation · brycewang-stanford
Use when planning the reproducibility/artifact story for an ECAI paper — noting that ECAI/FAIA has NO ACM/IEEE-style artifact-badging committee, so credibility is carried by the paper and its supplement and judged by the same reviewers, and adapting an ML-style reproducibility package (or a complete proof appendix for theory work) to that reality.

1k repo stars