Skip to content

Skill for your coding agent

aura skill install writes a skill into your repo that teaches a coding agent how to drive Aura: the run/ + data/ layout contract, the deploy loop, how to create a project and read a run’s result, and where the rest of these docs are. Your agent loads it when the task in front of it turns out to be about Aura.

Terminal window
aura skill install

It talks to no server, so it needs no API key.

Agent Skills directories it reads
Claude Code .claude/skills/
Codex .agents/skills/
opencode .opencode/skills/, .agents/skills/, .claude/skills/
pi .pi/skills/, .agents/skills/

Codex, opencode and pi all read .agents/skills, so one file there usually serves three of them. Each line it prints names every agent that reads the file it wrote, not only the one you asked for — so --claude reports read by Claude Code, opencode.

Given no flags, it looks for .claude/, CLAUDE.md, .codex/, .agents/, .opencode/ and .pi/ in the repo, falls back to the same names under your home directory, and installs for what it finds. Naming an agent turns detection off, and installs for exactly the ones you named.

A .agents/ directory counts for Codex, opencode and pi alike: its presence says one of the three put it there, never which — and the one file answers for all three.

Flag Installs for
--claude Claude Code
--codex Codex
--opencode opencode
--pi pi
--all all four
Terminal window
aura skill install --claude --codex

A root AGENTS.md is deliberately not treated as a Codex marker: in a repo holding an Aura model, that filename is more likely the Run agent’s instructions.

An agent that reads several is only asked about when the repo settles nothing. It is settled when the skill is already installed in one of them, or when that agent’s own marker names one — .opencode/ present means .opencode/skills. Otherwise you get the list, defaulting to a directory another agent in the same run already claimed, so pressing enter through it yields one file rather than three.

At the repo root — the directory holding .git — because every one of these agents searches from the directory it started in upward, and would never see a skill left in a subdirectory. --dir <path> installs somewhere else instead, and fails rather than creating a path you mistyped.

Re-running after upgrading the CLI is how you take a newer skill, and it prints already current when there is nothing to do.

A file you have edited since is left alone: the command names it, writes none of the other targets, and stops. --force replaces it. To read the skill without writing anything — to diff it, or to place it somewhere this command does not know about — use --print, which writes it to stdout.

Terminal window
aura skill install --print > my-own-copy.md