Zinc-J Scripting for Warcraft 3 Agent Skill

Optimizes Warcraft 3 map development by providing specialized syntax guidance and best practices for Zinc scripting within JASS files.

Context cost
3k tokensestimated from the bundle, loaded when it triggers
Bundle
6 files · 12.0 kBtext throughout, nothing executable
Licence
Apache-2.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

本项目 .j 文件中的 Zinc(//! zinc ... //! endzinc)语法与约定:库/结构体写法、匿名函数(无闭包)最佳实践、回调参数传递、资源释放/置空、Hash 表键位与避免不必要新建 hashtable、以及 JASS 到 Zinc 迁移要点。

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.

gamedev

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.0 kB · preview
--- name: zinc-j ---
6# Zinc(本项目)语法与约定
7
8## 必须遵守
9
10- 用 //! zinc / //! endzinc 包裹 Zinc 代码块。
11- 禁用 ++/--;用 += 1 / -= 1。
12- 禁用 break/continue;用 if 分支或布尔开关改写。
13- 数组声明一律用 type name[];,不要写大小(例如 integer a[10] 是错的)。
14- Zinc 的数组维度里不要写表达式(例如 arr[HERO_COUNT + 1][5]);需要先把值算成常量再使用,或直接用固定上界。
15- 二维数组在底层是线性存储;只要索引映射不冲突(例如 a[6][5] 下 (1,5) 与 (2,1) 映射不同),可以按项目约定安全使用,不必为了“从 1 开始”额外预留整段 [1]。
16- 返回类型用 -> type 写在参数列表后;无返回可省略。
17- 局部变量统一在函数/匿名函数开头声明:先基础类型,后句柄类型。
18- 函数定义顺序不再作为日常写法的硬性约束:vjassc 会处理上方函数直接调用下方函数的场景。
19- 仍需兼容 jasshelper 时,如果它只因函数顺序报错而 vjassc 能过,优先在该调用点改成 xxxx.evaluate(...),少做大范围函数重排。
20- 本地场景(例如 UI 本地执行)禁止 execute,只能用 evaluate,否则有 OOS 风险。
21- 仅在本文件内引用的固定长文案/标签,不要另起一个只 return "..." 的函数;优先按 CenterUp.j 的 GetResumeLabel() 风格用函数式 #define,并在文件末尾配套 #undef。
22
23## 匿名函数(无闭包)
24
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md410 words
Files6
LicenceApache-2.0
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.

≈40
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,960
on trigger
The instruction body and 5 supporting files, read only when the skill fires.
1.5%
of a 200k window
Ten skills this size would take about 15% of the window before you open a file.
050k100k150k200k context window

3k 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

6 files, 12.0 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md7.0 kB
  • references/anonymous-functions.md0.9 kB
  • references/callback-params.md0.5 kB
  • references/function-order-and-indirect-call.md2.4 kB
  • references/jass-to-zinc.md0.5 kB
  • references/method-syntax.md0.7 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 6 files you can review in full before installing. The Apache-2.0 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.

# Zinc-J Scripting for Warcraft 3 · 3k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/zinc-j-scripting-for-warcraft-3/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/zinc-j-scripting-for-warcraft-3" ] && { [ ! -e .claude/skills/zinc-j-scripting-for-warcraft-3 ] || { mv .claude/skills/zinc-j-scripting-for-warcraft-3 "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/zinc-j-scripting-for-warcraft-3" .claude/skills/ && echo "Installed .claude/skills/zinc-j-scripting-for-warcraft-3"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add crainax/zinc-j-scripting-for-warcraft-3

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/zinc-j-scripting-for-warcraft-3/ 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/zinc-j-scripting-for-warcraft-3/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/zinc-j-scripting-for-warcraft-3" ] && { [ ! -e ~/.claude/skills/zinc-j-scripting-for-warcraft-3 ] || { mv ~/.claude/skills/zinc-j-scripting-for-warcraft-3 "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/zinc-j-scripting-for-warcraft-3" ~/.claude/skills/ && echo "Installed ~/.claude/skills/zinc-j-scripting-for-warcraft-3" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/zinc-j-scripting-for-warcraft-3/ 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 zinc-j in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, zinc-j-scripting-for-warcraft-3.

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
Referencecrainax/zinc-j-scripting-for-warcraft-3

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