implement-issue
Use when given a GitHub issue number and base branch to implement end-to-end
69
55%
Does it follow best practices?
Impact
93%
3.20xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/implement-issue/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
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.80). The orchestrator is explicitly invoked with a GitHub issue number and the workflow's setup/research/evaluate/plan and implement stages indicate the agents will fetch and read that GitHub issue (user-generated public content) and use it to drive planning and actions, which exposes the agent to untrusted third‑party content.
- Repository
- aaddrick/claude-desktop-debian
- Commit
814cd52
- 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.