AgentStack
SKILL verified Apache-2.0 Self-run

Browser Testing With Devtools

skill-mmccalla-coding-agent-skill-library-browser-testing-with-devtools · by mmccalla

Use when verifying browser-based behaviour with Chrome DevTools, including DOM state, console output, network activity and performance evidence.

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-mmccalla-coding-agent-skill-library-browser-testing-with-devtools

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Browser Testing With Devtools? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Browser Testing With DevTools

When to use

Use this skill when a change affects a browser-rendered interface and you need runtime evidence from the browser rather than static code inspection alone.

Objective

Verify user-facing behaviour with DevTools evidence so frontend or browser issues are reproduced, localized and confirmed with the actual runtime state.

Procedure

  1. Reproduce the issue or feature in the browser.
  2. Inspect the DOM, console and network activity.
  3. Check state changes, errors and timing at the point of failure.
  4. Use performance or network traces when latency or rendering is relevant.
  5. Confirm the fix with the same browser path.

Rules

  • Do not rely on screenshots alone when runtime evidence is available.
  • Do not treat a successful page load as proof of correct behaviour.
  • Do not skip console or network checks when a browser bug is involved.
  • Do not use performance traces without first reproducing the user-visible problem.

References

Verification

  • [ ] Browser flows exercised listed.
  • [ ] DOM, console, network or performance evidence captured.
  • [ ] Defects or regressions reported with reproduction steps.
  • [ ] Residual untested browser risks stated.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.