Scientific Thinking Scholar Evaluation
affaan-m/ECC
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Agent skill
Iros Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code…
MITAuto-check passed
Install Iros Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-artifact-evaluation .claude/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .claude/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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/IROS-Skills/skills/iros-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 iros-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-artifact-evaluation .agents/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .agents/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-artifact-evaluation .cursor/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .cursor/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 IROS-Skills/skills/iros-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 iros-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills iros-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/IROS-Skills/skills/iros-artifact-evaluation .gemini/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .gemini/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-artifact-evaluation .github/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .github/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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 iros-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 iros-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/IROS-Skills/skills/iros-artifact-evaluation .opencode/skills/iros-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 "iros-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/IROS-Skills/skills/iros-artifact-evaluation into .opencode/skills/iros-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iros-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
iros-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~973 tokens
- SKILL.md length
- 421 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code…
- What an embodied-systems reviewer opens first
- SKILL.md covers The robotics artifact stack, What an IROS reviewer inspects…, Review-time versus… and Worked vignette: packaging a…, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Review-time anonymity versus acceptance-time public release
What it does
Iros Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
Its SKILL.md is about 970 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
- What an embodied-systems reviewer opens first
- Review-time anonymity versus acceptance-time public release
- Making a claim auditable not asserted
Example prompts
- “/iros-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.
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
Iros Artifact Evaluation loads about 973 tokens when it runs. Until then it costs about 90 tokens; SKILL.md has 421 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). 421 words, ~973 tokens.
Download SKILL.mdSave it as
.claude/skills/iros-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- iros-artifact-evaluation
- description
- Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
IROS Artifact Evaluation
IROS has no formal artifact-evaluation track or badge, so "artifact" here means the evidence bundle a reviewer could inspect and that a careful author prepares anyway. The audience is an embodied-systems reviewer who trusts a logged trajectory over a claimed one, and who cannot rerun your robot but can read your logs, configs, and code.
The robotics artifact stack
- Hardware ledger: platform, sensors (make/model/firmware), actuators, onboard computer, and power budget — the embodiment the result depends on.
- Logs: time-stamped rosbag-equivalent recordings for representative trials, so a claim about a contact force or trajectory is auditable.
- Configs: the exact parameters, calibration, and launch files that produced the reported runs.
- Code: the system as run, with an entry point and a one-minute orientation in the README.
- Data: any dataset or object set, with provenance and licensing; for restricted data, enough detail for credible reproduction without violating terms.
What an IROS reviewer inspects first
| Claim type | First artifact inspected | Common failure caught |
|---|---|---|
| "Runs onboard at rate X" | Timing logs and the compute/power spec | Rate measured on a desktop, not the robot |
| "Reliable across trials" | The trial log and failure record | Success rate with resets and failures omitted |
| "Transfers from sim" | Paired sim and real logs | Only sim logs exist; the gap is asserted |
| "Beats prior system" | Baseline configs on the same platform | Baseline run with different hardware or tuning |
Because a reviewer will read a log far sooner than rebuild a robot, make the logs and configs legible first, and polish the code second.
Show full SKILL.md (168 more words)Show less
Review-time versus acceptance-time states
- Review time (double-anonymous): strip organization names, cluster paths, calibration files tagged with a lab, commit authorship, and any URL carrying a lab identity. If you link code, use an anonymized mirror or omit the link and describe the artifact.
- Acceptance time: replace anonymized stand-ins with a public, licensed, citable release; test every link from a logged-out browser; and add the DOI or archival link the IEEE Xplore record can point to.
Worked vignette: packaging a field-robot result
A submission claims a lidar-inertial system runs onboard across three outdoor sites.
- Ship one representative rosbag per site plus the launch/config that processed it, so a reviewer can see the sensor streams and the estimated trajectory line up.
- Record the compute-and-power measurement method, not just a headline rate.
- Emit the trajectory-error tables directly from the logged runs so the paper numbers and the artifact cannot drift apart.
- State which site is easy and which stresses the system, since that mapping is what a reviewer grades.
Artifact layout:
/hardware.md platform, sensors, compute, power
/logs/<site>/ time-stamped bags for representative trials
/config/ calibration, params, launch files
/src/ system as run + README (1-minute orientation)
/data/ provenance + license (or access instructions)Output format
[Artifact role] review-time anonymous / acceptance-time public
[Contents] <hardware/logs/configs/code/data>
[Anonymity risks] <paths/metadata/URLs/calibration tags>
[Auditability] logged / scripted / described / asserted
[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 IROS-Skills/skills/iros-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Iros 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 |
|---|---|---|---|---|---|---|
| Iros Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~973 | Automated safety check: Pass | MIT | |
| Scientific Thinking Scholar Evaluationaffaan-m/ECC | 277k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Review Pending PR Reviewsnrwl/nx | 29k | — | ~3.9k | Automated safety check: Pass | MIT | |
| Reviewthedaviddias/Front-End-Checklist | 74k | — | ~556 | Automated safety check: Pass | MIT | |
| Skeptical Reviewmatthiasn/lotti | 1.2k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| ReviewClickHouse/ClickHouse | 50k | — | ~8k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Review Pending PR Reviews
nrwl/nx
Review, grill, edit, and post pending PR review drafts saved by /review-pr (or its batch/cron runners).
Review
thedaviddias/Front-End-Checklist
A skill your agent uses when applies to product pages, local business pages, recipes, apps, books, and any page that aggregates user reviews.
Skeptical Review
matthiasn/lotti
Act as a skeptical senior engineer performing a detailed code review of the latest changes on the current branch (or a given PR) — best practices, maintainability, performance, security, and…
Review
ClickHouse/ClickHouse
Review a ClickHouse Pull Request for correctness, safety, performance, and compliance.
Docling Pull Request Review
docling-project/docling
Reviews or re-reviews a Docling pull request in fixed stages, with findings that can be reproduced and an explicit record of every check that was run.
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 Iros Artifact Evaluation
What does Iros Artifact Evaluation do?
A skill your agent uses when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code…. Iros Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging IROS evidence for a skeptical reviewer even though IROS runs no formal artifact track — the robotics artifact stack of hardware ledger, logs, configs, code, and data, what an embodied-systems reviewer opens first, review-time anonymity versus acceptance-time public release, and making a claim auditable not asserted.
When should I use Iros Artifact Evaluation?
Iros Artifact Evaluation fits situations like: what an embodied-systems reviewer opens first; review-time anonymity versus acceptance-time public release; making a claim auditable not asserted.
How do I install Iros Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-artifact-evaluation -a claude-code`. Or copy the skill folder (IROS-Skills/skills/iros-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/iros-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Iros Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-artifact-evaluation -a codex`. Or copy the skill folder (IROS-Skills/skills/iros-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/iros-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Iros 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 iros-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/iros-artifact-evaluation, .gemini/skills/iros-artifact-evaluation, .github/skills/iros-artifact-evaluation and .opencode/skills/iros-artifact-evaluation in your project.
What does Iros Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Iros Artifact Evaluation is instructions for the agent only.
Does Iros 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 Iros 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 Iros Artifact Evaluation use?
Iros 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 Iros Artifact Evaluation use?
About 973 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 Iros Artifact Evaluation?
Skills that share tags, products or a category with Iros Artifact Evaluation: Scientific Thinking Scholar Evaluation (affaan-m/ECC, 277k stars), Review Pending PR Reviews (nrwl/nx, 29k stars), Review (thedaviddias/Front-End-Checklist, 74k stars) and Skeptical Review (matthiasn/lotti, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iros 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.