vibe-check

vibiumdev/vibium · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/vibiumdev/vibium --skill vibe-check
0 commentsdiscussion
summary

The vibium CLI automates Chrome via the command line. The browser auto-launches on first use (daemon mode keeps it running between commands).

skill.md

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:

  1. Navigate: vibium go <url>
  2. Map: vibium map (get element refs like @e1, @e2)
  3. Interact: Use refs to click, fill, select — e.g. vibium click @e1
  4. 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:

  1. Try vibium directly (works if globally installed via npm install -g vibium)
  2. Fall back to ./clicker/bin/vibium (dev environment, in project root)
  3. 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 subtree
  • vibium diff map — compare current vs last map (see what changed)

Navigation

  • vibium go <url> — go to a page
  • vibium back — go back in history
  • vibium forward — go forward in history
  • vibium reload — reload the current page
  • vibium url — print current URL
  • vibium title — print page title

Reading Content

  • vibium text — get all page text
  • vibium text "<selector>" — get text of a specific element
  • vibium html — get page HTML (use --outer for outerHTML)
  • vibium find "<selector>" — find element, return @e1 ref (clickable with vibium click @e1)
  • vibium find "<selector>" --all — find all matching elements → @e1, @e2, ... (--limit N)
  • vibium find text "Sign In" — find element by text content → @e1
  • vibium find label "Email" — find input by label → @e1
  • vibium find placeholder "Search" — find by placeholder → @e1
  • vibium find testid "submit-btn" — find by data-testid → @e1
  • vibium find xpath "//div[@class]" — find by XPath → @e1
  • vibium find alt "Logo" — find by alt attribute → @e1
  • vibium find title "Settings" — find by title attribute → @e1
  • vibium find role <role> — find element by ARIA role → @e1 (--name for accessible name filter)
  • vibium eval "<js>" — run JavaScript and print result (--stdin to read from stdin)
  • vibium count "<selector>" — count matching elements
  • vibium screenshot -o file.png — capture screenshot (--full-page, --annotate)
  • vibium a11y-tree — accessibility tree (--everything for all nodes)

Interaction

  • vibium click "<selector>" — click an element (also accepts @ref from map)
  • vibium dblclick "<selector>" — double-click an element
  • vibium 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 element
  • vibium focus "<selector>" — focus an element
  • vibium hover "<selector>" — hover over an element
  • vibium 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 option
  • vibium 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 coordinates
  • vibium 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 value
  • vibium attr "<selector>" "<attribute>" — get HTML attribute value
  • vibium 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 dimensions
  • vibium viewport <width> <height> — set viewport size (--dpr for device pixel ratio)
  • vibium window — get OS browser window dimensions and state
  • vibium 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 (--stdin to read from stdin)

Frames

  • vibium frames — list all iframes on the page
  • vibium 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 cookies
  • vibium cookies <name> <value> — set a cookie
  • vibium 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 pages
  • vibium page new [url] — open new page
  • vibium page switch <index|url> — switch page
  • vibium page close [index] — close page

Debug

  • vibium highlight "<selector>" — highlight element visually (3 seconds)

Session

  • vibium start — start a local browser session
  • vibium start <url> — start connected to a remote browser
  • vibium stop — stop the browser session
  • vibium daemon start — start background browser
  • vibium daemon status — check if running
  • vibium 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 @ref from vibium map
  • Use vibium map before interacting to discover interactive elements
  • Use vibium map --selector to reduce noise on large pages
  • Use vibium fill to replace a field's value, vibium type to append to it
  • Use vibium find text / find label / find testid for semantic element lookup (more reliable than CSS selectors)
  • Use vibium find role for ARIA-role-based lookup
  • Use vibium a11y-tree to understand page structure without visual rendering
  • Use vibium text "<selector>" to read specific secti
how to use vibe-check

How to use vibe-check on Cursor

AI-first code editor with Composer

1

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
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/vibiumdev/vibium --skill vibe-check

The skills CLI fetches vibe-check from GitHub repository vibiumdev/vibium and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/vibe-check

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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.669 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

1 / 7