feat(skills): rename "agent-browser" skill to "core"; make CLI-served main skill actually useful (#1253)

Before this change, the main skill served by the CLI (`agent-browser skills get agent-browser`) was a ~40-line discovery stub whose content was essentially "run `agent-browser skills get <name>` before doing anything." Agents already inside the CLI got no signal from it — the content they needed to actually use the tool lived only in the `--full` references. Split the two jobs apart: - **`skill-data/core/`** (new) — the runtime usage guide. 420-line `SKILL.md` covering the snapshot-and-ref loop, common workflows (login, extract, screenshot, multi-tab, sessions, iframes, dialogs), waiting strategies, element selection strategies, troubleshooting, and when to load a specialized skill. Supplementary `references/` and `templates/` (moved from `skills/agent-browser/`) provide the full command reference under `--full`. - **`skills/agent-browser/SKILL.md`** — still the discovery stub that `npx skills add` installs, now marked `hidden: true` so it stays out of `skills list` inside the CLI. Body is a clean pointer to `agent-browser skills get core` and the specialized skills. The `hidden: true` frontmatter flag is a new, general mechanism: skills marked hidden are omitted from `skills list` and `skills get --all` but can still be fetched by explicit name. This keeps the stub reachable for anyone who installed via `npx skills add` without polluting the CLI-side skill listing. ## Behavior ``` $ agent-browser skills list agentcore Run agent-browser on AWS Bedrock AgentCore cloud browsers... core Core agent-browser usage guide. Read this before running... dogfood Systematically explore and test a web application... electron Automate Electron desktop apps (VS Code, Slack, Discord...) slack Interact with Slack workspaces using browser automation... vercel-sandbox Run agent-browser + Chrome inside Vercel Sandbox microVMs... $ agent-browser skills get core # the actual usage guide # ~420 lines of workflows, patterns, troubleshooting $ agent-browser skills get agent-browser # still works if called explicitly # the thin stub, now pointing at `core` ``` External `npx skills add vercel-labs/agent-browser` behavior is unchanged: it finds and installs the thin `agent-browser` stub, which tells the agent to run `agent-browser skills get core` for real content. Version drift protection is preserved — the stub is the only thing that gets copied; the real content is always runtime-fetched. ## Updated - `cli/src/skills.rs` — `SkillInfo.hidden: bool`, parsed from frontmatter; `run_list` and `run_get --all` filter it. 3 new unit tests for the frontmatter parser. - `cli/src/output.rs` — top-level `--help` and `skills` subcommand help reference `skills get core` / `skills get core --full`. - `AGENTS.md` — "update these files for user-facing features" now points at `skill-data/core/` instead of the stub, with a note that the stub is not the right place for feature content. - `README.md`, `docs/src/app/skills/page.mdx` — describe the new split and `skills get core --full` as the recommended entry point. - `evals/cases/{command-usage,skill-selection}.ts` — expect `skills get core` in agent output instead of `skills get agent-browser`. Eval lib still reads `skills/agent-browser/SKILL.md` (simulating what an agent sees after `npx skills add`). All 11 skills unit tests pass. `cargo clippy -- -D warnings` and `cargo fmt --check` clean. Verified end-to-end: `skills list` shows `core` + specialized (no stub), `skills get core` returns the new content, `skills get agent-browser` still returns the stub on explicit request.
2026-04-16 14:36:59 -05:00
parent 1afcaa0e84
commit 4cc6ca40b7
19 changed files with 513 additions and 39 deletions
@@ -0,0 +1,173 @@
+# Video Recording
+
+Capture browser automation as video for debugging, documentation, or verification.
+
+**Related**: [commands.md](commands.md) for full command reference, [SKILL.md](../SKILL.md) for quick start.
+
+## Contents
+
+- [Basic Recording](#basic-recording)
+- [Recording Commands](#recording-commands)
+- [Use Cases](#use-cases)
+- [Best Practices](#best-practices)
+- [Output Format](#output-format)
+- [Limitations](#limitations)
+
+## Basic Recording
+
+```bash
+# Start recording
+agent-browser record start ./demo.webm
+
+# Perform actions
+agent-browser open https://example.com
+agent-browser snapshot -i
+agent-browser click @e1
+agent-browser fill @e2 "test input"
+
+# Stop and save
+agent-browser record stop
+```
+
+## Recording Commands
+
+```bash
+# Start recording to file
+agent-browser record start ./output.webm
+
+# Stop current recording
+agent-browser record stop
+
+# Restart with new file (stops current + starts new)
+agent-browser record restart ./take2.webm
+```
+
+## Use Cases
+
+### Debugging Failed Automation
+
+```bash
+#!/bin/bash
+# Record automation for debugging
+
+agent-browser record start ./debug-$(date +%Y%m%d-%H%M%S).webm
+
+# Run your automation
+agent-browser open https://app.example.com
+agent-browser snapshot -i
+agent-browser click @e1 || {
+    echo "Click failed - check recording"
+    agent-browser record stop
+    exit 1
+}
+
+agent-browser record stop
+```
+
+### Documentation Generation
+
+```bash
+#!/bin/bash
+# Record workflow for documentation
+
+agent-browser record start ./docs/how-to-login.webm
+
+agent-browser open https://app.example.com/login
+agent-browser wait 1000  # Pause for visibility
+
+agent-browser snapshot -i
+agent-browser fill @e1 "demo@example.com"
+agent-browser wait 500
+
+agent-browser fill @e2 "password"
+agent-browser wait 500
+
+agent-browser click @e3
+agent-browser wait --load networkidle
+agent-browser wait 1000  # Show result
+
+agent-browser record stop
+```
+
+### CI/CD Test Evidence
+
+```bash
+#!/bin/bash
+# Record E2E test runs for CI artifacts
+
+TEST_NAME="${1:-e2e-test}"
+RECORDING_DIR="./test-recordings"
+mkdir -p "$RECORDING_DIR"
+
+agent-browser record start "$RECORDING_DIR/$TEST_NAME-$(date +%s).webm"
+
+# Run test
+if run_e2e_test; then
+    echo "Test passed"
+else
+    echo "Test failed - recording saved"
+fi
+
+agent-browser record stop
+```
+
+## Best Practices
+
+### 1. Add Pauses for Clarity
+
+```bash
+# Slow down for human viewing
+agent-browser click @e1
+agent-browser wait 500  # Let viewer see result
+```
+
+### 2. Use Descriptive Filenames
+
+```bash
+# Include context in filename
+agent-browser record start ./recordings/login-flow-2024-01-15.webm
+agent-browser record start ./recordings/checkout-test-run-42.webm
+```
+
+### 3. Handle Recording in Error Cases
+
+```bash
+#!/bin/bash
+set -e
+
+cleanup() {
+    agent-browser record stop 2>/dev/null || true
+    agent-browser close 2>/dev/null || true
+}
+trap cleanup EXIT
+
+agent-browser record start ./automation.webm
+# ... automation steps ...
+```
+
+### 4. Combine with Screenshots
+
+```bash
+# Record video AND capture key frames
+agent-browser record start ./flow.webm
+
+agent-browser open https://example.com
+agent-browser screenshot ./screenshots/step1-homepage.png
+
+agent-browser click @e1
+agent-browser screenshot ./screenshots/step2-after-click.png
+
+agent-browser record stop
+```
+
+## Output Format
+
+- Default format: WebM (VP8/VP9 codec)
+- Compatible with all modern browsers and video players
+- Compressed but high quality
+
+## Limitations
+
+- Recording adds slight overhead to automation
+- Large recordings can consume significant disk space
+- Some headless environments may have codec limitations