
Zero
Install the Zero compiler once and pull version-matched agent workflows from the binary instead of baking stale instructions into the repo.
Install
npx skills add https://github.com/vercel-labs/zero --skill zeroWhat is this skill?
- One-line install via zerolang.ai script and PATH setup for `~/.zero/bin`
- Thin discovery stub—full workflow comes from `zero skills list` and `zero skills get` matched to the installed compiler
- Bundled inner skills include zero-agent, zero-language, zero-diagnostics, zero-packages, zero-builds, zero-testing, and
- Common JSON CLI entry points: check, graph, size, explain, fix --plan
- Multi-binary setups: call skills on the same `/path/to/zero` binary that will run the project
Adoption & trust: 183 installs on skills.sh; 4.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Journey fit
Zero targets agent-oriented code and diagnostics; the canonical shelf is Build because you invoke it while implementing and maintaining Zero packages. Agent-tooling fits a dedicated language plus CLI (`zero skills get`, `zero check`) that extends what coding agents can do on Zero projects.
Common Questions / FAQ
Is Zero safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Zero
# Zero Zero is the programming language for agents. 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 a discovery stub. Do not treat it as the full Zero workflow. Before editing, checking, testing, or repairing Zero code, ask the installed compiler for the skill content that matches that exact binary: ```sh zero skills list 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 list /path/to/zero skills get zero --full ``` Use `zero skills list` to discover additional skills bundled with that Zero version. Use `zero skills get <name>` to load the one relevant to the task. Common inner skills include `zero-agent`, `zero-language`, `zero-diagnostics`, `zero-packages`, `zero-builds`, `zero-testing`, and `zero-stdlib`. ## Common Entry Points ```sh zero check --json <file-or-package> zero graph --json <file-or-package> zero size --json <file-or-package> zero explain <diagnostic-code> zero fix --plan --json <file-or-package> ``` In a Zero repository checkout, prefer `bin/zero` when the task is about that checkout rather than the globally installed compiler.