# Solnix agent skills
Skills for AI agents (and people) working with **Solnix**, the illumos distribution
built with Nix: using it, running it, porting software to it, writing Nix for it,
contributing to it, building for its binary cache. They cover illumos itself too (SMF,
ZFS, zones, Crossbow, the link editor, mdb, DTrace, libumem, FMA, RBAC, boot
environments), and say where Solnix does something differently from upstream illumos.
One repository for every agent, in the [Agent Skills](https://agentskills.io/) layout
(`
/SKILL.md` with YAML frontmatter). CC0-1.0: no attribution needed.
- Source:
- Mirror:
- Map and rules: [`AGENTS.md`](AGENTS.md); everything listed: [`CATALOG.md`](CATALOG.md)
## Use it over MCP (no install)
The Solnix MCP server serves these skills and the tools they use:
```
https://solnix.io/mcp (streamable HTTP, no auth)
```
- Claude Code: `claude mcp add --transport http solnix https://solnix.io/mcp`
- Kiro: add to `.kiro/settings/mcp.json`:
`{"mcpServers": {"solnix": {"url": "https://solnix.io/mcp"}}}`
- Any MCP client: point it at the URL above.
Then ask for `find_skill {"task": "..."}` and `get_skill {"name": "solnix-porter"}`.
Clients with the MCP Skills extension (SEP-2640) also see them under `skills/list`.
## Install as files
Clone once and put the clone where your agent looks for skills:
```sh
git clone https://codeberg.org/solnix/skills.git solnix-skills
```
| agent | location |
|---|---|
| Claude Code | `~/.claude/skills/solnix` (or a project's `.claude/skills/solnix`) |
| Kiro, Pi | `~/.kiro/skills/solnix` |
| any other | its skills directory |
Point the agent at the root `AGENTS.md` (most read it on their own; `CLAUDE.md` is a
one-line stub that imports it). For always-on rules, wire in `steering/` as
[`steering/README.md`](steering/README.md) shows.
## What is in it
- `solnix//SKILL.md`: seven personas (user, sysadmin, porter, nix-dev,
illumos-dev, contributor, builder). Each is a short map: steps with a completion
check, the tools it uses, and pointers into the rules.
- `solnix/rules/`: the shared rule library, one rule per file, each citing its sources.
- `steering/`: always-on rules (honesty, query first, Solnix vs upstream illumos,
confirm before destroying, voice, privacy).
- `workflows/`: step-by-step procedures.
- `tools/`: `check.py` (lint and link check), `catalog.py` (writes CATALOG.md),
`manifest.py` (writes manifest.json, the per-file sha256 digests), and `sign-manifest` (signs it at release:
`manifest.json.sig`, ed25519, key `solnix-skills-1:aFFBL7b8vVvGAi0TpHh/Yj4WiHS3Ts/eGKtKRynae4A=`; check a copy with
`python3 tools/sign-manifest --verify`, or with OpenSSL as https://solnix.io/security#skills-signing-key shows).
## Status
The sysadmin, porter, illumos-dev and contributor personas, their rules and the two data
tables are reviewed (every claim checked against its sources by an independent reviewer).
The nix-dev and builder skills are drafts awaiting the Solnix build team's review; user is
the phase-1 migration.
## Contributing
Patches to `hackers@solnix.io` or pull requests on Codeberg. Read `AGENTS.md`
"Contributing to this repository" first: one rule per file, every claim cited.