How do I install the Dashboard Browser QA skill?

Run npx skillmds@latest add pockethost/dashboard-browser-qa in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dashboard Browser QA safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dashboard Browser QA?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dashboard Browser QA free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dashboard Browser QA?

pockethost (@pockethost) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dashboard Browser QA by pockethost — Agent Skill

Name: Dashboard Browser QA
Author: pockethost

Dashboard Browser QA

QA the PocketHost dashboard in the Cursor IDE browser (cursor-ide-browser MCP). Use when verifying UI changes, testing login flows, checking styling, or when the user asks to open or test the dashboard in the browser.

pockethost 7c88f0f 2.0 KB Updated Sep 17, 2026

File contents

Dashboard browser QA

The Cursor IDE browser works for PocketHost dashboard QA. Use the cursor-ide-browser MCP tools. Do not skip browser verification because you assume automation is unavailable.

Prerequisites

Requirement	Notes
`pnpm dev:dashboard`	Vite on `:5174` (usually already running)
`pnpm dev:cli serve`	Mothership + firewall on 80/443. Required for login and app routes
HTTPS base URL	`https://pockethost.lvh.me` — not `http://localhost:5174` (insecure context, wrong routing)

Credentials

Read .secret/pockethost-io-login at repo root:

Line 1: email
Line 2: password

Do not paste credentials into chat, commits, or rules. Reference the file path only.

Login flow

browser_navigate → https://pockethost.lvh.me/login
browser_lock before interactions (after navigate, or lock first if a tab already exists)
Fill #email and #password. Svelte bind:value needs CDP Runtime.evaluate that sets .value and dispatches input on each field
Click submit, then browser_snapshot to confirm redirect (e.g. /instances)
browser_unlock when done

Verification workflow

browser_snapshot for structure and refs before clicking
browser_take_screenshot after meaningful UI changes
Navigate the task flow the user cares about (not just the edited component in isolation)
Check mobile-ish width if layout is responsive

Lock order: navigate → lock → interact → unlock.

When to use

After dashboard UI/UX changes
When the user reports "hard to use" or confusing flows
Before shipping customer-visible (app)/ route changes
Pair with .cursor/rules/dashboard-ux.mdc for styling expectations

---name: dashboard-browser-qadescription: QA the PocketHost dashboard in the Cursor IDE browser (cursor-ide-browser MCP). Use when verifying UI changes, testing login flows, checking styling, or when the user asks to open or test the dashboard in the browser.---# Dashboard browser QAThe **Cursor IDE browser works** for PocketHost dashboard QA. Use the `cursor-ide-browser` MCP tools. Do not skip browser verification because you assume automation is unavailable.## Prerequisites| Requirement | Notes ||-------------|-------|| `pnpm dev:dashboard` | Vite on `:5174` (usually already running) || `pnpm dev:cli serve` | Mothership + firewall on 80/443. Required for login and app routes || HTTPS base URL | `https://pockethost.lvh.me` — **not** `http://localhost:5174` (insecure context, wrong routing) |## CredentialsRead `.secret/pockethost-io-login` at repo root:- Line 1: email- Line 2: passwordDo not paste credentials into chat, commits, or rules. Reference the file path only.## Login flow1. `browser_navigate` → `https://pockethost.lvh.me/login`2. `browser_lock` before interactions (after navigate, or lock first if a tab already exists)3. Fill `#email` and `#password`. Svelte `bind:value` needs CDP `Runtime.evaluate` that sets `.value` and dispatches `input` on each field4. Click submit, then `browser_snapshot` to confirm redirect (e.g. `/instances`)5. `browser_unlock` when done## Verification workflow1. `browser_snapshot` for structure and refs before clicking2. `browser_take_screenshot` after meaningful UI changes3. Navigate the **task flow** the user cares about (not just the edited component in isolation)4. Check mobile-ish width if layout is responsiveLock order: navigate → lock → interact → unlock.## When to use- After dashboard UI/UX changes- When the user reports "hard to use" or confusing flows- Before shipping customer-visible `(app)/` route changes- Pair with [.cursor/rules/dashboard-ux.mdc](../../rules/dashboard-ux.mdc) for styling expectations

Frequently asked questions