New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verifying In Browser

by spencerpauly in spencerpauly/awesome-cursor-skills

After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health.

CC0-1.0Auto-check passed

Install Verifying In Browser

skills CLI
$ npx skills add spencerpauly/awesome-cursor-skills --skill verifying-in-browser -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install spencerpauly/awesome-cursor-skills verifying-in-browser --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/spencerpauly/awesome-cursor-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/verifying-in-browser .claude/skills/verifying-in-browser && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
verifying-in-browser
GitHub stars
844
Token cost
~627 tokens
SKILL.md length
298 words
Files
1
Skills in repo
60
Repo updated
First seen
Licence
CC0-1.0

At a glance

After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health.

  • Works in 6 steps: Start the dev server in the background —… → Open in the side browser — launch the… → Quick health check — run these three… → …
  • SKILL.md covers Steps, When to Use This and Notes
  • Calls npm

What it does

Verifying In Browser is an agent skill from spencerpauly/awesome-cursor-skills. After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.

Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A curated list of awesome skills for Cursor. The licence is CC0-1.0.

Example prompts

  • “/verifying-in-browser”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Start the dev server in the background — check if one is already running by listing terminals. If not
  2. Open in the side browser — launch the app beside your code
  3. Quick health check — run these three checks
  4. Navigate to the changed page — if your changes are on a specific route, navigate there and repeat the checks.
  5. Test interactions — if you changed a form, button, or interactive element
  6. Report the verdict — tell the user

What it can do on your machine

Read from SKILL.md and the folder at commit 99cd265. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verifying In Browser loads about 627 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 298 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~60
When it runs · the whole SKILL.md, loaded when a task matches
~627

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from spencerpauly/awesome-cursor-skills at commit 99cd265, republished under its CC0-1.0 licence (© spencerpauly). 298 words, ~627 tokens.

Download SKILL.mdSave it as .claude/skills/verifying-in-browser/SKILL.md (or your agent's skills folder).
name
verifying-in-browser
description
After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Use proactively after any UI or API change.

Verify in Browser

Use this skill proactively after making code changes to verify the app actually works. Don't just trust that the code is correct — launch it and check.

Steps

  1. Start the dev server in the background — check if one is already running by listing terminals. If not:

    bash
    npm run dev

    Set block_until_ms: 0 to run it in the background. Then poll until you see the "ready" message with the localhost URL.

  2. Open in the side browser — launch the app beside your code:

    Tool: browser_navigate
Arguments: { "url": "http://localhost:3000", "position": "side", "take_screenshot_afterwards": true }

  3. Quick health check — run these three checks:

    Console errors:

    Tool: browser_console_messages

    Flag any errors. Warnings about deprecations can be noted but aren't blockers.

    Network failures:

    Tool: browser_network_requests

    Flag any 4xx/5xx responses, failed fetches, or CORS errors.

    Visual check: Review the screenshot. Does the page render? Is the layout correct? Are there any blank screens or loading spinners that never resolve?

  4. Navigate to the changed page — if your changes are on a specific route, navigate there and repeat the checks.

  5. Test interactions — if you changed a form, button, or interactive element:

    • Take a browser_snapshot to get element refs
    • Click, fill, or hover on the changed elements
    • Take another screenshot to verify the result

  6. Report the verdict — tell the user:

    • "Verified in browser — page renders correctly, no console errors, all network requests healthy."
    • Or: "Found issues: [list of problems]"

When to Use This

  • After changing any React component, CSS, or layout code
  • After modifying API routes or data fetching
  • After updating environment variables or configuration
  • After installing or removing dependencies
  • Before committing — as a final sanity check

Notes

  • Use position: "side" to see code and browser at the same time.
  • If the dev server is already running, skip step 1 and go straight to navigating.
  • For SSR apps, check both the initial server-rendered HTML and the client-hydrated state.

© spencerpauly, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/verifying-in-browser of spencerpauly/awesome-cursor-skills.

Open the folder on GitHubat commit 99cd265

Compare with similar skills

Verifying In Browser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verifying In Browser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verifying In Browser this skillspencerpauly/awesome-cursor-skills844—~627Automated safety check: PassCC0-1.0
Verifyasgeirtj/system_prompts_leaks69k—~3kAutomated safety check: PassCC0-1.0
Verify Thiscursor/plugins11k2 repos~693Automated safety check: PassNone
Verify Releaseopenclaw/openclaw392k—~2.4kAutomated safety check: PassMIT
Verifycodewhale-hq/Codewhale41k—~156Automated safety check: PassMIT
Verify Before CompletionYeachan-Heo/oh-my-claudecode40k—~277Automated safety check: PassMIT

Similar skills

  • Verify

    asgeirtj/system_prompts_leaks

    Verify that a code change actually does what it's supposed to by exercising it end-to-end and observing behavior — drive the affected flow, not just tests or typecheck.

    69k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

  • Verify This

    cursor/plugins

    Official

    Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED, NOT VERIFIED, or INCONCLUSIVE.

    11k GitHub starsUsed in 2 repos~693 tokens
    Auto-check passed

  • Verify Release

    openclaw/openclaw

    Verify regular or extended-stable OpenClaw releases against the exact publication surfaces, workflow identities, package provenance, smoke tests, and live Gateway behavior expected for that release…

    392k GitHub stars~2.4k tokensUpdated today
    Testing & QAAuto-check passed

  • Verify

    codewhale-hq/Codewhale

    Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.

    41k GitHub stars~156 tokensUpdated today
    Testing & QAAuto-check passed

  • Verify Before Completion

    Yeachan-Heo/oh-my-claudecode

    Has the agent prove that a feature, fix or refactor works, using existing tests first, then narrow commands and manual checks, and report only what was actually verified.

    40k GitHub stars~277 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Ruview Verify

    ruvnet/RuView

    Verify a RuView build — full Rust workspace tests, the deterministic Python pipeline proof (SHA-256 Trust Kill Switch), firmware hash manifest, and the ADR-028 witness bundle with one-command…

    97k GitHub stars~1k tokensUpdated today
    DevelopmentAuto-check: notes

More from spencerpauly/awesome-cursor-skills

All 60 skills in this repo

  • Generating Images

    spencerpauly/awesome-cursor-skills

    Generate or edit images using the OpenAI Image API (gpt-image-2).

    844 GitHub stars~3.7k tokensUpdated 2 mo ago
    Auto-check: notes

  • Babysitting PR

    spencerpauly/awesome-cursor-skills

    Monitor a pull request for CI failures, review comments, and merge conflicts — then fix them automatically.

    844 GitHub stars~930 tokensUpdated 2 mo ago
    Auto-check passed

  • Best Of N Solving

    spencerpauly/awesome-cursor-skills

    Solve a hard problem by trying multiple approaches in parallel using isolated git worktrees.

    844 GitHub stars~698 tokensUpdated 2 mo ago
    Auto-check passed

  • Grinding Until Pass

    spencerpauly/awesome-cursor-skills

    Keep iterating on code changes until the tests pass, the build succeeds, or linting is clean.

    844 GitHub stars~796 tokensUpdated 2 mo ago
    Auto-check passed

  • Parallel CI Triage

    spencerpauly/awesome-cursor-skills

    When GitHub Actions fails, fetch failing job logs and assign each failing job to a separate subagent that fixes its slice of the problem in parallel.

    844 GitHub stars~793 tokensUpdated 2 mo ago
    Auto-check passed

  • Parallel Exploring

    spencerpauly/awesome-cursor-skills

    Explore a large codebase in parallel by launching multiple explore subagents that each investigate a different area simultaneously.

    844 GitHub stars~787 tokensUpdated 2 mo ago
    Auto-check: notes

Questions about Verifying In Browser

What does Verifying In Browser do?

After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health. Verifying In Browser is an agent skill from spencerpauly/awesome-cursor-skills. After making code changes, start the dev server, open the app in Cursor's built-in browser, and verify everything works — check rendering, console errors, and network health.

How do I install Verifying In Browser in Claude Code?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill verifying-in-browser -a claude-code`. Or copy the skill folder (resources/verifying-in-browser in spencerpauly/awesome-cursor-skills) into .claude/skills/verifying-in-browser in your project. Claude Code loads it when a task matches its description.

How do I install Verifying In Browser in Codex?

Run `npx skills add spencerpauly/awesome-cursor-skills --skill verifying-in-browser -a codex`. Or copy the skill folder (resources/verifying-in-browser in spencerpauly/awesome-cursor-skills) into .agents/skills/verifying-in-browser in your project. Codex loads it when a task matches its description.

Can I use Verifying In Browser in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spencerpauly/awesome-cursor-skills --skill verifying-in-browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verifying-in-browser, .gemini/skills/verifying-in-browser, .github/skills/verifying-in-browser and .opencode/skills/verifying-in-browser in your project.

What does Verifying In Browser need to run?

Going by SKILL.md and its folder, Verifying In Browser needs the command-line tools its instructions call (npm).

Does Verifying In Browser access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Verifying In Browser safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Verifying In Browser use?

Verifying In Browser is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verifying In Browser use?

About 627 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verifying In Browser?

Skills that share tags, products or a category with Verifying In Browser: Verify (asgeirtj/system_prompts_leaks, 69k stars), Verify This (cursor/plugins, 11k stars), Verify Release (openclaw/openclaw, 392k stars) and Verify (codewhale-hq/Codewhale, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verifying In Browser?

spencerpauly (a GitHub user) maintains it in spencerpauly/awesome-cursor-skills, which has 844 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on August 2, 2026.

Source: spencerpauly/awesome-cursor-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.