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
Isca Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets…
MITAuto-check passed
Install Isca Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-artifact-evaluation .claude/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .claude/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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/ISCA-Skills/skills/isca-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 isca-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-artifact-evaluation .agents/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .agents/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-artifact-evaluation .cursor/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .cursor/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 ISCA-Skills/skills/isca-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 isca-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills isca-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/ISCA-Skills/skills/isca-artifact-evaluation .gemini/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .gemini/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-artifact-evaluation .github/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .github/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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 isca-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 isca-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/ISCA-Skills/skills/isca-artifact-evaluation .opencode/skills/isca-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 "isca-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ISCA-Skills/skills/isca-artifact-evaluation into .opencode/skills/isca-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "isca-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
isca-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 717 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets…
- Packaging simulator-heavy workflows others can run
- SKILL.md covers Decide scope first: which…, Simulator-heavy artifacts: the…, The package an evaluator can… and The badge set under ACM's policy, plus 3 more sections
- Calls docker
- Writing the evaluator-facing appendix
What it does
Isca Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
Its SKILL.md is about 1.6k 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 simulator-heavy workflows others can run
- Writing the evaluator-facing appendix
- Earning badges that print on the paper
Example prompts
- “/isca-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
Shell commands in SKILL.md call:
docker
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.
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
Isca Artifact Evaluation loads about 1.6k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 717 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). 717 words, ~1,639 tokens.
Download SKILL.mdSave it as
.claude/skills/isca-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- isca-artifact-evaluation
- description
- Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
ISCA Artifact Evaluation
The verified 2026 arrangement: authors of accepted papers could voluntarily submit artifacts, assessed under the ACM Artifact Review and Badging policy, with earned badges printed on the paper and attached as ACM Digital Library metadata — and with no effect on the acceptance decision itself. The conference framed AE as a recent, deliberate import into the architecture community (following ASPLOS from 2020 and MICRO from 2021). Voluntary does not mean optional in practice: badges are becoming the community's default trust signal, and an architecture paper without them increasingly gets asked why.
Decide scope first: which claims does the artifact defend?
Architecture artifacts fail most often from over-promising. Before packaging, split the paper's results three ways and say so in the artifact documentation:
| Tier | Contents | Evaluator experience |
|---|---|---|
| Reproduce | Headline figure(s) + key ablation, runnable on evaluator-accessible machines within hours | Runs it, matches within stated tolerance |
| Regenerate-with-resources | Full sweeps needing cluster-days; scripts and configs complete, cost stated honestly | Inspects, spot-runs a slice |
| Inspect-only | Anything needing hardware evaluators won't have (FPGA boards, silicon, internal traces) | Reads code + recorded raw outputs; verifies the pipeline from raw to figure |
Declaring tier boundaries up front converts "couldn't run everything" from a failure into the documented plan. Never gate the Reproduce tier on proprietary inputs — substitute an open workload subset and show it preserves the trend.
Simulator-heavy artifacts: the specific frictions
- Wall-clock honesty. Cycle-level simulation of full suites is CPU-months; evaluators have days. Ship reduced-input or single-region variants of the headline experiment, with the full-run manifests alongside. State expected runtimes per step, measured, not guessed.
- Build fragility. Simulator trees with local patches break on new toolchains. Ship a container image with everything pre-built, and the from-source path for evaluators who distrust images.
- Tolerance statement. Define "match": bit-identical stats for deterministic runs; a stated percentage band where sampling or threading varies. An evaluator staring at 33.7% vs the paper's 34% needs the band in writing.
- Third-party licenses. SPEC-class suites cannot be redistributed; ship build recipes plus checksums, and include one freely redistributable workload so the pipeline is exercisable end to end regardless.
The package an evaluator can drive blind
artifact/
README.md # claims-to-experiments map; runtimes; tolerance bands
INSTALL.md # container route + source route, both tested cold
run_all.sh # Reproduce tier end to end, one command
experiments/
f07-headline/ # regen.sh + manifest.ini per figure (from
f09-ablation/ # isca-reproducibility — same manifests, reused)
expected/ # our raw outputs + final CSVs, for diffing
workloads/ # free subset included; licensed suite: recipe + checksums
LICENSEThe README's first section is a claims table: paper claim → figure → command → expected output → tolerance. Evaluators grade against exactly this table; making them reverse-engineer the mapping from the paper costs goodwill and, frequently, a badge.
# Cold-start rehearsal — run on a machine that has never seen the project
docker load < artifact-image.tar.gz
docker run --rm -it artifact:v1 bash -lc './run_all.sh --tier reproduce'
diff <(csvcut -c workload,ipc results/f07.csv) \
<(csvcut -c workload,ipc expected/f07.csv) # within README tolerance?Have a group member outside the project do this rehearsal before submission; every question they ask is a missing README paragraph.
Show full SKILL.md (309 more words)Show less
The badge set under ACM's policy
The ACM Review and Badging framework distinguishes availability badging (the artifact is permanently retrievable from an archival location) from functional and results-oriented badging (the artifact works as documented; the paper's results can be obtained with it). Practical mapping:
- Availability is cheap and unconditional: deposit the evaluated snapshot with a DOI-issuing archive (a lab GitHub alone is not archival). Do this even if you pursue nothing else.
- Functionality rides on documentation and the cold-start test.
- Results reproduction rides on the Reproduce tier's design: modest runtime, clear tolerance, deterministic where possible.
Which badges ISCA 2027 requests, the AE calendar, and the committee's platform offerings (cloud credits, provided machines) are per-edition decisions — 待核实 against the 2027 AE page when it exists.
Working with evaluators
Architecture AE is conventionally collaborative and iterative: evaluators hit a
wall, authors fix and resubmit within the AE window. Budget author-days for this
in the post-acceptance calendar (isca-workflow), respond within a day while
the evaluator's context is warm, and version every fix (artifact:v1.1,
changelog in the README) so the final badge attaches to an identifiable object.
Timing and division of labor
AE happens in the same weeks as camera-ready preparation and talk writing.
Assign the artifact to someone who ran the original experiments — packaging is
recall-heavy — and start from the submission-time snapshot that
isca-reproducibility froze in November, not from the current dev tree, which
has drifted.
Submission gate
- Claims table complete: every badge-relevant figure mapped to a command
- Cold-start rehearsal passed by a non-author on a clean machine
- Runtimes measured and stated per step; tolerance bands written
- Container + source routes both build
- Licensed workloads handled by recipe; free subset runs end to end
- Archival deposit made; DOI in the camera-ready's artifact statement
Venue facts verified 2026-07-08 (../../resources/official-source-map.md);
badge definitions follow ACM's published badging policy — check the version the
2027 AE chairs cite.
© 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 ISCA-Skills/skills/isca-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Isca 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 |
|---|---|---|---|---|---|---|
| Isca Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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 | |
| LLM Evaluationdavila7/claude-code-templates | 32k | 12 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Web Artifacts Builderanthropics/skills | 180k | 41 repos | ~769 | Automated safety check: Pass | Apache-2.0 | |
| Micro Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.7k | 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).
LLM Evaluation
davila7/claude-code-templates
Master comprehensive evaluation strategies for LLM applications, from automated metrics to human evaluation and A/B testing.
- Official
Web Artifacts Builder
anthropics/skills
Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.
Micro Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing a MICRO artifact for post-acceptance evaluation — packaging simulators, configs, traces, and scripts so evaluators can regenerate the paper's figures…
Asplos Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when preparing an ASPLOS artifact for the post-acceptance evaluation committee — writing the ae.tex Artifact Appendix with software/hardware/dataset dependencies, targeting…
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 Isca Artifact Evaluation
What does Isca Artifact Evaluation do?
A skill your agent uses when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets…. Isca Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when preparing an accepted ISCA paper's artifact for evaluation under the ACM Review and Badging policy — scoping which results are reproducible within evaluator budgets, packaging simulator-heavy workflows others can run, writing the evaluator-facing appendix, and earning badges that print on the paper.
When should I use Isca Artifact Evaluation?
Isca Artifact Evaluation fits situations like: packaging simulator-heavy workflows others can run; writing the evaluator-facing appendix; earning badges that print on the paper.
How do I install Isca Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-artifact-evaluation -a claude-code`. Or copy the skill folder (ISCA-Skills/skills/isca-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/isca-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Isca Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-artifact-evaluation -a codex`. Or copy the skill folder (ISCA-Skills/skills/isca-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/isca-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Isca 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 isca-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/isca-artifact-evaluation, .gemini/skills/isca-artifact-evaluation, .github/skills/isca-artifact-evaluation and .opencode/skills/isca-artifact-evaluation in your project.
What does Isca Artifact Evaluation need to run?
Going by SKILL.md and its folder, Isca Artifact Evaluation needs the command-line tools its instructions call (docker). Our summary lists: Docker.
Does Isca Artifact Evaluation access the network?
SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Isca 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 Isca Artifact Evaluation use?
Isca 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 Isca Artifact Evaluation use?
About 1.6k tokens (SKILL.md is roughly 6.6k 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 Isca Artifact Evaluation?
Skills that share tags, products or a category with Isca Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Artifacts Builder (nexu-io/open-design, 100k stars), LLM Evaluation (davila7/claude-code-templates, 32k stars) and Web Artifacts Builder (anthropics/skills, 180k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Isca Artifact Evaluation?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,228 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.