browser-devtools
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.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
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.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «browser-devtools». The checkout button appears to do nothing after a recent frontend change.
Ожидаемый результат:
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.
Использование «browser-devtools». A dashboard becomes slow after switching between two filters.
Ожидаемый результат:
- 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.
Использование «browser-devtools». A React panel rerenders whenever an unrelated control changes.
Ожидаемый результат:
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.
Аудит безопасности
Безопасно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.
Факторы риска
⚙️ Внешние команды (4)
📁 Доступ к файловой системе (2)
🌐 Доступ к сети (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/shreyam1008-browser-devtools?utm_source=security_passport_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>Встраиваемая карточка
<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>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
shreyam1008. (2026). browser-devtools security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/shreyam1008-browser-devtools/audits/1Цитата 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"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
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.
Попробуйте эти промпты
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.
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 [interaction] in an isolated session. Record a short comparable trace, separate network, scripting, rendering, and paint costs, and identify the dominant measured path.
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.
Лучшие практики
- 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.
Избегать
- 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.
Часто задаваемые вопросы
What browser does this skill target?
Can it debug network and storage issues?
Can it measure real-world web performance?
Does it support React applications?
Is it safe to use on a logged-in browser?
Does it make code changes automatically?
Сведения для разработчиков
Автор
shreyam1008Лицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
bbec03cf10354f3aaccd6dd24eda4ac9ceeceac5
Актуальность поддержки
02.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов