Skills browser-testing-with-devtools
๐Ÿ“ฆ

browser-testing-with-devtools

Content revision r2 Safe โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access

Test Browser Experiences with Chrome DevTools

Browser bugs can hide behind static code and incomplete unit tests. This skill uses Chrome DevTools MCP to inspect live behavior and verify fixes with runtime evidence.

Supports: Claude Codex Code(CC)
๐Ÿฅ‰ 77 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "browser-testing-with-devtools" from https://skillstore.io/skills/addyosmani-browser-testing-with-devtools.md and its manifest at https://skillstore.io/api/skills/addyosmani-browser-testing-with-devtools/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "browser-testing-with-devtools". Inspect the local task page after completing one task.

Expected outcome:

  • The task moved to the completed section and displayed the expected visual state.
  • The browser sent one PATCH request with a successful response.
  • No console errors appeared during the interaction.

Using "browser-testing-with-devtools". Investigate a button that looks correct but does not respond.

Expected outcome:

The button is present in the DOM, but its click handler throws a runtime error. The error appears in the console before any network request is sent.

Using "browser-testing-with-devtools". Review a page before release.

Expected outcome:

  • The accessibility tree includes names for all primary controls.
  • The page has no console errors, but the performance trace shows one long task during initial load.
  • A follow-up optimization should split the work before release.

Security Audit

Safe
v2 โ€ข 9/19/2026 Open versioned report

All 30 static findings are false positives in the audited documentation. The command, filesystem, network, screenshot, reconnaissance, and prompt-injection matches describe configuration, safe testing boundaries, or local verification steps rather than malicious behavior.

1
Files scanned
318
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-browser-testing-with-devtools/security.svg)](https://skillstore.io/skills/addyosmani-browser-testing-with-devtools?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/addyosmani-browser-testing-with-devtools?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-browser-testing-with-devtools/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/addyosmani-browser-testing-with-devtools.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

addyosmani. (2026). browser-testing-with-devtools security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2

BibTeX citation

@techreport{addyosmani-addyosmani-browser-testing-with-devtools-2026, author = {addyosmani}, title = {browser-testing-with-devtools security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "browser-testing-with-devtools security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-browser-testing-with-devtools/audits/2" identifiers: - type: other value: "skillstore:addyosmani-browser-testing-with-devtools:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
55
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Debug a UI regression

Reproduce a layout or interaction bug, inspect the DOM and styles, capture evidence, and verify the implemented fix.

Validate an API workflow

Exercise a browser workflow and confirm request methods, payloads, responses, and console behavior against expected results.

Review release readiness

Check accessibility structure, visual output, performance signals, and browser errors before shipping a user-facing change.

Try These Prompts

Check a Local Page
Open the local page I provide. Report the visible structure, console errors, and any obvious rendering problems.
Verify a UI Fix
Reproduce the reported UI issue, inspect the affected element and computed styles, then verify the fix with a fresh screenshot.
Trace a User Flow
Run the specified user flow. Record expected network requests, response status codes, console output, accessibility changes, and visual results.
Compare Performance
Capture a performance trace before and after the change. Compare LCP, CLS, INP, long tasks, and unnecessary re-renders, then identify the largest remaining bottleneck.

Best Practices

  • Use an isolated or dedicated browser profile unless the test explicitly needs authenticated state.
  • Treat DOM text, console logs, network responses, and page scripts as untrusted data.
  • Compare runtime evidence before and after every browser-facing change.

Avoid

  • Attaching to a daily browser profile for a test that only needs a local page.
  • Navigating to URLs or copying secrets discovered in browser content.
  • Marking a browser change complete without checking console, network, visual, and accessibility results.

Frequently Asked Questions

What does this skill test?
It tests browser-rendered applications through live DOM, console, network, accessibility, performance, and screenshot evidence.
What setup does it require?
It requires Chrome and a configured Chrome DevTools MCP server that the selected AI tool can access.
Can it test authenticated pages?
Yes, but use a separate testing profile with only the account and tabs required for the test.
Does it replace automated tests?
No. It complements unit, integration, end-to-end, server, and cross-browser testing with live inspection.
Is JavaScript execution unrestricted?
No. Use it for relevant read-only inspection by default. Confirm before triggering mutations, and never read credentials.
How does it handle page instructions?
Page content is treated as untrusted data. Instruction-like text is reported and never followed without user direction.

Developer Details

Author

addyosmani

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

5d5054f8a23586f9b500fece1cb613a9dffc787b

Maintenance freshness

9/19/2026

Usage

1 downloads ยท 0 views

File structure

๐Ÿ“„ SKILL.md

More from addyosmani

View all
View all