Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Agent skill
Infocom Artifact Evaluation
by brycewang-stanford in 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…
Install Infocom Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .claude/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .claude/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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/INFOCOM-Skills/skills/infocom-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 infocom-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .agents/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .agents/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .cursor/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .cursor/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 INFOCOM-Skills/skills/infocom-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 infocom-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .gemini/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .gemini/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-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 infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .github/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .github/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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 infocom-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 infocom-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/INFOCOM-Skills/skills/infocom-artifact-evaluation .opencode/skills/infocom-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 "infocom-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/INFOCOM-Skills/skills/infocom-artifact-evaluation into .opencode/skills/infocom-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "infocom-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
infocom-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 530 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
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…
- Packaging IEEE INFOCOM code
- SKILL.md covers What the absence of a formal…, IEEE reproducibility options…, What a credible networking… and Packaging plan (optional but…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Datasets for credibility and optional IEEE reproducibility badges
What it does
Infocom Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Reproducible research. 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 IEEE INFOCOM code
- Datasets for credibility and optional IEEE reproducibility badges
- Given that INFOCOM runs no standing artifact-evaluation track
- Covering DOI-issuing archives
Example prompts
- “/infocom-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
Infocom Artifact Evaluation loads about 1.3k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 530 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). 530 words, ~1,336 tokens.
Download SKILL.mdSave it as
.claude/skills/infocom-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- infocom-artifact-evaluation
- description
- Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.
INFOCOM Artifact Evaluation
Use this when you want to release an artifact. The first thing to internalize: INFOCOM has no standing artifact-evaluation track and no mandatory badge process (as of 2026-07-09; 待核实 whether a cycle introduces one). Unlike SIGCOMM/NSDI/USENIX ATC — where a separate committee runs your artifact and awards badges — an INFOCOM artifact is entirely optional and self-directed. That changes the goal: you package not to pass an evaluator, but to make a large, skeptical, no-rebuttal reviewer pool believe your numbers.
What the absence of a formal track changes
| At an artifact-track venue (SIGCOMM/NSDI/ATC) | At INFOCOM |
|---|---|
| A committee runs your artifact on a deadline | No one is required to run it |
| Badges (Available/Functional/Reproduced) are awarded | No INFOCOM badge exists (待核实 per cycle) |
| Packaging is a graded deliverable | Packaging is a credibility investment you choose |
| The artifact can lift a borderline decision | A released package pre-empts "I don't believe this" in the PDF |
Because no evaluator is guaranteed, the payoff of a release is reviewer trust and post-publication impact, not a badge. Optimize for a reader who might look, and for the researchers who will build on your simulator after publication.
IEEE reproducibility options you can opt into
- IEEE DataPort — deposit datasets/traces with a DOI and a license.
- DOI-issuing archives — Zenodo, figshare, or Software Heritage for a simulator or code release with a permanent identifier and an OSI-approved license.
- Some IEEE venues offer code/data availability badges; INFOCOM does not mandate them — confirm the current cycle's specifics before claiming one (待核实).
What a credible networking release contains
| Contribution type | First thing a reader checks | Common failure to avoid |
|---|---|---|
| An algorithm/protocol | A README and one run command on a small example | Only-runs-on-authors'-cluster; undocumented deps |
| A simulation study | The scripts that regenerate the paper's figures from logged runs | Numbers in the PDF no script reproduces |
| A dataset/trace | The data plus its provenance and preprocessing | Query shipped, data missing; source unstated |
| A learning-for-networking result | Cached inputs/outputs, model IDs, seeds | Requires live API keys; not reproducible |
Show full SKILL.md (200 more words)Show less
Packaging plan (optional but persuasive)
[Container] a Dockerfile or a pinned environment (requirements/lockfile) for the simulator/tool
[README] one screen: what it is, how to install, how to run a small demo, how to regenerate
each figure, expected runtime and outputs
[Mapping] an explicit table: paper claim/figure -> script -> expected result
[Config] the exact topology, traffic model, seeds, and parameters used in the paper
[Data] the trace/dataset (or documented access), not just the generator
[License] an OSI-approved license so others can build on it
[Archive] deposit in a DOI-issuing repository (Zenodo/DataPort/Software Heritage)Double-blind timing
- At submission: if you link an artifact for reviewers, anonymize it — no owner strings, cluster paths, lab names, or identifying repo — and host it behind an anonymizing service. Nothing decision-critical may live only there (reviewers need not open it).
- After acceptance: replace anonymized placeholders with the public, licensed, DOI-issuing archive, and make the camera-ready's statements match it.
Vignette: releasing a scheduling simulator + trace
A paper contributes an edge-scheduling algorithm evaluated by trace-driven simulation. A credible
optional release: a Docker image with the custom simulator pre-built; a run_demo.sh that runs one
small scenario in under a minute; a figures/ directory whose scripts regenerate each plot from
logged runs; a claim-to-script table in the README; the request trace (or documented access) with
its provenance; and an MIT/Apache license with a Zenodo DOI. State honestly which figures are
turnkey and which need the full (slow) trace.
Calibration
- There is no artifact deadline because there is no artifact track — do not invent one; the
only related deadline is the IEEE Xplore camera-ready (
infocom-camera-ready). - If a future cycle adds an artifact/badge process, confirm its rules, timing, and anonymity model on the current call before advising (待核实).
Output format
[Release decision] release / no release, with reason
[Target] credibility only / IEEE DataPort / DOI archive / (badge if a cycle offers one, 待核实)
[Contents] <simulator/tool + config + data + license>
[Ten-minute test] does install + demo succeed on a clean machine? yes/no
[Figure mapping] <figure -> script -> expected result present? yes/no>
[Anonymity] anonymized for review; de-anonymized DOI archive for camera-ready? yes/no© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in INFOCOM-Skills/skills/infocom-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Infocom 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 |
|---|---|---|---|---|---|---|
| Infocom Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT | |
| CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw | 617 | 1 repos | ~1.8k | Automated safety check: Pass | None | |
| Compute Environment Setupaipoch/open-science | 5.5k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Figure Styleaipoch/open-science | 5.5k | — | ~5.1k | Automated safety check: Pass | Apache-2.0 | |
| Add Bactopia Toolbactopia/bactopia | 522 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
Compute Environment Setup
aipoch/open-science
Prepares setup instructions and a named activation file for a user-managed software environment on an Open-Science SSH or Slurm compute host.
Figure Style
aipoch/open-science
Publication-grade correctness and legibility rules for final-deliverable scientific figures, not exploratory plots.
Add Bactopia Tool
bactopia/bactopia
Scaffold a complete Bactopia Tool across all three tiers -- module, subworkflow, and workflow entry point under workflows/bactopia-tools/.
Modeling Code and Result Contracts
yushui2022/MathModel-Skill
Generates result-evidence contracts, tables and runnable q1 to q3 modeling code scaffolds for a math modeling paper from a model route, a data plan and cleaned data.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Infocom Artifact Evaluation
What does Infocom Artifact Evaluation do?
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…. Infocom Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging IEEE INFOCOM code, simulators, and datasets for credibility and optional IEEE reproducibility badges, given that INFOCOM runs no standing artifact-evaluation track, covering DOI-issuing archives, evaluator-proof documentation, what the absence of a formal track changes, and how a released package strengthens a no-rebuttal submission.
When should I use Infocom Artifact Evaluation?
Infocom Artifact Evaluation fits situations like: packaging IEEE INFOCOM code; datasets for credibility and optional IEEE reproducibility badges; given that INFOCOM runs no standing artifact-evaluation track; covering DOI-issuing archives.
How do I install Infocom Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-artifact-evaluation -a claude-code`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/infocom-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Infocom Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill infocom-artifact-evaluation -a codex`. Or copy the skill folder (INFOCOM-Skills/skills/infocom-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/infocom-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Infocom 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 infocom-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/infocom-artifact-evaluation, .gemini/skills/infocom-artifact-evaluation, .github/skills/infocom-artifact-evaluation and .opencode/skills/infocom-artifact-evaluation in your project.
What does Infocom Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Infocom Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Infocom 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 Infocom 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 Infocom Artifact Evaluation use?
Infocom 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 Infocom Artifact Evaluation use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Infocom Artifact Evaluation?
Skills that share tags, products or a category with Infocom Artifact Evaluation: Peer Review (K-Dense-AI/claude-scientific-writer, 2.4k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars), Compute Environment Setup (aipoch/open-science, 5.5k stars) and Figure Style (aipoch/open-science, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Infocom 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.