Fähigkeiten browser-testing-with-devtools
📦

browser-testing-with-devtools

Inhaltsrevision r2 Sicher ⚙️ Externe Befehle🌐 Netzwerkzugriff📁 Dateisystemzugriff

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.

Unterstützt: Claude Codex Code(CC)
🥉 77 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Testen

„browser-testing-with-devtools“ wird verwendet. Inspect the local task page after completing one task.

Erwartetes Ergebnis:

  • 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.

„browser-testing-with-devtools“ wird verwendet. Investigate a button that looks correct but does not respond.

Erwartetes Ergebnis:

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.

„browser-testing-with-devtools“ wird verwendet. Review a page before release.

Erwartetes Ergebnis:

  • 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.

Sicherheitsaudit

Sicher
v2 • 19.9.2026 Versionsbericht öffnen

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
Gescannte Dateien
318
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex Audit-Verlauf anzeigen →
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

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>

Einbettungskarte

<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>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

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-Zitat

@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

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
83
Spezifikationskonformität

Was Sie erstellen können

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.

Diese Prompts ausprobieren

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.

Bewährte Praktiken

  • 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.

Vermeiden

  • 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.

Häufig gestellte Fragen

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.

Entwicklerdetails

Lizenz

MIT

Skillstore-Revision

r2

Versionshinweis

Der Autor hat keine Version angegeben.

Ref.

5d5054f8a23586f9b500fece1cb613a9dffc787b

Aktualität der Wartung

19.9.2026

Nutzung

1 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md

Mehr von addyosmani

Alle anzeigen
Alle anzeigen