2.5k
GitHub Stars
5
Bundled Files
3 weeks ago
Catalog Refreshed
1 month ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill openclaw/skills --skill ghost-browser- _meta.json639 B
- AGENTS_INTEGRATION.md1.7 KB
- requirements.txt15 B
- setup.sh943 B
- SKILL.md14.7 KB
Overview
This skill provides an automated Chrome browser interface driven by nodriver and optimized for LLM-controlled web tasks. It exposes a compact CLI with LLM-friendly commands for navigation, interaction, session management, screenshots, and clean markdown page reads. Commands prioritize minimal token usage and reliable element matching by visible text.
How this skill works
The skill runs a local browser daemon that accepts concise CLI commands to navigate pages, list interactive elements, interact by visible text, and produce readable markdown. It saves and restores full session state (cookies, localStorage, sessionStorage) and exposes JSON output for machine use. Fallback CSS-selector actions and debugging tools (network/console logs) are available when text-based interaction is insufficient.
When to use it
- Automated login flows and session persistence across runs
- Scraping or reading pages as clean markdown rather than raw HTML
- Form filling, file uploads, and click/hover interactions by visible labels
- Taking screenshots or generating PDFs of pages reliably
- Debugging dynamic pages with network and console logs
Best practices
- Always follow the recommended workflow: navigate → wait-ready → page-summary → elements → interact/readable
- Prefer text-based commands (interact/click/type/fill-form) before using CSS selectors
- Use readable or readable --max-length for token-efficient page extraction; avoid raw content (HTML) unless necessary
- Save authenticated state with session save and reuse via session load or profiles for persistent automation
- Run the daemon headless for CI or with named profiles for persistent local development
Example use cases
- Automate site login, save session, and perform authenticated scraping of dashboards
- Run an agent to walk a multi-step signup flow and capture screenshots at key steps
- Extract article content as markdown for summarization or ingestion into downstream tools
- Test UI flows by listing elements, clicking by label, and validating page-summary outputs
- Collect network logs and console errors for diagnosing intermittent client-side failures
FAQ
Yes. Start the daemon with --headless for headless operation suitable for CI and servers.
How are sessions stored and secured?
Sessions, profiles, and logs live under the skill's state/ directory. Session files contain cookies and storage data—treat them as sensitive and delete when no longer needed.