Skills
A skill is a capability bundle: Markdown instructions plus an executor. Each agent has its own enabled skill list, independent of main.
Examples
| Skill | What it enables |
|---|---|
| read / write / edit | Files in the agent workspace |
| memory | Markdown notes plus local SQLite/vector recall when configured |
| search / http / browse / vision | Live search, direct HTTP fetches, Playwright browsing, screenshots, and image understanding |
| github | Repos, issues, pull requests |
| gog / gmail / calendar | Email search, summaries, sends, event creation, and free/busy checks |
| home-assistant | Lights, switches, sensors, scenes, scripts, and thermostat control |
| ssh-inspect | Read-only remote server, service, log, disk, and Docker inspection |
| agent-send | Delegate to another agent (with allow list) |
| cron | Reminders and scheduled jobs |
New agents
Skills are enabled per agent in configuration and surfaced in the dashboard. Keep powerful tools on the agents that need them, then use group deny lists or agent-specific settings to narrow access for shared contexts.
Intent planning
On each turn, Pasture Protocol classifies intent and selects relevant skill docs before the LLM loop. Not every enabled skill is loaded every time; the prompt gets the tools that fit the message and channel.
How skills are selected
| User intent | Typical skill path |
|---|---|
| Live information | search for summaries, browse for page interaction or proof |
| Reminder or recurring check | cron stores schedule plus originating chat/channel |
| Image, screenshot, or webcam | vision describes or generates images; browse screenshots can chain into vision |
| Remember or recall | memory saves explicit notes and searches notes/chat only when the user asks |
| Project planning | project-workflow links chat to Projects, Missions, Tasks, and progress logs |
| Home control | home-assistant resolves friendly names and replies with friendly summaries |
Skill boundaries
- Write-capable integrations preview important changes and ask for confirmation when the skill requires it.
- Group chats can deny specific skills even when the assigned agent normally has them.
- Secrets belong in the Pasture state directory, not in memory notes or project files.
- Powerful skills should be enabled only on agents that actually need them.