Agent skill

Cscw Artifact Evaluation

by brycewang-stanford in brycewang-stanford/Awesome-Journal-Skills

A skill your agent uses when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and…

MITAuto-check passed

Install Cscw Artifact Evaluation

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .claude/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .claude/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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

$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation

Type 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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .agents/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .agents/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .cursor/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .cursor/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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

$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path CSCW-Skills/skills/cscw-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .gemini/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .gemini/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation

Installs 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).

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .github/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .github/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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.

skills CLI

$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install brycewang-stanford/Awesome-Journal-Skills cscw-artifact-evaluation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/CSCW-Skills/skills/cscw-artifact-evaluation .opencode/skills/cscw-artifact-evaluation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cscw-artifact-evaluation" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/CSCW-Skills/skills/cscw-artifact-evaluation into .opencode/skills/cscw-artifact-evaluation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cscw-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: cscw-artifact-evaluation
GitHub stars: 1.2k
Token cost: ~1.2k tokens
SKILL.md length: 468 words
Files: 1
Skills in repo: 2,387
Repo updated: Sep 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and…

Works in 4 steps: Quote search: can any released text… → Join attack: can released fields… → Small-population exposure: would… → …
Packaging what stands behind a CSCW paper — systems
SKILL.md covers Artifact classes and their…, The community…, Minimum viable released package and Review-time discipline, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cscw Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.

Its SKILL.md is about 1.2k 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 what stands behind a CSCW paper — systems
Analysis pipelines
Datasets from real communities — for review-time scrutiny and post-acceptance release
Where community-data ethics constrain release more than any badge checklist

Example prompts

“/cscw-artifact-evaluation”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Quote search: can any released text snippet be pasted into a search engine
Join attack: can released fields (timestamps + community + activity counts)
Small-population exposure: would identifying the community (not any
Future-context check: platforms change hands and moderation regimes change;

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

Cscw Artifact Evaluation loads about 1.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 468 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~74
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

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). 468 words, ~1,195 tokens.

Download SKILL.mdSave it as .claude/skills/cscw-artifact-evaluation/SKILL.md (or your agent's skills folder).

name: cscw-artifact-evaluation
description: Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.

CSCW Artifact Packaging

CSCW has no artifact-evaluation committee stamping badges; the "evaluators" of your artifacts are the reviewers deciding whether to trust your methods, and later the researchers and the studied communities themselves who encounter the released materials. That second audience is the venue's distinctive constraint: a CSCW artifact release is an act with consequences for real people who never signed your consent form.

Artifact classes and their release logic

Artifact	Review-time form	Post-acceptance form	Governing constraint
Study instruments (guides, surveys)	Anonymized in supplement	Public archive	Institution redaction only
Codebooks	Anonymized in supplement	Public archive	Paraphrased exemplars only
Analysis code	Anonymized archive	Public repository + DOI archive	Strip identity from history
Built systems / prototypes	Screenshots/video + code where feasible	Open source if maintainable	Third-party assets, API keys
Trace datasets	Aggregates or synthetic sample	Aggregates; raw only if terms + ethics allow	Platform ToS + re-identification risk
Interview/field data	Never	Almost never	Consent scope is absolute

The community re-identification test

Before releasing any dataset or exemplar text derived from an online community, run the adversary exercise — assume a motivated actor (a journalist, a harasser, a platform admin, a community member with a grudge):

Quote search: can any released text snippet be pasted into a search engine and land on the original post? If yes, paraphrase or drop it.
Join attack: can released fields (timestamps + community + activity counts) be joined against public APIs or archives to recover usernames? Coarsen until the join fails.
Small-population exposure: would identifying the community (not any member) expose it to raids, deplatforming, or press attention it has not chosen? If the community is small or marginalized, community-level anonymity is part of the ethical contract — name it only with its agreement.
Future-context check: platforms change hands and moderation regimes change; would this release be safe under a hostile future owner of the platform's data?

Document the outcome in a short release memo; it becomes the honest core of the paper's data-availability statement (cscw-reproducibility).

Show full SKILL.md (143 more words)Show less

Minimum viable released package

text

release/
├── README.md            # what claims each artifact supports; setup in ≤ 5 steps
├── LICENSE              # code license + data terms, which may differ
├── instruments/         # guides, surveys, recruitment text (redacted)
├── codebook/            # definitions + paraphrased exemplars
├── pipeline/            # collection + analysis code, config, environment spec
├── data/
│   ├── aggregates/      # tables behind each figure
│   └── synthetic/       # optional: structure-preserving fake sample
└── ETHICS.md            # consent scope, what is withheld and WHY, contact path

ETHICS.md is the CSCW-specific file: it tells reusers what they may not do (re-identify, recontact, join against other datasets) and why the withheld parts are withheld. A release that explains its own limits earns more trust than a maximal dump.

Review-time discipline

Everything reviewers can open must be anonymous — including git metadata, archive paths, and hosting URLs (use anonymized repository services, not a lab server whose domain resolves the institution).
Never put decision-critical evidence only in the artifact; the paper must stand if a reviewer opens nothing.
Keep the review package and the eventual public release as separate builds from one source tree; the deanonymization diff at acceptance should be mechanical (cscw-camera-ready).

Release audit

text

[Claims map]     each artifact → the claim it supports (no orphan uploads)
[Adversary test] quote-search / join / community-exposure / future-context: pass?
[Consent gate]   every released item inside consent + ToS scope? y/n
[Two builds]     review build anonymous; release build attributed; same tree? y/n
[ETHICS.md]      withholdings explained, reuse limits stated? y/n

No CSCW badge program existed at the 2026-07-08 check; if one appears in a future cycle, its checklist supplements — never replaces — the community-protection tests above.

Files

Just SKILL.md in CSCW-Skills/skills/cscw-artifact-evaluation of brycewang-stanford/Awesome-Journal-Skills.

Open the folder on GitHubat commit 932eb23

Compare with similar skills

Cscw 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.

Cscw Artifact Evaluation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Cscw Artifact Evaluation this skillbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.2k	Automated safety check: Pass	MIT	13 days ago
Arize Evaluatorgithub/awesome-copilot	40k	1 repos	~8.1k	Automated safety check: Notes	MIT	2 days ago
Artifacts Buildernexu-io/open-design	100k	—	~347	Automated safety check: Pass	Apache-2.0	yesterday
Ccs Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~969	Automated safety check: Pass	MIT	13 days ago
Mobisys Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1k	Automated safety check: Pass	MIT	13 days ago
Fast Artifact Evaluationbrycewang-stanford/Awesome-Journal-Skills	1.2k	—	~1.6k	Automated safety check: Pass	MIT	13 days ago

Similar skills

Arize Evaluator
github/awesome-copilot
Official
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…
40k GitHub starsUsed in 1 repo~8.1k tokens
AI & LLM EngineeringAuto-check: notes
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).
100k GitHub stars~347 tokensUpdated yesterday
Frontend & DesignAuto-check passed
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…
1.2k GitHub stars~969 tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.2k tokensUpdated 13 days ago
DevOps & CloudAuto-check passed

More from brycewang-stanford/Awesome-Journal-Skills

All 2,387 skills in this repo

Aaag 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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.4k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.3k tokensUpdated 13 days ago
Auto-check passed
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…
1.2k GitHub stars~1.6k tokensUpdated 13 days ago
Auto-check passed

Questions about Cscw Artifact Evaluation

What does Cscw Artifact Evaluation do?

A skill your agent uses when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and…. Cscw Artifact Evaluation is an agent skill from brycewang-stanford/Awesome-Journal-Skills. Use when packaging what stands behind a CSCW paper — systems, analysis pipelines, codebooks, instruments, datasets from real communities — for review-time scrutiny and post-acceptance release, where community-data ethics constrain release more than any badge checklist.

When should I use Cscw Artifact Evaluation?

Cscw Artifact Evaluation fits situations like: packaging what stands behind a CSCW paper — systems; analysis pipelines; datasets from real communities — for review-time scrutiny and post-acceptance release; where community-data ethics constrain release more than any badge checklist.

How do I install Cscw Artifact Evaluation in Claude Code?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a claude-code`. Or copy the skill folder (CSCW-Skills/skills/cscw-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/cscw-artifact-evaluation in your project. Claude Code loads it when a task matches its description.

How do I install Cscw Artifact Evaluation in Codex?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cscw-artifact-evaluation -a codex`. Or copy the skill folder (CSCW-Skills/skills/cscw-artifact-evaluation in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/cscw-artifact-evaluation in your project. Codex loads it when a task matches its description.

Can I use Cscw 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 cscw-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/cscw-artifact-evaluation, .gemini/skills/cscw-artifact-evaluation, .github/skills/cscw-artifact-evaluation and .opencode/skills/cscw-artifact-evaluation in your project.

What does Cscw Artifact Evaluation need to run?

SKILL.md names no scripts, command-line tools or credentials: Cscw Artifact Evaluation is instructions for the agent only.

Does Cscw 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 Cscw 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 Cscw Artifact Evaluation use?

Cscw 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 Cscw Artifact Evaluation use?

About 1.2k tokens (SKILL.md is roughly 4.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 Cscw Artifact Evaluation?

Skills that share tags, products or a category with Cscw 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 Cscw 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.

Install Cscw Artifact Evaluation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CSCW Artifact Packaging

Artifact classes and their release logic

The community re-identification test

Minimum viable released package

Review-time discipline

Release audit

Files

Compare with similar skills

Similar skills

More from brycewang-stanford/Awesome-Journal-Skills

Questions about Cscw Artifact Evaluation