Ieee Paper Reader
CloudWave818/ieee-skills
Read, decompose, and analyze IEEE-style papers using routed technical-reading workflows.
A skill your agent uses when writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic, learning, multi-agent, application) for a broad reviewer pool, writing…
Install Ecai Related Work
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-related-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-related-work --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-related-work .claude/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .claude/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-workType 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-related-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-related-work --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-related-work .agents/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .agents/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-related-work --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-related-work .cursor/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .cursor/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-work--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-related-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills ecai-related-work --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-related-work .gemini/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .gemini/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-workInstalls 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-related-work -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-related-work .github/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .github/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-work -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-related-work --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-related-work .opencode/skills/ecai-related-work && 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-related-work" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ECAI-Skills/skills/ecai-related-work into .opencode/skills/ecai-related-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ecai-related-work", 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-related-work- GitHub stars
- 1.2k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 477 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic, learning, multi-agent, application) for a broad reviewer pool, writing…
- Writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic
- SKILL.md covers Cover the lanes a general-AI…, Delta-first positioning, Keep it double-blind and Budget discipline, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Application) for a broad reviewer pool
What it does
Ecai Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
Its SKILL.md is about 1.1k 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, covering Literature review, Citation management and Positioning and messaging. 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
- Writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic
- Application) for a broad reviewer pool
- Writing delta-first positioning
- Keeping self-citations double-blind
Example prompts
- “/ecai-related-work”
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 (its code samples are bash).
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 Related Work loads about 1.1k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 477 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). 477 words, ~1,085 tokens.
Download SKILL.mdSave it as
.claude/skills/ecai-related-work/SKILL.md (or your agent's skills folder).- name
- ecai-related-work
- description
- 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).
ECAI Related Work
ECAI's related work has a peculiar difficulty: the reviewer pool is broad (a planning paper may draw a KR reviewer and an ML reviewer), yet the space is tiny — the body is 7 pages and references overflow into only 1 page (standalone ECAI) or 2 pages (IJCAI-ECAI 2026). You must position against the right lanes for a general audience and stay compact.
Cover the lanes a general-AI reviewer will expect
Identify which AI lanes your contribution touches and place it in each — a broad reviewer will fault a section that only cites its author's home subfield:
- Symbolic / foundational lane — the KR, planning, search, reasoning, or argumentation line your problem sits in.
- Learning lane — the ML/statistical methods your work uses or competes with.
- Multi-agent / decision lane — if agents, game-theoretic, or sequential-decision aspects apply.
- Application lane — the real-world domain, especially for a PAIS-flavored contribution.
- Cross-venue neighbors — the closest work at IJCAI, AAAI, AAMAS, KR, or a specialist venue, so a reviewer from that community sees you know the field's flagship results.
You will not cover all lanes deeply at 7+1(2) pages — cover the ones your claim actually engages, and cite the canonical entry point for the rest.
Delta-first positioning
Do not write an annotated bibliography. For each closest competitor, state the delta in one sentence: what they do, and precisely what you do differently or additionally.
"Prior learned-heuristic planners plug the model in directly and lose completeness [refs]; we preserve completeness and a (1+ε) bound via per-state switching."
Delta-first writing does three jobs at once in minimal space: it credits prior work, states your novelty, and pre-empts the "how is this different from [X]?" reviewer question.
Show full SKILL.md (200 more words)Show less
Keep it double-blind
ECAI is double-blind. Self-citations are the classic leak:
- Cite your own prior work in the third person ("Smith et al. [7] showed...") — never "in our previous work [7]."
- Do not let the density or phrasing of self-citations reveal the author group.
- Anonymize a system name that identifies you if it appears in the comparison.
# Catch first-person self-citation and identity leaks in related work
grep -nEi 'our (previous|prior|earlier) (work|paper|system|approach)|we previously' paper.tex | headBudget discipline
- The reference pages are 1 page (standalone) or 2 pages (IJCAI-ECAI 2026) — finite. Prune to the works that position the contribution, not every paper you read.
- Prefer the canonical citation for a well-known result over three secondary ones.
- Move an extended survey-style discussion to the supplement if it is not decision-critical
(
ecai-supplementary); keep the delta-establishing citations in the body. - Do not pad the reference list to signal thoroughness — a broad reviewer notices citations that do no positioning work.
Common failure modes
- Home-subfield tunnel vision — a planning paper that ignores the learning lane it competes with, or an ML paper blind to the symbolic literature it reinvents.
- Bibliography, not positioning — listing works without stating the delta.
- First-person self-citation breaking double-blind.
- Missing the obvious neighbor at IJCAI/AAAI/AAMAS/KR that a specialist reviewer will know by heart.
- Reference-budget overflow forcing body cuts (
ecai-submission).
Output format
[Lanes covered] symbolic / learning / multi-agent / application / cross-venue — which apply, all present?
[Delta statements] each closest competitor -> one-sentence delta? gaps: <list>
[Double-blind] self-citations third-person; no identifying system names? yes/no
[Budget] reference pages within 1 (standalone) / 2 (2026); extended survey moved to supplement?
[Neighbor check] closest IJCAI/AAAI/AAMAS/KR result cited? yes/no© 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-related-work of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Ecai Related Work 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 Related Work this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Ieee Paper ReaderCloudWave818/ieee-skills | 359 | — | ~591 | Automated safety check: Pass | MIT | |
| Gec Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~855 | Automated safety check: Pass | None | |
| Jpe Literature Positioningfranklee16/academic-research-skills | 223 | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Systematic Review ScreenerImbad0202/academic-research-skills | 51k | — | ~8.4k | Automated safety check: Pass | Custom licence | |
| Literature Reviewneflibata-feng/MyArxiv-Agent | 126 | 20 repos | ~5.9k | Automated safety check: Notes | MIT |
Similar skills
Gec Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when positioning a Global Environmental Change (GEC) manuscript against the relevant literatures.
Jpe Literature Positioning
franklee16/academic-research-skills
A skill your agent uses when writing or repairing the introduction and related-work framing for a Journal of Political Economy (JPE) manuscript — situating the contribution in the economics…
Systematic Review Screener
Imbad0202/academic-research-skills
Screens records for systematic, scoping and rapid reviews against fixed eligibility rules, using two blinded AI reviewers and a third adjudicator, with traceable PRISMA counts.
Literature Review
neflibata-feng/MyArxiv-Agent
Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.).
Preprint Search on bioRxiv
LigphiDonk/Oh-my--paper
Searches bioRxiv life sciences preprints by keyword, author, date range or category with a Python script, returning JSON metadata and optional PDF downloads.
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 Related Work
What does Ecai Related Work do?
A skill your agent uses when writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic, learning, multi-agent, application) for a broad reviewer pool, writing…. Ecai Related Work is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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).
When should I use Ecai Related Work?
Ecai Related Work fits situations like: writing the ECAI related-work section — covering the relevant general-AI lanes (symbolic; application) for a broad reviewer pool; writing delta-first positioning; keeping self-citations double-blind.
How do I install Ecai Related Work in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-related-work -a claude-code`. Or copy the skill folder (ECAI-Skills/skills/ecai-related-work in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/ecai-related-work in your project. Claude Code loads it when a task matches its description.
How do I install Ecai Related Work in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ecai-related-work -a codex`. Or copy the skill folder (ECAI-Skills/skills/ecai-related-work in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/ecai-related-work in your project. Codex loads it when a task matches its description.
Can I use Ecai Related Work 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-related-work -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-related-work, .gemini/skills/ecai-related-work, .github/skills/ecai-related-work and .opencode/skills/ecai-related-work in your project.
What does Ecai Related Work need to run?
SKILL.md names no scripts, command-line tools or credentials: Ecai Related Work is instructions for the agent only.
Does Ecai Related Work 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 Related Work 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 Related Work use?
Ecai Related Work 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 Related Work use?
About 1.1k tokens (SKILL.md is roughly 4.3k 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 Related Work?
Skills that share tags, products or a category with Ecai Related Work: Ieee Paper Reader (CloudWave818/ieee-skills, 359 stars), Gec Literature Positioning (franklee16/academic-research-skills, 223 stars), Jpe Literature Positioning (franklee16/academic-research-skills, 223 stars) and Systematic Review Screener (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ecai Related Work?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 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.