Detailed Phase Breakdown
Deep dive into each phase of the Skill Adapter Protocol with examples, templates, and implementation details
Learn Phase
Passive observation and documentation of platform interfaces and user flows
Translate Phase
Synthesis of observations into structured, executable skill definitions
Execute Phase
Deployment and execution with persistent state tracking and error recovery
Core Objective
The Learn phase is about understanding the platform from the perspective of your chosen role. You're not just cataloging UI elements—you're mapping how a human expert would navigate and interact with the platform.
What to Document
UI Elements
Buttons, inputs, menus, navigation elements with their text labels and locations
User Flows
Step-by-step sequences for common tasks (e.g., "To post: Home → Compose → Type → Publish")
Affordances
What each UI element enables (e.g., "Search box allows content discovery")
Skill Mappings
How role-specific capabilities map to platform features
Exploration Strategy
Sample Learn Phase Output
Core Objective
Transform raw observations into a structured, executable SAP file. This phase converts human-readable documentation into a format that AI agents can parse and execute autonomously.
SAP File Structure
YAML Header
Metadata including name, platform, version, author, role context
Skills Section
10-12 structured skills with YAML metadata and execution steps
Role Orchestrator
Workflow sequences, conditional logic, error handling, success metrics
Skill Definition Components
Sample Skill Definition
Core Objective
Deploy the SAP file as a living, breathing agent that can execute tasks autonomously while maintaining transparency, safety, and adaptability through persistent state management.
Execution Features
Task Checklists
Persistent state tracking with TODO/DONE/FAILED status for each task
Real-time Monitoring
Live status updates, performance metrics, and execution logs
Error Recovery
Automatic retry logic, fallback strategies, and graceful degradation
Safety Mechanisms
Sample Execution Checklist
The three phases work together as a continuous improvement cycle. Each execution provides feedback that can inform future learning and translation phases.
Learn → Translate
Rich observations enable comprehensive skill definitions. Poor documentation leads to incomplete or unreliable skills.
Translate → Execute
Well-structured SAP files execute smoothly. Missing error handling or unclear steps cause execution failures.
Execute → Learn
Execution failures reveal gaps in understanding. Platform changes trigger new learning cycles.
Continuous Improvement Cycle
SAP is designed for iterative refinement. Monitor execution metrics, identify failure patterns, and periodically re-run learning phases to adapt to platform changes. This creates agents that become more reliable and effective over time.