colebanman/grabbit-skills
Overview
This skill exposes the Grabbit CLI to record browser interactions (HAR) and convert them into stable API workflows. It helps automate browser actions, capture web traffic for analysis, and produce deterministic workflows that agents or tools can call. Use it to iterate quickly from manual browsing to reusable API integrations.
How this skill works
You run Grabbit commands to start isolated sessions, drive a real browser (optionally headed), and take snapshots that produce stable element references. Captured network requests and example-rich prompts are submitted to Grabbit, which synthesizes a workflow you can poll for completion and then install or call via API keys. The skill also provides commands to manage workflows, keys, and troubleshooting errors.
When to use it
- Automating end-to-end browser actions that should become repeatable API calls.
- Capturing HAR/network traffic to reverse-engineer backend APIs for tooling or testing.
- Creating deterministic workflows from interactive sessions for agents or CI.
- Debugging sites with bot protection by using headed mode and visual snapshots.
- Learning and onboarding to the Grabbit CLI command set and best practices.
Best practices
- Always run sessions with --session <name> to isolate captures and avoid mixing data.
- Use --headed for sites with bot protection (Cloudflare) or when you need visual debugging.
- Take frequent snapshot commands to get stable @e# element references instead of fragile CSS selectors.
- Provide verbose, example-rich prompts when saving a capture: include example inputs and expected JSON outputs.
- Store and use scoped API keys via grabbit keys and export GRABBIT_API_KEY for agents and CI.
- If you see Unauthorized or no requests recorded, re-authenticate and ensure you started a browse session before saving.
Example use cases
- Record a checkout flow and generate an API workflow that submits orders programmatically.
- Capture a login and data fetch sequence to build a service that scrapes authorized endpoints via API calls.
- Convert a product search and filter session into a reproducible workflow returning structured JSON prices.
- Run headed sessions to debug 403/bot-blocking issues and extract stable selectors for automation.
- Install a generated workflow as a local skill and wire it into an agent with GRABBIT_API_KEY.
FAQ
Run grabbit check <task-id> to poll status. Ensure you included concrete examples in the save prompt; vague prompts slow or fail synthesis.
How do I keep requests scoped for production?
Use grabbit keys to create scoped tokens and export GRABBIT_API_KEY in your environment for tools and CI. Limit key scope to specific workflows when possible.