browser-debug
Capture browser console, network, and performance logs for debugging. Auto-loads when debugging browser issues, analyzing errors, or investigating page behavior. Provides systematic log capture workflow using Chrome DevTools MCP.
57
71%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./plugins/product-design/skills/browser-debug/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Third-party content exposure detected (high risk: 0.90). The SKILL.md explicitly uses Chrome DevTools to capture console messages and network request/response data from arbitrary webpages (see Step 2 mcp__plugin_product-design_chrome-devtools__list_console_messages and Step 3 mcp__plugin_product-design_chrome-devtools__get_network_request producing network-detail.json) and then instructs the AI agent to "Parse captured logs" and act on findings (Step 5 / Pattern 4 "Allow AI agent to interact with page"), so untrusted third‑party content can be ingested and influence agent decisions.
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.