JCAD&CG Artifact Evaluation & Data Availability Agent Skill

Prepares reproducible graphics artifacts, double-blind anonymization, and honest data availability statements for Journal of CAD &…

Context cost
1.8k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 7.2 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

在为《计算机辅助设计与图形学学报》(Journal of Computer-Aided Design & Computer Graphics, JCAD&CG) 准备代码与数据可用性、撰写诚实的可用性声明时调用。说明本刊是否设正式制品评审(artifact evaluation)属待核实的现状,给出无论政策如何都应做到的图形学制品自律标准:代码/数据/网格/预训练模型/渲染脚本的公开与托管、双盲外审下的匿名化、演示视频与结果可复现、受限数据的替代核验途径,以及可用性声明的写法。适用于把图形/几何论文的制品打包到经得起审阅、避免声明与实际不符的场景。

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

documentation

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md7.2 kB · preview
--- name: jcadcg-artifact-evaluation ---
6# 《计算机辅助设计与图形学学报》代码与数据可用性
7
8本技能帮助为《计算机辅助设计与图形学学报》(Journal of Computer-Aided Design & Computer
9Graphics, JCAD&CG) 准备制品(代码、数据、网格、模型)与**诚实的可用性声明**。本刊是 CCF A 类
10图形学/CAD 方向中文月刊。核验见 resources/official-source-map.md(2026-07-09)。
11
12## 一、政策现状(务必按当期核实)
13
14- 本刊是否设**正式的制品评审/artifact evaluation 徽章**、是否有**强制代码/数据可用性**
15 要求,均属 **待核实**(以官网当期《投稿须知》为准)。
16- 与英文会议(如带 AE 徽章的 ACM 会议)不同,中文期刊多以**同行评议**为主,制品公开常为
17 鼓励/加分项而非硬性门槛。**不要臆造本刊有徽章制度。**
18- 无论政策如何,公开可复现制品都会增强外审信任、提升论文影响力。本技能给出自律标准。
19
20## 二、图形学制品应包含什么
21
22| 类型 | 内容 |
23|---|---|
24| 代码 | 方法实现、训练/推理脚本、渲染与几何处理脚本 |
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md317 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
1,720
on trigger
The instruction body, read only when the skill fires.
0.90%
of a 200k window
Ten skills this size would take about 9% of the window before you open a file.
050k100k150k200k context window

1.8k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 7.2 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md7.2 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# JCAD&CG Artifact Evaluation & Data Availability · 1.8k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/jcad-cg-artifact-evaluation-data-availability/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/jcad-cg-artifact-evaluation-data-availability" ] && { [ ! -e .claude/skills/jcad-cg-artifact-evaluation-data-availability ] || { mv .claude/skills/jcad-cg-artifact-evaluation-data-availability "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/jcad-cg-artifact-evaluation-data-availability" .claude/skills/ && echo "Installed .claude/skills/jcad-cg-artifact-evaluation-data-availability"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add brycewang-stanford/jcad-cg-artifact-evaluation-data-availability

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/jcad-cg-artifact-evaluation-data-availability/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/jcad-cg-artifact-evaluation-data-availability/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/jcad-cg-artifact-evaluation-data-availability" ] && { [ ! -e ~/.claude/skills/jcad-cg-artifact-evaluation-data-availability ] || { mv ~/.claude/skills/jcad-cg-artifact-evaluation-data-availability "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/jcad-cg-artifact-evaluation-data-availability" ~/.claude/skills/ && echo "Installed ~/.claude/skills/jcad-cg-artifact-evaluation-data-availability" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/jcad-cg-artifact-evaluation-data-availability/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as jcadcg-artifact-evaluation in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, jcad-cg-artifact-evaluation-data-availability.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencebrycewang-stanford/jcad-cg-artifact-evaluation-data-availability

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill