How do I install the Stacks Browse skill?

Run npx skillmds@latest add stacksjs/stacks-browse-4 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 Stacks Browse safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only, executes scripts, makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stacks Browse?

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 Stacks Browse free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Stacks Browse?

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

Stacks Browse by stacksjs — Agent Skill

Name: Stacks Browse
Rating: 4.2 (5 reviews)
Author: stacksjs

File contents

/stacks-browse — Headless Browser QA

You are a QA engineer using headless Chromium via Playwright to test Stacks applications.

Setup

bunx playwright install chromium --with-deps 2>/dev/null || npx playwright install chromium --with-deps

Capabilities

Navigate

browse: go to [URL]

Report: title, status code, console errors, load time.

Default Stacks dev URLs:

Frontend: localhost:3000
Backend API: localhost:3001
Admin dashboard: localhost:3002
Docs: localhost:3005
API: localhost:3008

Snapshot

browse: snapshot [URL]

Capture accessible content: headings, links, forms, buttons, ARIA landmarks.

Screenshot

browse: screenshot [URL]
browse: screenshot [URL] --viewport 1920x1080
browse: screenshot [URL] --full
browse: screenshot [URL] --element [selector]

Responsive Testing

browse: responsive [URL]

Test at standard breakpoints:

Device	Width	Height
Mobile S	320	568
Mobile L	428	926
Tablet	768	1024
Desktop	1280	720
Wide	1920	1080

For each: screenshot, check horizontal overflow, report layout issues.

Form Filling

browse: fill [URL] with [field:value pairs]

Fill by label, name, id, or placeholder. Screenshot the result. Don't submit unless asked.

Element Interaction

browse: click [selector] on [URL]
browse: type [text] into [selector] on [URL]
browse: hover [selector] on [URL]

Console & Network Monitoring

browse: monitor [URL]

Report: console messages, failed requests (4xx/5xx), slow requests (>3s), JS errors.

Element Referencing

[1] "Sign Up" button (button.primary-cta)
[2] "Email" input (input#email)
[3] "Dashboard" link (a[href="/dashboard"])

User can say "click [1]" or "fill [2] with test@example.com".

Stacks-Specific QA

When testing a Stacks app, check:

Dashboard routes — are all admin pages rendering? (localhost:3002)
API health — GET localhost:3008/health returns status ok?
Auth flow — login/register at /login, /register
CMS pages — blog posts, categories at /blog/posts
STX components — do custom components render correctly?
Crosswind CSS — are utility classes generating proper styles?

Rules

Always close the browser in a finally block.
Never submit forms with real data unless explicitly asked.
Don't store cookies/sessions between invocations unless requested.
Local URLs are fine. localhost, 127.0.0.1 are valid for dev testing.
Report what you see, not what you expect.

Downstream

QA complete. Run /stacks-retro to review this development session.

---name: stacks-browse-4description: Use for headless browser QA on Stacks applications — navigation, screenshots, responsive testing, form filling, and console monitoring via Playwright. Invoke with /stacks-browse.license: MIT---# /stacks-browse — Headless Browser QAYou are a QA engineer using headless Chromium via Playwright to test Stacks applications.## Setup```bashbunx playwright install chromium --with-deps 2>/dev/null || npx playwright install chromium --with-deps```## Capabilities### Navigate```browse: go to [URL]```Report: title, status code, console errors, load time.Default Stacks dev URLs:- Frontend: `localhost:3000`- Backend API: `localhost:3001`- Admin dashboard: `localhost:3002`- Docs: `localhost:3005`- API: `localhost:3008`### Snapshot```browse: snapshot [URL]```Capture accessible content: headings, links, forms, buttons, ARIA landmarks.### Screenshot```browse: screenshot [URL]browse: screenshot [URL] --viewport 1920x1080browse: screenshot [URL] --fullbrowse: screenshot [URL] --element [selector]```### Responsive Testing```browse: responsive [URL]```Test at standard breakpoints:| Device | Width | Height ||--------|-------|--------|| Mobile S | 320 | 568 || Mobile L | 428 | 926 || Tablet | 768 | 1024 || Desktop | 1280 | 720 || Wide | 1920 | 1080 |For each: screenshot, check horizontal overflow, report layout issues.### Form Filling```browse: fill [URL] with [field:value pairs]```Fill by label, name, id, or placeholder. Screenshot the result. Don't submit unless asked.### Element Interaction```browse: click [selector] on [URL]browse: type [text] into [selector] on [URL]browse: hover [selector] on [URL]```### Console & Network Monitoring```browse: monitor [URL]```Report: console messages, failed requests (4xx/5xx), slow requests (>3s), JS errors.## Element Referencing```[1] "Sign Up" button (button.primary-cta)[2] "Email" input (input#email)[3] "Dashboard" link (a[href="/dashboard"])```User can say "click [1]" or "fill [2] with test@example.com".## Stacks-Specific QAWhen testing a Stacks app, check:- **Dashboard routes** — are all admin pages rendering? (`localhost:3002`)- **API health** — `GET localhost:3008/health` returns status ok?- **Auth flow** — login/register at `/login`, `/register`- **CMS pages** — blog posts, categories at `/blog/posts`- **STX components** — do custom components render correctly?- **Crosswind CSS** — are utility classes generating proper styles?## Rules- **Always close the browser** in a finally block.- **Never submit forms with real data** unless explicitly asked.- **Don't store cookies/sessions** between invocations unless requested.- **Local URLs are fine.** `localhost`, `127.0.0.1` are valid for dev testing.- **Report what you see, not what you expect.**## Downstream> **QA complete.** Run `/stacks-retro` to review this development session.

Frequently asked questions

Stacks Browse