team-frontend-debug
Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".
58
67%
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 ./.codex/skills/team-frontend-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
The skill explicitly navigates to and ingests content from arbitrary target/base URLs (e.g., REPRODUCE-001 and roles/reproducer/role.md use mcp__chrome-devtools__navigate_page, take_snapshot, list_console_messages and specs/debug-tools.md documents these tools), treating page DOM, console messages and network responses as required evidence that the analyzer/fixer/verifier must read and act on—so untrusted third-party web content can materially influence decisions and tool use.
- Repository
- catlog22/Claude-Code-Workflow
- Commit
07491b0
- 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.