team-issue
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
46
48%
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 ./.claude/skills/team-issue/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 loads external, user-authored issue content (e.g., coordinator Phase 1 and roles/explorer/role.md call Bash("ccw issue status <issueId> --json") and coordinator uses `ccw issue list`/GH-<id> detection) and then feeds those issue texts into CLI/agent prompts and pipeline decisions (exploration prompts, solution generation, execution routing), so untrusted third-party issue data can materially influence tool use and actions.
- 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.