evolve skills

The manual ships with the CLI. An agent can read its index, then load just the page it needs.

evolve skills get evals
evolve skills get evals cli-reference/run

Installed pointer: evolve
  ↓
Documentation index
  evolve skills get evals
  ↓
One focused page
  evolve skills get evals PAGE

These commands read local files and need no API key. The manual matches the installed CLI; it does not refresh from the website. See skill to upload skills for evaluated agents.

List the bundled skills

evolve skills
evolve skills list --json

Skill	Purpose
`evals`	Managed evaluations: concepts, CLI, APIs, and SDKs.
`create-task`	Author a Harbor-format task.
`rewardkit`	Write a verifier with Reward Kit.
`create-adapter`	Convert a benchmark into tasks.
`swebench-to-harbor`	Convert SWE-bench-format instances into tasks.
`publish`	Publish task datasets or import completed results.

The evolve entry point, also called the pointer skill, is available by explicit name but hidden from the list. Agent SDK guides are available on the website; evolve skills does not serve the separate evolve-agents skill.

Read a skill or page

evolve skills get create-task
evolve skills get create-task rewardkit
evolve skills get evals core-concepts/tasks

Option	Meaning
`--full`	Include all files under the skill’s references and templates.
`--all`	Read every listed skill without supplying names.

Use the listed name, such as evals, rather than its folder name evolve-evals. A second argument that names another skill reads both skills; otherwise, it selects a page in the first skill. get <skill> <page> accepts a path under references/ without that prefix, with or without .md/.mdx. It cannot combine with --full. --all cannot combine with skill names. Prefer the index and focused pages. Use --full when the complete reference is needed. Without --json, get prints the skill body without its YAML frontmatter. --full adds reference and template files after --- <path> --- separators. It does not follow symbolic links.

Find files on disk

evolve skills path
evolve skills path evals

The optional skill name selects its folder. For local development, set EVOLVE_SKILLS_DIR to serve a different skills directory. A nonempty value must name an existing directory.

Install the pointer

evolve skills install
evolve skills install --target codex

Install the CLI first; see Installation. This command copies only the small evolve/SKILL.md pointer and prints each destination. The full manual stays in the CLI package.

Option	Meaning
`--target <name>`	`claude`, `codex`, `cursor`, `copilot`, `gemini`, `opencode`, `agents`, or `all`. Default `all`.
`--path <dir>`	Your own skills directory instead of a named target.
`--force`	Replace an installed pointer whose contents differ.

Target locations

Each target receives evolve/SKILL.md inside its skills directory:

Target	Skills directory
`claude`	`~/.claude/skills`
`codex`	`~/.codex/skills`
`cursor`	`~/.cursor/skills`
`copilot`	`~/.copilot/skills`
`gemini`	`~/.gemini/skills`
`opencode`	`$XDG_CONFIG_HOME/opencode/skills`, or `~/.config/opencode/skills` when unset or empty.
`agents`	`~/.agents/skills`

all installs only where the parent of the skills directory already exists. A named target creates its directory when missing. If no agent home exists, the command writes nothing, reports that on stderr, and exits successfully. Choose --target or --path to create a destination. An identical pointer is left unchanged. Different content requires --force. The command checks every destination before writing. A file where a directory is needed, or a directory where SKILL.md is needed, blocks the install even with --force. --target and --path cannot be combined. Global options, including JSON output, apply.

JSON output

evolve skills get evals cli-reference/run --json

Command	JSON output
`list`	Array of `{ name, description, path }`. `path` is the skill folder.
`get <name> [name...]`	Array of `{ name, path, content }`. `content` includes YAML frontmatter.
`get <name> --full`	Same array, with `files`: an array of `{ path, content }` for references and templates. These file paths are relative to the skill folder.
`get <name> <page>`	One-item array of `{ name, page, path, content }`. `page` has no suffix.
`path`	`{ path }`, or `{ name, path }` with a skill name.
`install`	Array of `{ target, path, status }`. `status` is `written` or `unchanged`; no destinations produces `[]`.

list, get, and path return absolute paths, except for paths inside files. Install paths identify SKILL.md; page paths identify the selected file.

Errors

Unknown skills or pages, an invalid skills directory, and install conflicts exit with code 1. Unknown names report the available skills or pages. Invalid options or combinations exit with code 2; see CLI exit codes.

Start work

Inspect results

Manage resources