6 / 168 · 01 Agent Skills for Browser Automation · Anatomy of a SKILL.md File← prev⊞ allnext →☰ Read as one page
1.6How the Agent Uses the Skill at Runtime
Here's what happens when you say "Go to example.com and take a screenshot":
1. User: "Go to example.com and take a screenshot"
2. The agent reads available skills → finds the browser skill description matches
3. The agent invokes: Skill(skill="playwright-cli")
4. System injects SKILL.md content into conversation context
5. The agent now knows the full command surface
6. The agent executes via Bash:
→ playwright-cli open https://example.com
→ playwright-cli screenshot
7. The agent reports: "Done. Screenshot saved to .playwright-cli/screenshot.png"
The key insight: steps 1-5 happen transparently. The user never sees the SKILL.md. They just see the agent driving a browser.