vibe-check▌
vibiumdev/vibium · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
The vibium CLI automates Chrome via the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).
Vibium Browser Automation — CLI Reference
The vibium CLI automates Chrome via the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).
vibium go <url> && vibium map && vibium click @e1 && vibium map
Core Workflow
Every browser automation follows this pattern:
- Navigate:
vibium go <url> - Map:
vibium map(get element refs like@e1,@e2) - Interact: Use refs to click, fill, select — e.g.
vibium click @e1 - Re-map: After navigation or DOM changes, get fresh refs with
vibium map
Binary Resolution
Before running any commands, resolve the vibium binary path once:
- Try
vibiumdirectly (works if globally installed vianpm install -g vibium) - Fall back to
./clicker/bin/vibium(dev environment, in project root) - Fall back to
./node_modules/.bin/vibium(local npm install)
Run vibium --help (or the resolved path) to confirm. Use the resolved path for all subsequent commands.
Windows note: Use forward slashes in paths (e.g. ./clicker/bin/vibium.exe) and quote paths containing spaces.
Command Chaining
Chain commands with && to run them sequentially. The chain stops on first error:
vibium go https://example.com && vibium map && vibium click @e3 && vibium diff map
When to chain: Use && for sequences that should happen back-to-back (navigate → interact → verify). Run commands separately when you need to inspect output between steps.
When NOT to chain: Don't chain commands that depend on parsing the previous output (e.g. reading map output to decide what to click). Run those separately so you can analyze the result first.
Commands
Discovery
vibium map— map interactive elements with @refs (recommended before interacting)vibium map --selector "nav"— scope map to elements within a CSS subtreevibium diff map— compare current vs last map (see what changed)
Navigation
vibium go <url>— go to a pagevibium back— go back in historyvibium forward— go forward in historyvibium reload— reload the current pagevibium url— print current URLvibium title— print page title
Reading Content
vibium text— get all page textvibium text "<selector>"— get text of a specific elementvibium html— get page HTML (use--outerfor outerHTML)vibium find "<selector>"— find element, return@e1ref (clickable withvibium click @e1)vibium find "<selector>" --all— find all matching elements →@e1,@e2, ... (--limit N)vibium find text "Sign In"— find element by text content →@e1vibium find label "Email"— find input by label →@e1vibium find placeholder "Search"— find by placeholder →@e1vibium find testid "submit-btn"— find by data-testid →@e1vibium find xpath "//div[@class]"— find by XPath →@e1vibium find alt "Logo"— find by alt attribute →@e1vibium find title "Settings"— find by title attribute →@e1vibium find role <role>— find element by ARIA role →@e1(--namefor accessible name filter)vibium eval "<js>"— run JavaScript and print result (--stdinto read from stdin)vibium count "<selector>"— count matching elementsvibium screenshot -o file.png— capture screenshot (--full-page,--annotate)vibium a11y-tree— accessibility tree (--everythingfor all nodes)
Interaction
vibium click "<selector>"— click an element (also accepts@reffrom map)vibium dblclick "<selector>"— double-click an elementvibium type "<selector>" "<text>"— type into an input (appends to existing value)vibium fill "<selector>" "<text>"— clear field and type new text (replaces value)vibium press <key> [selector]— press a key on element or focused elementvibium focus "<selector>"— focus an elementvibium hover "<selector>"— hover over an elementvibium scroll [direction]— scroll page (--amount N,--selector)vibium scroll into-view "<selector>"— scroll element into view (centered)vibium keys "<combo>"— press keys (Enter, Control+a, Shift+Tab)vibium select "<selector>" "<value>"— pick a dropdown optionvibium check "<selector>"— check a checkbox/radio (idempotent)vibium uncheck "<selector>"— uncheck a checkbox (idempotent)
Mouse Primitives
vibium mouse click [x] [y]— click at coordinates or current position (--button 0|1|2)vibium mouse move <x> <y>— move mouse to coordinatesvibium mouse down— press mouse button (--button 0|1|2)vibium mouse up— release mouse button (--button 0|1|2)vibium drag "<source>" "<target>"— drag from one element to another
Element State
vibium value "<selector>"— get input/textarea/select valuevibium attr "<selector>" "<attribute>"— get HTML attribute valuevibium is visible "<selector>"— check if element is visible (true/false)vibium is enabled "<selector>"— check if element is enabled (true/false)vibium is checked "<selector>"— check if checkbox/radio is checked (true/false)vibium is actionable "<selector>"— check if element is actionable (true/false)
Waiting
vibium wait "<selector>"— wait for element (--state visible|hidden|attached,--timeout ms)vibium wait url "<pattern>"— wait until URL contains substring (--timeout ms)vibium wait load— wait until page is fully loaded (--timeout ms)vibium wait text "<text>"— wait until text appears on page (--timeout ms)vibium wait fn "<expression>"— wait until JS expression returns truthy (--timeout ms)vibium sleep <ms>— pause execution (max 30000ms)
Capture
vibium screenshot -o file.png— capture screenshot (--full-page,--annotate)vibium pdf -o file.pdf— save page as PDF
Dialogs
vibium dialog accept [text]— accept dialog (optionally with prompt text)vibium dialog dismiss— dismiss dialog
Emulation
vibium viewport— get current viewport dimensionsvibium viewport <width> <height>— set viewport size (--dprfor device pixel ratio)vibium window— get OS browser window dimensions and statevibium window <width> <height> [x] [y]— set window size and position (--state)vibium media— override CSS media features (--color-scheme,--reduced-motion,--forced-colors,--contrast,--media)vibium geolocation <lat> <lng>— override geolocation (--accuracy)vibium content "<html>"— replace page HTML (--stdinto read from stdin)
Frames
vibium frames— list all iframes on the pagevibium frame "<nameOrUrl>"— find a frame by name or URL substring
File Upload
vibium upload "<selector>" <files...>— set files on input[type=file]
Recording
vibium record start— start recording (--screenshots,--snapshots,--name)vibium record stop— stop recording and save ZIP (-o path)
Cookies
vibium cookies— list all cookiesvibium cookies <name> <value>— set a cookievibium cookies clear— clear all cookies
Storage State
vibium storage— export cookies + localStorage + sessionStorage (-o state.json)vibium storage restore <path>— restore state from JSON file
Downloads
vibium download dir <path>— set download directory
Pages
vibium pages— list open pagesvibium page new [url]— open new pagevibium page switch <index|url>— switch pagevibium page close [index]— close page
Debug
vibium highlight "<selector>"— highlight element visually (3 seconds)
Session
vibium start— start a local browser sessionvibium start <url>— start connected to a remote browservibium stop— stop the browser sessionvibium daemon start— start background browservibium daemon status— check if runningvibium daemon stop— stop daemon
Common Patterns
Ref-based workflow (recommended for AI)
vibium go https://example.com
vibium map
vibium click @e1
vibium map # re-map after interaction
Verify action worked
vibium map
vibium click @e3
vibium diff map # see what changed
Read a page
vibium go https://example.com && vibium text
Fill a form (end-to-end)
vibium go https://example.com/login
vibium map
# Look at map output to identify form fields
vibium fill @e1 "[email protected]"
vibium fill @e2 "secret"
vibium click @e3
vibium wait url "/dashboard"
vibium screenshot -o after-login.png
Scoped map (large pages)
vibium map --selector "nav" # Only map elements in <nav>
vibium map --selector "#sidebar" # Only map elements in #sidebar
vibium map --selector "form" # Only map form controls
Semantic find (no CSS selectors needed)
vibium find text "Sign In" # → @e1 [button] "Sign In"
vibium find label "Email" # → @e1 [input] placeholder="Email"
vibium click @e1 # Click the found element
vibium find placeholder "Search..." # → @e1 [input] placeholder="Search..."
vibium find testid "submit-btn" # → @e1 [button] "Submit"
vibium find alt "Company logo" # → @e1 [img] alt="Company logo"
vibium find title "Close" # → @e1 [button] title="Close"
vibium find xpath "//a[@href='/about']" # → @e1 [a] "About"
Authentication with state persistence
# Log in once and save state
vibium go https://app.example.com/login
vibium fill "input[name=email]" "[email protected]"
vibium fill "input[name=password]" "secret"
vibium click "button[type=submit]"
vibium wait url "/dashboard"
vibium storage -o auth.json
# Restore in a later session (skips login)
vibium storage restore auth.json
vibium go https://app.example.com/dashboard
Extract structured data
vibium go https://example.com
vibium eval "JSON.stringify([...document.querySelectorAll('a')].map(a => ({text: a.textContent.trim(), href: a.href})))"
Check page structure without rendering
vibium go https://example.com && vibium a11y-tree
Remote browser
vibium start ws://remote-host:9515/session
vibium go https://example.com
vibium map
vibium stop
Multi-page workflow
vibium page new https://docs.example.com
vibium text "h1"
vibium page switch 0
Annotated screenshot
vibium screenshot -o annotated.png --annotate
Inspect an element
vibium attr "a" "href"
vibium value "input[name=email]"
vibium is visible ".modal"
Save as PDF
vibium go https://example.com && vibium pdf -o page.pdf
Eval / JavaScript
vibium eval is the escape hatch for any DOM query or mutation the CLI doesn't cover directly.
Simple expressions — use single quotes:
vibium eval 'document.title'
vibium eval 'document.querySelectorAll("li").length'
Complex scripts — use --stdin with a heredoc:
vibium eval --stdin <<'EOF'
const rows = [...document.querySelectorAll('table tbody tr')];
JSON.stringify(rows.map(r => {
const cells = r.querySelectorAll('td');
return { name: cells[0].textContent.trim(), price: cells[1].textContent.trim() };
}));
EOF
JSON output — use --json to get machine-readable output:
vibium eval --json 'JSON.stringify({url: location.href, title: document.title})'
Important: eval returns the expression result. If your script doesn't return a value, you'll get null. Always make sure the last expression evaluates to the data you want.
Timeouts and Waiting
All interaction commands (click, fill, type, etc.) auto-wait for the target element to be actionable. You usually don't need explicit waits.
Use explicit waits when:
- Waiting for navigation:
vibium wait url "/dashboard"— after clicking a link that navigates - Waiting for content:
vibium wait text "Success"— after form submission, wait for confirmation - Waiting for element:
vibium wait ".modal"— wait for a modal to appear - Waiting for page load:
vibium wait load— after navigation to a slow page - Waiting for JS condition:
vibium wait fn "window.appReady === true"— wait for app initialization - Fixed delay (last resort):
vibium sleep 2000— only when no better signal exists (max 30s)
All wait commands accept --timeout <ms> (default varies by command).
Ref Lifecycle
Refs (@e1, @e2) are invalidated when the page changes. Always re-map after:
- Clicking links or buttons that navigate
- Form submissions
- Dynamic content loading (dropdowns, modals)
Global Flags
| Flag | Description |
|---|---|
--headless |
Hide browser window |
--json |
Output as JSON |
-v, --verbose |
Debug logging |
Tips
- All click/type/hover/fill actions auto-wait for the element to be actionable
- All selector arguments also accept
@reffromvibium map - Use
vibium mapbefore interacting to discover interactive elements - Use
vibium map --selectorto reduce noise on large pages - Use
vibium fillto replace a field's value,vibium typeto append to it - Use
vibium find text/find label/find testidfor semantic element lookup (more reliable than CSS selectors) - Use
vibium find rolefor ARIA-role-based lookup - Use
vibium a11y-treeto understand page structure without visual rendering - Use
vibium text "<selector>"to read specific secti
How to use vibe-check on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add vibe-check
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches vibe-check from GitHub repository vibiumdev/vibium and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate vibe-check. Access the skill through slash commands (e.g., /vibe-check) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★69 reviews- ★★★★★Ganesh Mohane· Dec 24, 2024
I recommend vibe-check for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Fatima Ndlovu· Dec 16, 2024
Useful defaults in vibe-check — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amelia Shah· Dec 16, 2024
I recommend vibe-check for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Daniel Bansal· Dec 16, 2024
vibe-check is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zara Khan· Dec 12, 2024
Keeps context tight: vibe-check is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amelia Singh· Dec 8, 2024
We added vibe-check from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Anika Brown· Dec 8, 2024
Useful defaults in vibe-check — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amelia Martinez· Nov 27, 2024
vibe-check fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Fatima Gonzalez· Nov 27, 2024
Registry listing for vibe-check matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Sakshi Patil· Nov 15, 2024
Solid pick for teams standardizing on skills: vibe-check is focused, and the summary matches what you get after install.
showing 1-10 of 69