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
Rss Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as…
MITAuto-check passed
Install Rss Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-artifact-evaluation .claude/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .claude/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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/RSS-Skills/skills/rss-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 rss-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-artifact-evaluation .agents/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .agents/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-artifact-evaluation .cursor/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .cursor/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 RSS-Skills/skills/rss-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 rss-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills rss-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/RSS-Skills/skills/rss-artifact-evaluation .gemini/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .gemini/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-artifact-evaluation .github/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .github/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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 rss-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 rss-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/RSS-Skills/skills/rss-artifact-evaluation .opencode/skills/rss-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 "rss-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/RSS-Skills/skills/rss-artifact-evaluation into .opencode/skills/rss-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rss-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
rss-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 645 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as…
- Packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code
- SKILL.md covers The robotics artifact stack, Review-time state (anonymous), Release-time state (public) and Mechanical anonymity sweep for…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Trained policies
What it does
Rss Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free open-access proceedings culture expects, without any badge program to structure it.
Its SKILL.md is about 1.5k 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 the artifacts behind an RSS (Robotics: Science and Systems) paper — code
- Trained policies
- Hardware documentation
- Footage — first as anonymous review-time evidence and then as the public release the venues free open-access proceedings culture expects
Example prompts
- “/rss-artifact-evaluation”
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
Rss Artifact Evaluation loads about 1.5k tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 645 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). 645 words, ~1,461 tokens.
Download SKILL.mdSave it as
.claude/skills/rss-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- rss-artifact-evaluation
- description
- Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free open-access proceedings culture expects, without any badge program to structure it.
RSS Artifact Evaluation
Package the artifacts as if a skeptical peer lab will pick them up — because at RSS, that is the actual evaluation mechanism. No badge track or artifact committee was verified for the 2026 cycle (待核实 each edition); the discipline is therefore self-imposed, and the reward is post-publication: RSS papers are free to every reader at roboticsproceedings.org, so strong artifacts get found and reused quickly.
The robotics artifact stack
Inventory what the paper's claims actually rest on, layer by layer:
| Layer | Artifact | Review-time state | Release state |
|---|---|---|---|
| Claim analysis | Scripts turning logs into tables | in supplement | public repo |
| Evidence corpus | Trial ledger + footage | anonymized | full, licensed |
| Learned components | Policy/model weights + training configs | weights or recipe | both |
| Software stack | Planner/controller code, sim environments | source in archive | tagged release |
| Hardware layer | Platform ledger, CAD for custom parts, BOM | described in PDF | files where possible |
| Protocol | Reset/intervention/success-criterion doc | in supplement | versioned doc |
The stack ordering is a triage order: the top layers are cheap and non-negotiable; the bottom layers may be partially closed for legitimate reasons — but each closure needs one honest sentence in the paper.
Review-time state (anonymous)
- Everything ships through the supplementary channel by its own deadline
(
rss-supplementary); no external links — the 2026 CFP admits links only in the camera-ready. - Scrub authorship trails ML packaging misses: ROS package names carrying lab acronyms, URDF files naming custom rigs after people, commit history, notebook metadata, cluster paths.
- Optimize for a ten-minute inspection: a reviewer who opens the archive should be able to regenerate one small table and watch one labeled clip without reading documentation twice.
Release-time state (public)
- Swap placeholders for a public repository, choose a real license (code and data may need different ones), and archive a citable snapshot (e.g., a DOI-minting service) so citations outlive lab servers.
- Publish the trial ledger and analysis scripts together — this is the pairing that lets others audit rather than merely admire the result.
- Weights too large to host? Publish the training recipe, seeds, and the evaluation harness, and say which reported numbers depend on the exact checkpoint.
- Update the camera-ready to point at the release; RSS explicitly welcomes links
there (
rss-camera-ready).
Mechanical anonymity sweep for robotics archives
Robotics repositories leak identity in places generic checklists never look; run greps before packaging:
# lab and platform tells in code, configs, and robot descriptions
grep -riE "(lab|univ|institute|group)[-_a-z]*" --include="*.yaml" --include="*.xacro" .
grep -rl "<your-lab-acronym>" . # ROS package prefixes
find . -name "*.urdf" -o -name "*.xacro" | xargs grep -l "author\|copyright"
# history and metadata
rm -rf .git; find . -name "*.ipynb" -exec jq '.metadata' {} \;
exiftool supplement_video.mp4 | grep -iE "creator|artist|gps|serial"Then rename: packages, launch files, and URDF link names that encode the lab or a person ("annas_gripper_v3") are as identifying as an author block.
Show full SKILL.md (244 more words)Show less
Sizing the inspection to reality
- Assume the archive gets ten minutes at review time and an afternoon post-publication; order the README for the ten-minute reader and link deeper.
- Put the one-command table regeneration first in the README; it is the highest belief-per-minute artifact the package contains.
- State expected runtimes next to every command — a reviewer who hits a silent 20-minute script assumes it is broken.
Handling the un-releasable
Robotics has honest closure cases — proprietary platforms, safety-critical controllers, partner data. The rule: closure is declared per stack layer, with a replication path around it ("the controller API is proprietary; we release the planner and the recorded command streams so the planning claim remains auditable"). What kills credibility is not the closed layer; it is discovering it after publication.
License and citation plumbing at release
- Code and data usually want different licenses; a permissive code license does not cover collected trial data or footage of identifiable environments.
- Third-party components inherited through the software stack (simulators, vendor SDKs, ROS packages) carry terms that survive your packaging — audit before promising "fully open."
- Add a machine-readable citation file pointing at the roboticsproceedings.org
entry and its
10.15607/RSS.*DOI, so downstream users cite the venue version rather than a preprint. - Pin a release tag matching the camera-ready ("as-published"); development can continue on main without eroding the paper's evidentiary snapshot.
- Record hosting longevity: lab servers rot, which is why the citable snapshot in an archival service is the load-bearing copy.
Output format
[Stack inventory] <layer -> artifact -> state>
[Ten-minute test] table regenerated <y/n> | clip labeled <y/n>
[Anonymity findings] <ros-names/urdf/history/paths>
[Closure declarations] <layer -> reason -> replication path>
[Release checklist] repo / license / citable snapshot / ledger+scripts / camera-ready link© 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 RSS-Skills/skills/rss-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Rss 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 |
|---|---|---|---|---|---|---|
| Rss Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.5k | 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 | |
| Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Fast Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.6k | 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…
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…
Issta Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ISSTA tool, benchmark, and results for the artifact-evaluation track, covering the ACM badges (Artifacts Available via Zenodo, Evaluated Functional and…
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 Rss Artifact Evaluation
What does Rss Artifact Evaluation do?
A skill your agent uses when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as…. Rss Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code, trained policies, trial ledgers, hardware documentation, and footage — first as anonymous review-time evidence and then as the public release the venue's free open-access proceedings culture expects, without any badge program to structure it.
When should I use Rss Artifact Evaluation?
Rss Artifact Evaluation fits situations like: packaging the artifacts behind an RSS (Robotics: Science and Systems) paper — code; trained policies; hardware documentation; footage — first as anonymous review-time evidence and then as the public release the venues free open-access proceedings culture expects.
How do I install Rss Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-artifact-evaluation -a claude-code`. Or copy the skill folder (RSS-Skills/skills/rss-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/rss-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Rss Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill rss-artifact-evaluation -a codex`. Or copy the skill folder (RSS-Skills/skills/rss-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/rss-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Rss 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 rss-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/rss-artifact-evaluation, .gemini/skills/rss-artifact-evaluation, .github/skills/rss-artifact-evaluation and .opencode/skills/rss-artifact-evaluation in your project.
What does Rss Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Rss Artifact Evaluation is instructions for the agent only.
Does Rss 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 Rss 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 Rss Artifact Evaluation use?
Rss 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 Rss Artifact Evaluation use?
About 1.5k tokens (SKILL.md is roughly 5.8k 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 Rss Artifact Evaluation?
Skills that share tags, products or a category with Rss 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 Mobisys 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 Rss 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.