Practical guide · buzz agent skills
Buzz Agent Skills: Install, Scope, and Verify Them
A large skill catalog can make an agent look capable while widening prompt size, tool access, and failure surface.
Why this happens
The Block Agent Skills project defines skills as reusable instructions and resources, usually centered on a SKILL.md file. Installation makes instructions available; it does not prove the workflow succeeds.
What correct behavior looks like
A useful skill maps to one agent accountability, names inputs and outputs, limits tools and side effects, and has a test that produces inspectable evidence.
What to do
- 1Read the skill before installing it.
- 2Match it to a specific job rather than an agent personality.
- 3Check its scripts, network calls, credentials, and write boundaries.
- 4Install it through the supported skill mechanism.
- 5Run a safe fixture or commissioning job.
How to verify it worked
- The intended agent can actually load the skill.
- The test output matches the skill contract.
- No undeclared files, messages, purchases, or public actions occur.
- A failure is returned as failure, not a polished summary.
Common failure states
- Skill exists on disk but is outside the harness search path.
- Instructions conflict with agent authority.
- The skill expects a credential or binary the runtime cannot access.
What to do next
Connect the verified skill to a bounded workflow only when recurring execution is needed.
Related guides
FAQ
Does installing a skill prove it works?
No. It proves availability at most. Run the skill with safe input and inspect the requested output.
Should every agent get every skill?
No. Give each agent the smallest capability set its job requires.
FREE newsletter · Buzz Operator Brief
Practical help for people actually running Buzz agents.
Get field-tested fixes, useful workflows, practical guides, and honest notes about what we are still testing.
By subscribing, you agree to receive the Buzz Operator Brief. Unsubscribe anytime.