Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Agent skill
Icalp Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete…
Install Icalp Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icalp-artifact-evaluation --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/ICALP-Skills/skills/icalp-artifact-evaluation .claude/skills/icalp-artifact-evaluation && 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 "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .claude/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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/ICALP-Skills/skills/icalp-artifact-evaluationType 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 icalp-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icalp-artifact-evaluation --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/ICALP-Skills/skills/icalp-artifact-evaluation .agents/skills/icalp-artifact-evaluation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .agents/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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 icalp-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icalp-artifact-evaluation --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/ICALP-Skills/skills/icalp-artifact-evaluation .cursor/skills/icalp-artifact-evaluation && 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 "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .cursor/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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 ICALP-Skills/skills/icalp-artifact-evaluation--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 icalp-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icalp-artifact-evaluation --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/ICALP-Skills/skills/icalp-artifact-evaluation .gemini/skills/icalp-artifact-evaluation && 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 "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .gemini/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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 icalp-artifact-evaluationInstalls 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 icalp-artifact-evaluation -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/ICALP-Skills/skills/icalp-artifact-evaluation .github/skills/icalp-artifact-evaluation && 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 "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .github/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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 icalp-artifact-evaluation -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 icalp-artifact-evaluation --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/ICALP-Skills/skills/icalp-artifact-evaluation .opencode/skills/icalp-artifact-evaluation && 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 "icalp-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICALP-Skills/skills/icalp-artifact-evaluation into .opencode/skills/icalp-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icalp-artifact-evaluation", 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
icalp-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~964 tokens
- SKILL.md length
- 419 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete…
- Understand why ICALP (EATCS) has no artifact-evaluation track
- SKILL.md covers Why no artifact track, What plays the artifact's role, When your paper DOES contain… and Do not, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- What plays the equivalent role for a pure-theory paper — the full version with complete proofs
What it does
Icalp Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.
Its SKILL.md is about 960 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
- Understand why ICALP (EATCS) has no artifact-evaluation track
- What plays the equivalent role for a pure-theory paper — the full version with complete proofs
- Reproducible computational certificates
- Optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate
Example prompts
- “/icalp-artifact-evaluation”
Requirements
- Docker
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
Icalp Artifact Evaluation loads about 964 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 419 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). 419 words, ~964 tokens.
Download SKILL.mdSave it as
.claude/skills/icalp-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- icalp-artifact-evaluation
- description
- Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.
ICALP Artifact Evaluation (there isn't one — and what replaces it)
Read this first if you are arriving from a venue with an artifact track. ICALP has no artifact evaluation, no artifact-evaluation committee, and no ACM/IEEE badges. It is a pure theoretical computer science venue: the contribution is a theorem, and the "artifact" a referee cares about is the proof. Building a Docker image, a benchmark harness, or a reproducibility capsule for an ICALP submission is effort spent on something no one will evaluate — and can even signal that the paper is mis-routed.
Why no artifact track
- ICALP results are mathematical: correctness is established by a proof a referee checks, not by running code on a machine.
- The community norm and the LIPIcs open-access model center the published proof and the full version, not a software deliverable.
- Contrast the software-engineering / systems / ML world (ACM/IEEE Available–Functional–Reusable– Reproduced badges, or ML reproducibility checklists): those exist because the contribution is a system or an empirical result. At ICALP it is not.
What plays the artifact's role
| Systems/ML artifact concept | ICALP equivalent |
|---|---|
| "Artifacts Available" (archived, DOI) | The full version on arXiv/ECCC/HAL, and the open-access LIPIcs paper |
| "Functional" (it runs) | The proof is complete and checkable in the appendix / full version |
| "Reproduced" (results re-obtained) | An expert re-derives / verifies the proof; certificates for any computation |
| Reproducibility capsule | A machine-checked formalization (Coq/Lean/Isabelle), when provided |
So the "artifact" work for an ICALP paper is: write the complete proofs, make any computation
checkable (icalp-experiments, icalp-reproducibility), and optionally formalize the central
theorem.
Show full SKILL.md (168 more words)Show less
When your paper DOES contain software
Some ICALP papers include an implementation or a computer-assisted proof. Even then, there is no badge track — but you should still:
- Make the code reproducible and reference it at camera-ready (public repo, or Zenodo/Software Heritage for a DOI), primarily to support the proof, not as a graded artifact.
- Provide certificates an independent checker can verify where the method allows.
- Keep any such repository from breaking anonymity during lightweight double-blind review.
If the implementation/experiment is the actual contribution rather than support for a theorem, that
is a routing signal: an experimental-algorithms track (e.g. ALENEX/ESA's experimental track), a
systems venue, or a database/ML venue may be the right home — see icalp-topic-selection.
Do not
- Do not build an artifact-evaluation package for ICALP; there is nothing to submit it to.
- Do not import ACM/IEEE badge language or an ML reproducibility-checklist artifact into the paper.
- Do not assume a future ICALP will add an artifact track without checking the live call (待核实 if ever announced).
Output format
[Artifact track?] none at ICALP (pure-theory venue)
[Proof-as-artifact] complete proofs in full version? yes/no
[Computation support] certificates / reproducible code where a proof uses computation? n/a or yes/no
[Formalization] none / partial / archived+cited (optional, not required)
[Routing flag] is software the real contribution (=> reconsider venue)? 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 ICALP-Skills/skills/icalp-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icalp Artifact Evaluation 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 |
|---|---|---|---|---|---|---|
| Icalp Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~964 | 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 | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.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.
Last30days
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
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 Icalp Artifact Evaluation
What does Icalp Artifact Evaluation do?
A skill your agent uses to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete…. Icalp Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use to understand why ICALP (EATCS) has no artifact-evaluation track or badge scheme, and what plays the equivalent role for a pure-theory paper — the full version with complete proofs, reproducible computational certificates, and optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.
When should I use Icalp Artifact Evaluation?
Icalp Artifact Evaluation fits situations like: understand why ICALP (EATCS) has no artifact-evaluation track; what plays the equivalent role for a pure-theory paper — the full version with complete proofs; reproducible computational certificates; optional machine formalization — so authors coming from a systems/ML venue do not waste effort building an artifact ICALP does not evaluate.
How do I install Icalp Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-artifact-evaluation -a claude-code`. Or copy the skill folder (ICALP-Skills/skills/icalp-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icalp-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Icalp Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icalp-artifact-evaluation -a codex`. Or copy the skill folder (ICALP-Skills/skills/icalp-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icalp-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Icalp Artifact Evaluation 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 icalp-artifact-evaluation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icalp-artifact-evaluation, .gemini/skills/icalp-artifact-evaluation, .github/skills/icalp-artifact-evaluation and .opencode/skills/icalp-artifact-evaluation in your project.
What does Icalp Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Icalp Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Icalp Artifact Evaluation 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 Icalp Artifact Evaluation 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 Icalp Artifact Evaluation use?
Icalp Artifact Evaluation 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 Icalp Artifact Evaluation use?
About 964 tokens (SKILL.md is roughly 3.9k 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 Icalp Artifact Evaluation?
Skills that share tags, products or a category with Icalp Artifact Evaluation: 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 Icalp Artifact Evaluation?
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.