product-tour-captureCapture product tour video segments using browser automation and screen recording. Coordinates timing between UI interactions and narration cues for demo and...
Install via ClawdBot CLI:
clawdbot install nissan/product-tour-captureGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://...Audited May 22, 2026 · audit v1.0
Generated Oct 8, 2026
A B2B SaaS team wants new signups to understand core features without a sales demo. They run the playbook against their production app to generate a 12-step /tour page, embed it in the onboarding email sequence, and reduce time-to-first-value.
A hackathon team needs judges to explore their Next.js app on their own schedule because live demo slots are limited. The playbook captures the key flows into a polished /tour page deployed alongside the project, letting judges self-tour any time.
After a major frontend redesign, a product team needs to show stakeholders every updated screen without scheduling a walkthrough. The capture agent re-runs the step list on the new build and the builder agent refreshes /tour in one playbook run.
A startup founder wants a shareable, interactive product tour link for investor decks and sales outreach. They configure a 14-step tour covering the landing page, dashboard, and demo pipeline, then send the deployed URL in pitch materials.
A customer support team regularly fields questions about where features live in the app. They capture annotated screenshots into a /tour page that doubles as a visual help center, reducing repetitive ticket volume and improving self-service.
The skill supports a PLG motion by giving every new user an instant, self-guided walkthrough of the product without human intervention. Tours can be refreshed automatically after each release, keeping the onboarding experience current and frictionless.
Web agencies can bundle product tour creation as a value-added deliverable for client projects. Each Next.js site shipped includes a polished /tour page generated by the playbook, differentiating the agency from competitors.
The playbook architecture and /tour page template can be packaged as a paid starter kit or boilerplate for Next.js developers. Buyers get the capture script, tour component, and agent workflow out of the box.
💬 Integration Tip
Install ffmpeg and Playwright browsers in the capture environment before running the script, and use the documented `node node_modules/next/dist/bin/next build` command instead of `npx next build` to avoid path issues on Node 24. Pin the TOUR_STEPS list to 14 steps and keep screenshots under public/tour/ so re-runs overwrite cleanly without cluttering the repo.
Scored Oct 8, 2026
A fast Rust-based headless browser automation CLI with Node.js fallback that enables AI agents to navigate, click, type, and snapshot pages via structured commands.
Uses a headless browser to navigate web pages, interact with elements, and extract clean, readable text content from URLs.
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection
High-performance browser automation for heavy scraping, multi-tab management, and precise DOM extraction. Use this when you need speed, reliability, or advanced state management (cookies/local storage) beyond standard web fetching.
Ultimate stealth browser automation with anti-detection, Cloudflare bypass, CAPTCHA solving, persistent sessions, and silent operation. Use for any web automation requiring bot detection evasion, login persistence, headless browsing, or bypassing security measures. Triggers on "bypass cloudflare", "solve captcha", "stealth browse", "silent automation", "persistent login", "anti-detection", or any task needing undetectable browser automation. When user asks to "login to X website", automatically use headed mode for login, then save session for future headless reuse.
Browser automation CLI (browser-act) for AI agents. MUST trigger when: (1) user mentions 'browser-act' in any form, or user needs to: (2) open/visit/browse/c...