Capabilities & operations
Skills.
For: developers and operators
A skill is a capability an agent can run, written in Markdown. Each declares when it fires, what it consumes, what it produces, and what it touches in the database. Skills are how the agents do concrete work — from drafting a brief to draining a queue to onboarding an engagement.
Anatomy of a skill
What a skill declares
- Triggers — the phrases or schedule that fire it
- Inputs — what it needs to run
- Outputs — what it produces, and which records it writes
- An owner — the role responsible for it
How a skill behaves
- Writes through the audited write-path, never raw inserts
- Respects the human-in-the-loop gate on anything outbound
- Stays inside its role's read/write boundaries
The three firing modes
Human phrase
An operator asks for it in natural language; the matching skill runs.
Schedule
The Ticker fires it on a cadence — when the operator has that cadence enabled.
Skill to skill
One skill triggers another — fan-out, drain, escalate, ratify — to form a pipeline.
Families of skills
Rotation & bootstrap
Stand up the ring, validate config, rotate a role, sync the corpus, recover after a laptop loss.
Audit & hygiene
Scan for secrets, check kernel purity, verify the audit chain, mirror it off-site.
Conversation substrate
Group and classify inbound conversations, embed summaries, reconcile threads.
Publishing & reporting
Drain the publish queue, drive report cadences, produce the brief, shape outbound voice.
Engagement lifecycle
Mobilise a new engagement, transition a phase, close one out.
Documents & build
Enumerate the document canon (metadata only), and the durable build recipes.