Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From browser-testing
Use this when testing the dashboard with a web client in interactive sessions. Best for testing frontend tools, verifying UI behavior, checking page loads, validating URL routing, or interacting with the browser. Preferred over playwright-testing for interactive work — the browser opens as a visible split pane and results return inline.
npx claudepluginhub amitkot/claude-code-tools --plugin browser-testingHow this skill is triggered — by the user, by Claude, or both
Slash command
/browser-testing:cmux-browserThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Test websites and frontend tools using `cmux browser`.
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Structures git workflow practices for committing, branching, resolving conflicts, and organizing work across parallel streams. Use when making any code change.
Share bugs, ideas, or general feedback.
Test websites and frontend tools using cmux browser.
Run the help command to discover all available commands:
cmux browser --help
Use the URL appropriate for the current context:
http://127.0.0.1:8000 or similar)cmux browser open <url> returns a surface handle (e.g. surface:14) — use it for all subsequent commandse9, e18) come from snapshot --interactive and change after page mutations — always re-snapshot before interactingclick ref=eNN fails with JS errors, fall back to eval "document.querySelector('...').click()"eval with JS instead of fill/type