agentskill-description¶
Skill description should be meaningful and within length limits
| Severity | warning (auto) |
| Autofix | - |
| Since | v0.1.0 |
| Repo Types | agentskills, dot-claude, marketplace, single-plugin |
| Category | agentskills.io |
Why¶
The skill description is what the agent reads to decide whether to load the skill. A missing, empty, or overly long description means the skill is either invisible or consumes excessive tokens in the skill-selection prompt.
Examples¶
Bad:
Good:
---
name: deploy-staging
description: Deploy the application to the staging environment. Use
when the user asks to deploy, ship, or release to staging.
---
How to fix¶
Write a description that states what the skill does and when to use it. Keep it under 200 tokens — enough for the agent to make a selection decision, not a full manual. Use imperative voice and include trigger phrases the user might say.
Choosing a tighter budget¶
The length limit defaults to the agentskills.io spec's 1024
characters, so default behavior matches the spec. It is configurable
via max_length, and a tighter budget is recommended: the
description is permanent context, loaded into every prompt so the
agent can decide which skill to route to, meaning every character is
paid on every request — and some ecosystems rank or route on only a
prefix of the description. 256 is a good working budget:
Values above 1024 are honored as configured; the spec's own limit is enforced by the ecosystem at publish time.
Configuration¶
| Parameter | Description | Default |
|---|---|---|
max_length |
Maximum description length in characters (spec limit 1024; consider 256 to keep routing context lean) | 1024 |
Run skillsaw explain agentskill-description to see this documentation and the rule's effective configuration in your terminal.