sg-browser

Open a URL in a real browser and verify one observable non-auth objective.

A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.

Browse skills on GitHub Back to the hub

Problem

What problem this solves

ShipGlows had auth debugging, manual QA, and production verification skills, but no small general-purpose browser evidence entrypoint for non-auth page checks.

Outcome

What changes when it works

You get a concise browser report with target, runtime, objective, observed state, verdict, evidence, limits, and the right next ShipGlows command.

Why It Matters

What this changes for a solo founder

This skill matters when you need to know what the browser actually sees without opening a full bug dossier or stretching an auth-specialized workflow.

When to use it

When you need to verify that a public page, preview, or production URL displays an expected state
When a visual, console, network, screenshot, or accessibility snapshot check is enough
When a browser finding should route to sg-fix, sg-test, sg-prod, sg-auth-debug, or sg-verify

What you give it

A URL, route, deployment surface, or local page
One observable objective, such as text appearing, layout rendering, or a network status
Optional viewport or screenshot preference

What you get back

A real-browser observation
A narrow pass, fail, partial, blocked, or routed verdict
Sanitized console or network summaries when relevant
Screenshot or snapshot evidence when useful
Clear limits and the next ShipGlows command

Typical examples

/sg-browser https://example.com verify Example Domain is visible
/sg-browser local homepage check that the pricing CTA renders
/sg-browser preview URL inspect console errors on /dashboard
/sg-browser production page verify the docs link is visible

Limits

It is read-only by default and will not click through destructive or production-mutating actions without explicit approval
Auth, OAuth, session, callback, cookie, tenant, and protected-route issues belong in sg-auth-debug
Full manual user-flow QA and durable test logs belong in sg-test
Deployment URL discovery and runtime logs belong in sg-prod

Related Skills

See the rest of the loop around this move.

Build & Fix

sg-auth-debug

Debug a broken auth flow in a real browser before you start guessing from static code alone.

A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.

Open skill page

Build & Fix

sg-test

Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.

A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.

Open skill page

Operate & Ship

sg-prod

Check whether production is actually healthy after a push instead of assuming the deploy tells the truth.

A production verification skill for deployment status, logs, and live health checks after release.

Open skill page

Build & Fix

sg-fix

Triage a bug fast, decide whether it is safe to patch now, and route it correctly.

The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.

Open skill page

Audit & Improve

sg-verify

Check whether the work really satisfies the user story, not just whether the code compiles.

A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.

Open skill page

Go Deeper

This public page explains the move. The repository explains the execution contract.

Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.

Documentation Overview Open skills on GitHub Return to the skills hub