Orbit Support Agent — AI skill for Claude Code

Orbit Support Agent — the Pydantic AI 2.0 capability pattern

A small, runnable demo of the one idea that changed in Pydantic AI 2.0: you stop **configuring** an agent through a giant constructor and start **composing** it out of *capabilities*.

The idea

A **capability** is one composable brick that bundles everything that used to be scattered across the `Agent(...)` call — its instructions, its tools, its model settings, and its lifecycle hooks — into a single self-contained unit. You build an agent by snapping bricks together, and the same brick drops into a completely different agent, unchanged.

from pydantic_ai import Agent
from pydantic_ai.capabilities import Thinking

agent = Agent(
    "openrouter:anthropic/claude-sonnet-4.6",
    capabilities=[
        KnowledgeBaseCapability(),   # its instructions + its tool + model settings + a guardrail
        EscalationCapability(),      # its own tool + its own instructions
        Thinking(effort="low"),      # a built-in capability, one line
        audit_hooks(),               # lifecycle hooks, no subclass needed
    ],
)

That is the whole thesis: **compose, don't configure.** Each brick carries its own instructions, tools, settings, and hooks, so nothing has to be hand-wired onto the agent and nothing is welded to one model. The payoff is reuse — pick a brick up and drop it into the next agent without touching it.

What's in here

File	What it shows
cli.py	An interactive REPL. After every answer it prints a "capabilities used this turn" panel that maps each tool call back to the capability that owns it. /faq swaps to an agent that reuses the KnowledgeBase brick, live.
main.py	The agent composed from capabilities, then the reuse payoff: the same brick dropped into a second, unrelated agent without a single change.
capabilities.py	The capabilities themselves — each one a small class bundling its own instructions, tool, settings, and ho