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
Socc Artifact Evaluation
by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what…
MITAuto-check passed
Install Socc Artifact Evaluation
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-artifact-evaluation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-artifact-evaluation .claude/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .claude/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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/SoCC-Skills/skills/socc-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 socc-artifact-evaluation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-artifact-evaluation .agents/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .agents/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-artifact-evaluation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-artifact-evaluation .cursor/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .cursor/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 SoCC-Skills/skills/socc-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 socc-artifact-evaluation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills socc-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/SoCC-Skills/skills/socc-artifact-evaluation .gemini/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .gemini/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-artifact-evaluation .github/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .github/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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 socc-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 socc-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/SoCC-Skills/skills/socc-artifact-evaluation .opencode/skills/socc-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 "socc-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/SoCC-Skills/skills/socc-artifact-evaluation into .opencode/skills/socc-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "socc-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
socc-artifact-evaluation- GitHub stars
- 1.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 588 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what…
- Packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available
- SKILL.md covers The ACM badges (verify the…, What a cloud-systems evaluator…, Packaging plan and Anonymized review artifact vs.…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Evaluated Functional and Reusable
What it does
Socc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what a cloud-systems evaluator checks first, reproducing tail-latency and cost results on a testbed, DOI-issuing archives, and the fact that whether SoCC runs a dedicated artifact-evaluation track for a given edition must be verified.
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 an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available
- Evaluated Functional and Reusable
- Results Reproduced)
- Covering what a cloud-systems evaluator checks first
Example prompts
- “/socc-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
Socc Artifact Evaluation loads about 1.5k tokens when it runs. Until then it costs about 108 tokens; SKILL.md has 588 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). 588 words, ~1,513 tokens.
Download SKILL.mdSave it as
.claude/skills/socc-artifact-evaluation/SKILL.md (or your agent's skills folder).- name
- socc-artifact-evaluation
- description
- Use when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what a cloud-systems evaluator checks first, reproducing tail-latency and cost results on a testbed, DOI-issuing archives, and the fact that whether SoCC runs a dedicated artifact-evaluation track for a given edition must be verified.
SoCC Artifact Evaluation
Use this for artifact preparation. SoCC — as an ACM venue — follows the ACM Artifact Review and Badging scheme where an edition offers evaluation. First, verify whether the current SoCC edition runs a dedicated artifact-evaluation track, and which badges it offers — unlike some sibling systems flagships that run a standing AE process, SoCC's artifact track and badge set are decided per edition and are 待核实 as of 2026-07-09. The advice below applies once the edition's call confirms evaluation.
Two things to internalize: badges are earned by evaluators actually reproducing your cloud results, and the review artifact (anonymized, for the paper's reviewers) is not the same deliverable as the badge artifact (de-anonymized, permanently archived).
The ACM badges (verify the current set and names)
| Badge | What it certifies | What earns it for a cloud paper |
|---|---|---|
| Artifacts Available | The artifact is permanently, publicly retrievable | Deposit in a DOI-issuing archive (Zenodo, figshare, Software Heritage) |
| Artifacts Evaluated - Functional | The artifact runs and does what the paper says | A documented testbed setup, a workload replay, and expected outputs |
| Artifacts Evaluated - Reusable | Others can build on it | Functional plus careful docs, structure, licensing, and a portable harness |
| Results Reproduced | An evaluator reproduced the paper's key results | A turnkey path from the artifact to the headline throughput/tail/cost numbers |
Available is a low-cost, high-value badge (archive the package); Functional/Reusable/Reproduced require the evaluator's own run to succeed, so the failure mode is always "did not run on their testbed," never "the idea was weak."
What a cloud-systems evaluator opens first
| Claim type | First thing inspected | Common failure caught |
|---|---|---|
| A cloud system/mechanism | The README and one setup+run command | Undocumented cluster assumptions; only-runs-on-authors'-testbed |
| A measurement/trace study | The scripts that turn the trace into the paper's figures | Numbers in the PDF no script reproduces; trace missing |
| A scheduling/serverless result | The workload generator + the tail/cost measurement scripts | Only the mean reproduces; tail and cost cannot be regenerated |
| A large-scale deployment | A scaled-down but faithful reproduction path | Requires a proprietary cluster; no smaller-scale replay |
Assume an evaluator has a bounded time budget and cannot reserve your 200-node cluster. Provide a scaled-down reproduction that still regenerates the shape of the tail and cost results, plus a clear statement of what needs full scale.
Show full SKILL.md (219 more words)Show less
Packaging plan
[Environment] ship a Dockerfile / pinned environment AND a testbed description (node counts,
instance types, OS, kernel) so a run is reproducible
[Workloads] the workload generator or the (anonymized, then released) trace, not just a pointer
[README] one-screen orientation: what it is, how to set up, how to run a small demo, how to
reproduce each figure, expected runtime and outputs
[Mapping] an explicit table: paper claim -> script -> expected result (incl. tail and cost)
[Scaled path] a small-scale reproduction that runs without the full cluster
[Provenance] commit SHAs, trace extraction dates, instance types, seeds, run counts
[License] an OSI-approved license so the artifact can be badged Reusable
[Archive] deposit in a DOI-issuing repository for the Available badgeAnonymized review artifact vs. badge artifact
- At submission: the artifact is anonymized for the paper's reviewers — no cluster names, provider hints, owner strings, or identity-revealing trace provenance, and no live repository that discloses authors.
- After acceptance: replace anonymized placeholders with the public, licensed, DOI-issuing archive; this is the version any artifact evaluators badge and the camera-ready cites.
Worked vignette: packaging an autoscaler + trace study
A paper contributes a tail-aware autoscaler and a measurement of the cost-tail gap. To target
Reusable and Reproduced: ship a Docker image with the controller pre-built; a run_demo.sh that
replays a short trace slice on a few nodes in minutes and prints p99 and instance-seconds; a
reproduce/ directory whose scripts regenerate each figure from logged runs; a claim-to-script
mapping table in the README; the (released) trace-replay harness with pinned SHAs; and an
MIT/Apache license. State honestly which figures are turnkey at small scale and which need the full
testbed.
Calibration
- Confirm the track exists for this edition before planning; SoCC's AE track and badge set are 待核实 per cycle.
- Reproducing tail and cost, not just the mean, is the cloud-specific bar; design the package so an evaluator can regenerate them.
- Badge names, the exact set offered, and whether evaluation is single- or double-anonymous vary by edition — confirm on the current call.
Output format
[Track status] SoCC AE track confirmed for this edition? yes/no/待核实
[Target badges] Available / Functional / Reusable / Reproduced
[Artifact role] anonymized review artifact / public badge artifact
[Contents] <system/workloads/trace/scripts/testbed-desc/provenance/license>
[Small-scale test] does setup + demo reproduce tail+cost shape without the full cluster? yes/no
[Claim mapping] <claim -> script -> expected result (incl. tail/cost) present? yes/no>
[Fixes before upload] <ordered list>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in SoCC-Skills/skills/socc-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Socc 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 |
|---|---|---|---|---|---|---|
| Socc 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 | |
| Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~969 | Automated safety check: Pass | MIT | |
| Sigcomm Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Sigmetrics Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
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…
Sigcomm Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ACM SIGCOMM paper's code, traces, topologies, and configuration for the artifact-evaluation committee — choosing ACM badges (Artifacts Available, Evaluated…
Sigmetrics Artifact Evaluation
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when packaging an ACM SIGMETRICS artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced)…
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…
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 Socc Artifact Evaluation
What does Socc Artifact Evaluation do?
A skill your agent uses when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what…. Socc Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available, Evaluated Functional and Reusable, Results Reproduced), covering what a cloud-systems evaluator checks first, reproducing tail-latency and cost results on a testbed, DOI-issuing archives, and the fact that whether SoCC runs a dedicated artifact-evaluation track for a given edition must be verified.
When should I use Socc Artifact Evaluation?
Socc Artifact Evaluation fits situations like: packaging an ACM SoCC artifact for the ACM Artifact Review and Badging scheme (Artifacts Available; evaluated Functional and Reusable; results Reproduced); covering what a cloud-systems evaluator checks first.
How do I install Socc Artifact Evaluation in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-artifact-evaluation -a claude-code`. Or copy the skill folder (SoCC-Skills/skills/socc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/socc-artifact-evaluation in your project. Claude Code loads it when a task matches its description.
How do I install Socc Artifact Evaluation in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill socc-artifact-evaluation -a codex`. Or copy the skill folder (SoCC-Skills/skills/socc-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/socc-artifact-evaluation in your project. Codex loads it when a task matches its description.
Can I use Socc 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 socc-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/socc-artifact-evaluation, .gemini/skills/socc-artifact-evaluation, .github/skills/socc-artifact-evaluation and .opencode/skills/socc-artifact-evaluation in your project.
What does Socc Artifact Evaluation need to run?
SKILL.md names no scripts, command-line tools or credentials: Socc Artifact Evaluation is instructions for the agent only. Our summary lists: Docker.
Does Socc 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 Socc 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 Socc Artifact Evaluation use?
Socc 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 Socc Artifact Evaluation use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Socc Artifact Evaluation?
Skills that share tags, products or a category with Socc Artifact Evaluation: Arize Evaluator (github/awesome-copilot, 40k stars), Ccs Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars), Sigcomm Artifact Evaluation (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars) and Sigmetrics 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 Socc 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.