Chris Tate
4cc6ca40b7
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.
63 lines
1.8 KiB
Bash
Executable File
63 lines
1.8 KiB
Bash
Executable File
#!/bin/bash
|
|
# Template: Form Automation Workflow
|
|
# Purpose: Fill and submit web forms with validation
|
|
# Usage: ./form-automation.sh <form-url>
|
|
#
|
|
# This template demonstrates the snapshot-interact-verify pattern:
|
|
# 1. Navigate to form
|
|
# 2. Snapshot to get element refs
|
|
# 3. Fill fields using refs
|
|
# 4. Submit and verify result
|
|
#
|
|
# Customize: Update the refs (@e1, @e2, etc.) based on your form's snapshot output
|
|
|
|
set -euo pipefail
|
|
|
|
FORM_URL="${1:?Usage: $0 <form-url>}"
|
|
|
|
echo "Form automation: $FORM_URL"
|
|
|
|
# Step 1: Navigate to form
|
|
agent-browser open "$FORM_URL"
|
|
agent-browser wait --load networkidle
|
|
|
|
# Step 2: Snapshot to discover form elements
|
|
echo ""
|
|
echo "Form structure:"
|
|
agent-browser snapshot -i
|
|
|
|
# Step 3: Fill form fields (customize these refs based on snapshot output)
|
|
#
|
|
# Common field types:
|
|
# agent-browser fill @e1 "John Doe" # Text input
|
|
# agent-browser fill @e2 "user@example.com" # Email input
|
|
# agent-browser fill @e3 "SecureP@ss123" # Password input
|
|
# agent-browser select @e4 "Option Value" # Dropdown
|
|
# agent-browser check @e5 # Checkbox
|
|
# agent-browser click @e6 # Radio button
|
|
# agent-browser fill @e7 "Multi-line text" # Textarea
|
|
# agent-browser upload @e8 /path/to/file.pdf # File upload
|
|
#
|
|
# Uncomment and modify:
|
|
# agent-browser fill @e1 "Test User"
|
|
# agent-browser fill @e2 "test@example.com"
|
|
# agent-browser click @e3 # Submit button
|
|
|
|
# Step 4: Wait for submission
|
|
# agent-browser wait --load networkidle
|
|
# agent-browser wait --url "**/success" # Or wait for redirect
|
|
|
|
# Step 5: Verify result
|
|
echo ""
|
|
echo "Result:"
|
|
agent-browser get url
|
|
agent-browser snapshot -i
|
|
|
|
# Optional: Capture evidence
|
|
agent-browser screenshot /tmp/form-result.png
|
|
echo "Screenshot saved: /tmp/form-result.png"
|
|
|
|
# Cleanup
|
|
agent-browser close
|
|
echo "Done"
|