Arize Evaluator
github/awesome-copilot
Handles LLM-as-judge evaluation workflows on Arize including creating/updating evaluators, running evaluations on spans or experiments, managing tasks, trigger-run operations, column mapping, and…
Agent skill
Icsme Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed"…
MITAuto-check passed
Install Icsme Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .claude/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .claude/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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/ICSME-Skills/skills/icsme-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 icsme-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .agents/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .agents/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .cursor/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .cursor/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 ICSME-Skills/skills/icsme-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 icsme-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .gemini/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .gemini/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .github/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .github/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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 icsme-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 icsme-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/ICSME-Skills/skills/icsme-artifact-evaluation .opencode/skills/icsme-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 "icsme-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICSME-Skills/skills/icsme-artifact-evaluation into .opencode/skills/icsme-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icsme-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
icsme-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 561 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed"…
- Packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival
- SKILL.md covers The IEEE badges (verify the…, What ROSE evaluators open first, Packaging plan and Anonymized review artifact vs.…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Covering the IEEE Open Research Object and Research Object Reviewed badges
What it does
Icsme Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.
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.
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
- Packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival
- Covering the IEEE Open Research Object and Research Object Reviewed badges
- What evaluators check first
- DOI-issuing archives
Example prompts
- “Open Research Object”
- “Research Object Reviewed”
- “/icsme-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
Icsme Artifact Evaluation loads about 1.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 561 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). 561 words, ~1,374 tokens.
Download SKILL.mdSave it as
.claude/skills/icsme-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- icsme-artifact-evaluation
- description
- Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.
ICSME Artifact Evaluation
Use this for the artifact track. ICSME evaluates artifacts in the Joint Artifact Evaluation Track and ROSE Festival (ROSE = Recognizing and rewarding Open Science in software Engineering), shared with its co-located siblings SCAM and VISSOFT, and it awards the IEEE badge scheme — not ACM's four badges. Two things to internalize: the badges are earned by evaluators actually retrieving and using your package, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived).
The IEEE badges (verify the current set and names)
| Badge | What it certifies | What earns it |
|---|---|---|
| Open Research Object | The artifact is permanently, publicly retrievable and open | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) with an open license |
| Research Object Reviewed | The artifact was examined and is exercisable, well-structured, and documented | Evaluators can run/inspect it and confirm it supports the paper's claims |
A package can earn both badges if it is open and exercisable, well-structured, and documented for reuse and repurposing. Open Research Object is the low-cost, high-value badge (archive the package cleanly); Research Object Reviewed requires the evaluator's own inspection/run to succeed, so the failure mode is always "did not retrieve or run on their side," never "the idea was weak."
Do not import ACM badge names (Available / Functional / Reusable / Reproduced) — those are the ACM scheme used at FSE and other ACM venues. ICSME is an IEEE venue with the IEEE research-object badges. Using the wrong badge names is a tell that the artifact author has not read the ROSE call.
What ROSE evaluators open first
| Claim type | First thing inspected | Common failure caught |
|---|---|---|
| A maintenance tool | The README and one install/run command | Undocumented dependencies; only-works-on-authors'-laptop |
| A mining/evolution study | The scripts that turn the corpus into the paper's tables | Numbers in the PDF that no script reproduces |
| A mined dataset | The extraction scripts + the extracted corpus with SHAs | Query shipped, corpus missing; provenance unpinned |
| An LLM-based result | Cached prompts/outputs + model IDs | Requires live API keys; not reproducible |
Assume an evaluator gives your package a bounded time budget on a clean machine. Design for the first ten minutes to succeed.
Show full SKILL.md (203 more words)Show less
Packaging plan
[Container] ship a Dockerfile or a pinned environment (requirements/lockfile); avoid
"install these 40 things by hand"
[README] one-screen orientation: what it is, install, run the demo, reproduce each claim,
expected runtime and outputs
[Mapping] an explicit table: paper claim -> script -> expected result
[Corpus] the extracted mining dataset itself (or documented access), with SHAs and dates,
not just the query
[Provenance] repo SHAs, extraction dates, model IDs/dates, seeds, fork/bot handling
[License] an OSI-approved open license so the artifact can earn Open Research Object
[Archive] deposit in a DOI-issuing repository for a permanent, citable objectAnonymized review artifact vs. badge artifact
- At submission: the artifact is anonymized for the paper's reviewers — no owner strings, cluster paths, lab names, your own org's repos, or identity-revealing subject-system names.
- After acceptance: replace anonymized placeholders with the public, licensed, DOI-issuing archive; this is the version ROSE evaluators badge and the camera-ready cites.
Worked vignette: packaging a debt-detection tool + mining study
A paper contributes a technical-debt detection tool and a mining study of debt over release history.
To target both badges: ship a Docker image with the tool pre-built; a run_demo.sh that detects
debt on a small bundled repository in under a minute; a reproduce/ directory whose scripts
regenerate each table from logged mining results; a claim-to-script mapping in the README; the
extracted corpus with pinned SHAs and extraction dates; and an MIT/Apache license with a Zenodo DOI.
State honestly which results are turnkey and which need the full (slow) corpus re-mining.
Calibration
- The ROSE-Festival artifact deadline is after acceptance and shared with SCAM and VISSOFT; Journal-First papers are typically excluded — confirm eligibility on the current call.
- Badge names, the exact set offered, and whether evaluation is single- or double-anonymous vary by cycle — confirm on the current artifact/ROSE call.
Output format
[Target badges] Open Research Object / Research Object Reviewed
[Artifact role] anonymized review artifact / public badge artifact
[Contents] <tool/corpus/scripts/provenance/license>
[Ten-minute test] does retrieve + install + demo succeed on a clean machine? yes/no
[Claim mapping] <claim -> script -> expected result present? yes/no>
[Fixes before upload] <ordered list>© 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-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icsme 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 |
|---|---|---|---|---|---|---|
| Icsme Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Arize Evaluatorgithub/awesome-copilot | 40k | 1 repos | ~8.1k | Automated safety check: Notes | MIT | |
| Artifacts Buildernexu-io/open-design | 100k | — | ~347 | Automated safety check: Pass | Apache-2.0 | |
| Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~969 | Automated safety check: Pass | MIT | |
| Infocom Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Artifacts Builder
nexu-io/open-design
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).
Ccs Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging ACM CCS artifacts for the artifact-evaluation committee and the ACM badges — Artifacts Available, Artifacts Evaluated Functional, Artifacts Evaluated Reusable…
Infocom Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation…
Mobisys Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a MobiSys artifact for the Artifact Evaluation Committee — choosing among the three independent ACM badges (Available, Evaluated–Functional, Results…
Fast Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging a USENIX FAST artifact for the USENIX Artifact Evaluation scheme (Artifacts Available, Artifacts Functional, Results Reproduced), covering what a storage AEC…
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…
Questions about Icsme Artifact Evaluation
What does Icsme Artifact Evaluation do?
A skill your agent uses when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed"…. Icsme Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival, covering the IEEE "Open Research Object" and "Research Object Reviewed" badges, what evaluators check first, DOI-issuing archives, evaluator-proof documentation, the shared track with SCAM and VISSOFT, and the separate post-acceptance deadline.
When should I use Icsme Artifact Evaluation?
Icsme Artifact Evaluation fits situations like: packaging an IEEE ICSME artifact for the Joint Artifact Evaluation Track and ROSE Festival; covering the IEEE Open Research Object and Research Object Reviewed badges; what evaluators check first; DOI-issuing archives.
How do I install Icsme Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-artifact-evaluation -a claude-code`. Or copy the skill folder (ICSME-Skills/skills/icsme-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icsme-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Icsme Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icsme-artifact-evaluation -a codex`. Or copy the skill folder (ICSME-Skills/skills/icsme-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icsme-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Icsme 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 icsme-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/icsme-artifact-evaluation, .gemini/skills/icsme-artifact-evaluation, .github/skills/icsme-artifact-evaluation and .opencode/skills/icsme-artifact-evaluation in your project.
What does Icsme Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Icsme Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Icsme 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 Icsme 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 Icsme Artifact Evaluation use?
Icsme 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 Icsme Artifact Evaluation use?
About 1.4k tokens (SKILL.md is roughly 5.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 Icsme Artifact Evaluation?
Skills that share tags, products or a category with Icsme Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Artifacts Builder (nexu-io/open-design, 100k stars), Ccs Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Infocom Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icsme 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.