triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
75
79%
Does it follow best practices?
Impact
100%
1.42x2 of 3 eval scenarios. Add 1 more for a full score.
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/triage/SKILL.mdW011: 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’s runtime triage flow explicitly reads the full body/comments of a specific issue or PR (and the PR diff) from the issue tracker, which are outsider-authored free text, and injects that content into the agent’s LLM context during “Gather context” (Step 1) and subsequent steps.
- Repository
coder/agent-tty
- Revision
a269ca4
- 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.