- Installs
- 704
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/vercel-labs/zerolang --skill zero- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads zero automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Zero
Zero is an agent-first programming language. zero.graph is the program; .0 files are projections of it. Edit through zero patch.
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.
Use the zero already on PATH or at ~/.zero/bin/zero when one exists; environments often pin a specific compiler, and replacing it silently breaks version-matched stores and workflows. Install only when zero is missing:
command -v zero >/dev/null 2>&1 || { curl -fsSL https://zerolang.ai/install.sh | bash; }
export PATH="$PATH:$HOME/.zero/bin"
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:
zero skills
zero skills get zero
zero skills get zero --full
zero skills get stdlib --topic std.time # one section instead of the whole topic
If the user has multiple Zero binaries, use the same binary that will run the project:
/path/to/zero skills
/path/to/zero skills get zero --full
Use zero skills get <name> to load only what the task needs, and fetch each
topic at most once per session: the content is fixed for a given compiler
binary, so refetching a loaded topic returns the same text. Topics and
approximate served sizes:
zero(~2 KB): this discovery stubagent(~4 KB): read-edit-verify loop, zero query usage, edit surfaces, verificationlanguage(~6 KB): syntax, types, effects, control flow, genericsgraph(~9 KB): zero.graph store, query/view, patch operations, import/export/mergediagnostics(~4 KB): reading diagnostics, zero explain, typed fix planspackages(~5 KB): manifests, package layout, creation and repairbuilds(~5 KB): build/run, targets, profiles, emitted artifactstesting(~3 KB): test blocks, filters, runtime checksstdlib(~39 KB): full signature reference, including ready-made validators:std.time(RFC 3339 incl. the exact leap-second rule),std.inet(IPv4/IPv6/hostname),std.regex(ECMA subset),std.unicode(strict UTF-8). Check here before hand-writing any parsing or validation logic. Fetch one module's section (~1 KB) withzero skills get stdlib --topic <prefix>, e.g.--topic std.time.
Before hand-writing any parsing or validation, check the stdlib catalog: zero skills get stdlib --topic <module> serves one section (std.time covers RFC 3339 incl. leap seconds).
Edit through the graph: zero patch covers everything from surgical in-function text edits (--replace-in-fn <fn> --old <text> --new <text>, Edit semantics) to complete helper creation (upsertFunction ... end) and whole function bodies (--replace-fn <fn> --body-file - with a heredoc). Direct .0 text edits are a last resort for changes no patch op expresses; package commands refresh zero.graph from edited source, but patch keeps the loop faster and preserves node identity. Read one function with zero view --fn <name> instead of whole files. Prefer concise text output during interactive agent work; use --json only for automation, exact spans, contracts, or machine-readable diagnostics.
Common Entry Points
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.
FAQ
What does the zero skill do?
Install Zero and load version-matched workflows with zero skills.
How do I install zero?
Run npx skills add https://github.com/vercel-labs/zerolang --skill zero in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/zero/ (personal) or .claude/skills/zero/ (project).
Which AI agents can use zero?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is zero safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains zero?
It is published by vercel-labs in vercel-labs/zerolang. It has 704 recorded installs.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.