---
title: Skill
order: 4
description: "A packaged set of instructions an agent host loads when a task matches its description: a directory holding a SKILL.md. magus ships its magus-* skills in the binary and writes them with magus agent install."
tags: [glossary, agents]
---

# Skill

A packaged set of instructions an agent host loads when a task matches its
description: a directory holding a `SKILL.md` whose front matter carries a
`name` and a `description`. magus ships its `magus-*` skills in the binary and
writes them with `magus agent install`. Each is stamped with its version, so
`magus doctor` reports a hand edit as drift; instructions that belong to one
workspace go in a local skill beside them.

## Elsewhere

Anthropic's Agent Skills define the format magus writes: a `SKILL.md` with YAML front
matter, loaded in stages so only the name and description cost context until the skill is
used. The format is the same; what differs is ownership. A magus skill is generated output
of the binary, not a file a person edits, and the next install replaces it.

## Example

```sh
magus agent install --force
```

## Used in

<!-- BEGIN GLOSSARY USAGE (generated by glossary-usage-generate from the knowledge graph; edit the generator, not this list) -->

In the docs:

- [Choose a skill form deliberately](../guides/integrations/agents/skills.md#choose-a-skill-form-deliberately)
- [skill-description-budget](../reference/proofread/skill-description-budget.md#skill-description-budget)
- [skill-set-description-budget](../reference/proofread/skill-set-description-budget.md#skill-set-description-budget)
- [installed-skill](../reference/rules/installed-skill.md#installed-skill)
- [skill-source](../reference/rules/skill-source.md#skill-source)

In the code (`magus refs <name>` lists every site):

- `types.Skill` (Go)

<!-- END GLOSSARY USAGE -->

## See also

- [Agent](agent.md)
- [Harness](harness.md)