12 / 168 · 01 Agent Skills for Browser Automation · Skill Lifecycle: From Installation to Execution← prev⊞ allnext →☰ Read as one page
2.5Phase 5: Execution
With the SKILL.md instructions in context and tools available, the agent proceeds to execute. For a browser skill, this typically means:
Agent reads: "playwright-cli open <url> — launch browser at a page"
Agent executes: Bash("playwright-cli open https://example.com")
Agent reads: "playwright-cli snapshot — save page state to disk"
Agent executes: Bash("playwright-cli snapshot")
Agent reads the snapshot file only if it needs it, and decides next actions
The agent is now operating with domain knowledge (how to use vibe-check) that it didn't have before the skill was loaded. This is the core value of skills.
Error Recovery During Execution
When a command fails, the agent:
- Reads the error output from Bash
- Applies its reasoning (enhanced by SKILL.md tips)
- Tries alternative approaches
Example: If playwright-cli click e14 fails with a timeout, the agent might:
- Run
playwright-cli snapshotand read it to see what's actually on the page - Run
playwright-cli screenshotto inspect the visual state - Pick a different element ref based on what it finds
This is not self-healing in the traditional sense — it's an intelligent agent reasoning about failures, which is more flexible than any static retry logic.