Skill API Reference

May 16, 2026 · View on GitHub

Definitive reference for AgentOps SKILL.md frontmatter fields. Schema: schemas/skill-frontmatter.v1.schema.json.

Publicly, AgentOps talks about bookkeeping, validation, primitives, and flows. This document describes the internal API and taxonomy behind that operating model.

Frontmatter Format

Every skill has a YAML frontmatter block between --- delimiters at the top of SKILL.md:

---
name: my-skill
description: 'What this skill does. Triggers: "keyword1", "keyword2".'
skill_api_version: 1
context:
  window: fork
  intent:
    mode: task
  sections:
    exclude: [HISTORY]
  intel_scope: topic
metadata:
  tier: execution
---

Required Fields

FieldTypeDescription
namestringSkill identifier (must match directory name)
descriptionstringWhat the skill does, including trigger phrases
skill_api_versionintegerAlways 1 (const)

Optional Fields

context

Controls what knowledge ao lookup --for=<skill> provides. Two forms:

String form (backward compat):

context: fork

Object form (recommended):

context:
  window: isolated
  intent:
    mode: task
  sections:
    exclude: [HISTORY]
  intel_scope: full

context.window

How the skill's execution context relates to the parent session.

ValueMeaning
isolatedFresh context, no parent inheritance. For validation and mechanical skills.
forkCopy parent context as starting point. For skills that need to know what you're working on.
inheritUse full parent context as-is. For session utilities (status, handoff, recover).

v1 status: Parsed and stored. Not enforced at runtime (Phase 2). Do not rely on this field alone for /rpi phase isolation; use the phase-isolated skill transport contract in skills/rpi/references/isolation-contract.md.

context.sections

Filter which knowledge sections are injected.

sections:
  include: [INTEL, TASK]     # Allowlist — only these sections
  exclude: [HISTORY]         # Blocklist — everything except these

If both include and exclude are set, include takes precedence.

Valid section names:

SectionKnowledge Fields
HISTORYPast session summaries
INTELLearnings and patterns from the knowledge flywheel
TASKCurrent bead ID and predecessor context

v1 status: Actively enforced at runtime. ao lookup --for=<skill> zeroes excluded/non-included sections.

context.intent.mode

Declares what the skill is doing.

ValueMeaning
taskExecuting work (implement, plan, validate)
questionsExploring or researching
noneOperational utility (status, push, update)

v1 status: Parsed and stored. Not enforced at runtime (Phase 2 — orchestrators will use this to adapt behavior).

context.intel_scope

How much of the knowledge flywheel to inject.

ValueMeaning
fullAll learnings and patterns
topicOnly learnings matching the current query/task
noneNo learnings or patterns injected

v1 status: none is actively enforced (zeroes learnings + patterns). topic and full are declaration-only (Phase 2).

allowed-tools

Restricts which tools the skill can auto-approve.

# Array form
allowed-tools:
  - Read
  - Grep
  - Glob
  - Bash

# String form (comma-separated)
allowed-tools: Read, Grep, Glob, Bash

model

Preferred model for skill execution.

model: haiku    # Use cheaper/faster model for lightweight skills

Currently used by flywheel and status. Declaration-only — no CLI enforcement.

user-invocable

Whether the skill appears in the slash-command list.

user-invocable: true   # Shows as /skill-name
user-invocable: false  # Hidden from user, used by other skills

metadata

Skill classification and dependency information.

metadata:
  tier: execution           # See tier values below
  dependencies: [standards] # Skills loaded as context
  internal: false           # If true, not published externally
  version: "1.0.0"
  author: "Gas Town"
  triggers: ["keyword"]     # Additional trigger phrases
  replaces: old-skill-name  # Supersedes another skill

Tier Values

TierPurposeExample Skills
judgmentLegacy internal tier name for validation and review gatescouncil, vibe, pre-mortem, post-mortem
executionSingle-task implementationimplement, bug-hunt, complexity, security-suite
orchestrationMulti-skill coordinationrpi, crank, swarm, evolve
sessionSession lifecyclehandoff, recover, status, quickstart
backgroundMechanical utilitiespush, ratchet, flywheel, forge
knowledgeKnowledge managementcompile, trace
productProduct strategyproduct, readme, release, goals
libraryShared referencesshared, standards, beads
metaSystem-levelusing-agentops, update, heal-skill
contributeExternal contributionspr-plan, pr-implement, pr-research, oss-docs
cross-vendorCross-platformopenai-docs, codex-team, converter, grafana-platform-dashboard

output_contract

Path to a JSON Schema file that defines the skill's structured output format.

output_contract: skills/council/schemas/verdict.json

Used by downstream skills to validate that upstream output matches the expected schema. Paths are relative to repo root.

v1 status: Declaration-only. No runtime enforcement. Consumed by skill chaining validation tooling.

Other Fields

FieldTypeDescription
licensestringLicense identifier (e.g., MIT)
compatibilitystringRuntime requirements (e.g., Requires git, gh CLI)

Context Declaration Quick Reference

Core skills and their context policies:

SkillWindowSectionsIntentIntel Scope
Validation (tier: judgment)
councilisolatedexclude: HISTORYtaskfull
vibeforkexclude: HISTORYtask
pre-mortemforkexclude: HISTORYtask
post-mortemforkexclude: HISTORYtask
Orchestration
rpifork
crankforkexclude: HISTORYtaskfull
swarmforkexclude: HISTORYtaskfull
evolveforkexclude: HISTORYtaskfull
Execution
implementisolatedexclude: HISTORYtasktopic
bug-huntforkexclude: HISTORYtasktopic
docforkexclude: HISTORYtasktopic
complexityforkexclude: HISTORYtasktopic
securityforkexclude: HISTORYtasktopic
security-suiteforkexclude: HISTORYtasktopic
reverse-engineer-rpiforkexclude: HISTORYtasktopic
grafana-platform-dashboardforkexclude: HISTORY, TASKquestionsnone
Knowledge
researchforkexclude: HISTORY, TASKquestionstopic
traceforkexclude: HISTORYtaskfull
compileforkexclude: TASKtaskfull
forgeforkexclude: TASKtaskfull
flywheelforkexclude: TASKtaskfull
retrofork
Session
handoffinheritnonenone
recoverinheritnonenone
statusinheritnonenone
quickstartinheritnonenone
Background
pushisolatedexclude: HISTORY, INTEL, TASKnonenone
ratchetisolatedexclude: HISTORY, INTEL, TASKnonenone
updateisolatedexclude: HISTORY, INTEL, TASKnonenone
heal-skillisolatedexclude: HISTORY, INTEL, TASKnonenone
Product
productforkexclude: HISTORYtaskfull
readmeforkexclude: HISTORYtaskfull
releaseforkexclude: HISTORYtaskfull
goalsforkexclude: HISTORYtasktopic
Contribute
pr-planforkexclude: HISTORYtasktopic
pr-implementforkexclude: HISTORYtasktopic
pr-prepforkexclude: HISTORYtasktopic
pr-researchforkexclude: HISTORYtasktopic
pr-retroforkexclude: HISTORYtasktopic
pr-validateforkexclude: HISTORYtasktopic
oss-docsforkexclude: HISTORYtasktopic
Library/Meta
sharedisolatedexclude: HISTORY, INTEL, TASKnonenone
standardsisolatedexclude: HISTORY, INTEL, TASKnonenone
using-agentopsisolatedexclude: HISTORY, INTEL, TASKnonenone
converterisolatedexclude: HISTORY, INTEL, TASKnonenone
beadsforkexclude: HISTORYtasktopic
injectfork
provenancefork
Cross-Vendor
openai-docsforkexclude: HISTORY, TASKquestionsnone
codex-teamfork
brainstorminheritexclude: INTEL, HISTORY, TASKnonenone
planforktasktopic

Enforcement Summary (v1)

FieldRuntime Enforcement
sections.includeActive — zeroes non-included knowledge
sections.excludeActive — zeroes excluded knowledge
intel_scope: noneActive — zeroes learnings + patterns
intel_scope: topic/fullDeclaration-only (Phase 2)
context.windowDeclaration-only (Phase 2)
context.intent.modeDeclaration-only (Phase 2)
allowed-toolsActive — controls auto-approval
modelDeclaration-only

See Also

  • Skills Reference — Skill descriptions and router
  • Skill Tiers — Taxonomy and dependency graph
  • Schema: schemas/skill-frontmatter.v1.schema.json