Agent skills

Zuke ships agent skills so AI coding assistants set up and author builds the right way — using the typed *Tasks wrappers instead of guessing the API or shelling out. The skills are authored once as portable SKILL.md folders and distributed from the repo's own skills marketplace, which installs into Claude Code, OpenAI Codex, and the Gemini CLI alike.

The two skills

Skill	Use it to
`zuke-setup`	Scaffold Zuke into a project (`zuke setup`, the `./zuke` launcher, a first build).
`zuke-write-build`	Write or edit a `zuke.ts` — add targets, wire dependencies, call tool wrappers, generate CI.

Both live as SKILL.md folders under skills/ in the Zuke repo; each harness below serves that same source.

Claude Code

The skills are packaged as a Claude Code plugin distributed from the repo's marketplace. In Claude Code, add the marketplace:

/plugin marketplace add zuke-build/zuke

Then install the plugin from it:

/plugin install zuke@zuke

That makes zuke-setup and zuke-write-build available — they trigger automatically when you ask Claude to add Zuke to a project or write a build, and can be invoked explicitly as /zuke:zuke-setup and /zuke:zuke-write-build.

OpenAI Codex

The same plugin installs into Codex from the same repo — it carries a Codex-native .agents/plugins/marketplace.json and .codex-plugin/plugin.json alongside the Claude manifests. Add the marketplace:

codex plugin marketplace add zuke-build/zuke

Then install the plugin from it:

codex plugin add zuke@zuke

A single skill can also be pulled straight from the repo with Codex's built-in installer skill:

$skill-installer install https://github.com/zuke-build/zuke/tree/master/skills/zuke-write-build

Gemini CLI

The repo doubles as a Gemini CLI extension (the root gemini-extension.json; Gemini auto-discovers the skills/ folder next to it):

gemini extensions install https://github.com/zuke-build/zuke

Gemini installs a GitHub extension from the repo's latest release snapshot (offering a git clone as the fallback), so the extension tracks releases rather than master.

One source, every harness

The SKILL.md content is harness-agnostic — it follows the open Agent Skills standard. Each manifest above (the Claude marketplace and plugin manifests, the Codex marketplace and plugin manifests, the Gemini extension manifest) is a thin adapter over the shared skills/ source, so every harness serves the same two skills, and an improvement to a skill lands everywhere at once.

Skills teach an agent to author a build; the MCP server is the complement — it lets an agent operate one through typed tool calls. They work well together: install the skills, register zuke mcp, and an assistant can write a target and then run it.