Compétences browser-devtools

📦

browser-devtools

Name: browser-devtools
Author: shreyam1008

Révision du contenu r1 Sûr ⚙️ Commandes externes📁 Accès au système de fichiers🌐 Accès réseau

Debug Chrome Web Apps with DevTools

Chrome web problems often require evidence from several browser surfaces, which makes diagnosis slow and inconsistent. This skill provides a focused workflow for reproducing issues, collecting bounded evidence, and verifying fixes with agent-browser and Chrome DevTools.

Prend en charge: Claude Codex Code(CC)

📊 76 Adéquat

Maintain this Skill? Claim it 📊 76 Adéquat

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent

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

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Détail Markdown GET /skills/shreyam1008-browser-devtools.md manifest signé GET /api/skills/shreyam1008-browser-devtools/manifest lockfile signé GET /api/skills/shreyam1008-browser-devtools/lockfile

Tester

Utilisation de « browser-devtools ». The checkout button appears to do nothing after a recent frontend change.

Résultat attendu:

Evidence: the click reaches the page, but the request is blocked during preflight. Cause: the new origin is missing the required CORS response. Verification: the same authorized test action succeeds after the server policy is corrected.

Utilisation de « browser-devtools ». A dashboard becomes slow after switching between two filters.

Résultat attendu:

Trace result: repeated rendering dominates the measured interaction.
Relevant path: the filter change remounts the results branch and repeats expensive work.
Next check: compare an equivalent interaction after stabilizing the branch identity.

Utilisation de « browser-devtools ». A React panel rerenders whenever an unrelated control changes.

Résultat attendu:

The focused component branch receives a changed object identity from its parent. The profile shows extra commits, but it does not establish a production-wide performance impact.

Audit de sécurité

Sûr

v1 • 02/10/2026 Ouvrir le rapport versionné

All 15 static findings are false positives caused by documentation examples, safety warnings, or legitimate browser diagnostics. The reviewed files describe scoped, authorized investigation and include safeguards for secrets, profiles, request replay, and persistent browser state.

Fichiers analysés

281

Lignes analysées

Éléments à examiner

Faux positifs ignorés

Facteurs de risque

⚙️ Commandes externes (4)

references/backends.md:15 references/backends.md:17 references/backends.md:31 SKILL.md:8

📁 Accès au système de fichiers (2)

references/backends.md:7 references/backends.md:7

🌐 Accès réseau (1)

SKILL.md:21

Le dernier audit statique et sémantique terminé n’a détecté aucun constat de sécurité confirmé. Cela ne prouve pas que le skill est sans effets secondaires.

Audité par: codex

Partager et citer ce rapport

Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.

Ouvrir le rapport versionné

Copier le lien du rapport

https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

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

Badge HTML

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

Carte intégrable

<iframe src="https://skillstore.io/embed/skills/shreyam1008-browser-devtools.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Citations académiques (APA · BibTeX · CFF)

Citation APA

shreyam1008. (2026). browser-devtools security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1

Citation BibTeX

@techreport{shreyam1008-shreyam1008-browser-devtools-2026,
  author = {shreyam1008},
  title = {browser-devtools security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1},
  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-devtools security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "shreyam1008"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1"
identifiers:
  - type: other
    value: "skillstore:shreyam1008-browser-devtools:audit:1"
    description: "Skillstore immutable audit report identifier"

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen

Architecture

Maintenabilité

Contenu

Communauté

Conformité aux spécifications

Ce que vous pouvez créer

Diagnose a failed API request

Capture the failing transaction, inspect redirects and browser policies, trace the initiator, and verify the repair under comparable conditions.

Find a slow interaction

Record a focused interaction, separate network, rendering, and JavaScript costs, then identify the dominant measured path.

Investigate a React rendering issue

Inspect the relevant component branch and profile repeated commits without dumping unrelated application state.

Essayez ces prompts

Start a browser diagnosis

Investigate this Chrome issue: [describe the symptom]. Use the intended test URL, reproduce it once, and report the observed evidence, likely cause, and next check.

Trace a failed request

Analyze the failed request for [action]. Capture the request and response details, redirect or preflight behavior, initiating source, and resulting UI state. Redact secrets.

Profile a slow interaction

Profile [interaction] in an isolated session. Record a short comparable trace, separate network, scripting, rendering, and paint costs, and identify the dominant measured path.

Validate a React performance hypothesis

Investigate whether [component or interaction] causes repeated expensive renders. Inspect the smallest relevant React branch, profile the same interaction before and after one controlled change, and report limits.

Bonnes pratiques

Start collection before reproduction and keep the investigation scoped to the failing origin and action.
Redact credentials, cookies, signed URLs, and sensitive payloads before sharing traces, screenshots, HARs, or heap data.
Change one condition at a time, preserve normal browser behavior, and repeat the same scenario after a fix.

Éviter

Do not replay requests, clear storage, change security settings, or mutate application state without authorization.
Do not dump whole globals, session objects, component trees, HAR files, or heap snapshots when bounded evidence is enough.
Do not treat one trace, a successful terminal request, or a mocked response as proof of production behavior.