prioritize-repo-issues
Prioritize open issues in a local GitHub repository workspace by value outcome framing and strategic goal alignment. Classifies backlog items across outcome altitude (Impact/Outcome vs Output vs Activity) and evaluates them against repository strategic goals (P0 Strategic Drivers down to P4 Distractions). Use when planning milestones or sprints, triaging an issue backlog, deciding what work to pull next, or auditing a repository queue for outcome and strategic focus.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./skills/prioritize-repo-issues/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 required workflow reads open GitHub issues from a repository workspace or remote repository via CLI, exposing the agent to outsider-authored issue titles, bodies, and comments.
- Repository
yyeret/ai-impact
- Revision
f9ec7f4
- 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.