# Zero

> Install Zero and load version-matched workflows with zero skills.

- Skill: `keejkrej/zero` (Agent Skill)
- Install (CLI): `npx skillmds@latest add keejkrej/zero`
- Raw SKILL.md: https://api.skillmd.com/api/skills/keejkrej/zero/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: keejkrej (https://skillmd.com/u/keejkrej)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/keejkrej/zero

---


# Zero

Zero is an agent-first programming language where the graph is the program
database and `.0` files are human-readable projections.

Install this skill once in an agent's skill manager. Keep it thin; Zero's own CLI serves the version-matched workflow for each installed compiler.

Install the latest release:

```sh
curl -fsSL https://zerolang.ai/install.sh | bash
export PATH="$HOME/.zero/bin:$PATH"
zero --version
```

## Version-Matched Skills

This file is only a discovery stub. Do not treat it as the full Zero workflow
or as command reference.

Before editing, checking, testing, or repairing Zero code, ask the installed compiler for the skill content that matches that exact binary:

```sh
zero skills
zero skills get zero
zero skills get zero --full
```

If the user has multiple Zero binaries, use the same binary that will run the project:

```sh
/path/to/zero skills
/path/to/zero skills get zero --full
```

Use `zero skills` to discover additional skills bundled with that Zero version.
Use `zero skills get <name>` to load only what is relevant to the task. Common
inner skills include `agent`, `language`, `graph`, `diagnostics`, `packages`,
`builds`, `testing`, and `stdlib`.

Agents should normally author through the graph and use `.0` projections only
for human review or explicit import/export work. Prefer concise text output
during interactive agent work; use `--json` only for automation, exact spans,
contracts, or machine-readable diagnostics.

## Common Entry Points

```sh
zero query [graph-or-package]
zero patch [graph-or-package] --op '<operation>'
zero check [graph-or-package]
zero test [graph-or-package]
zero run [graph-or-package] -- <args>
zero diff [graph-or-package]
zero explain <diagnostic-code>
zero fix --plan [graph-or-package]
```

In a Zero repository checkout, prefer `bin/zero` when the task is about that checkout rather than the globally installed compiler.