github-pr-workflow
Working with GitHub Pull Requests using the gh CLI. Use for fetching PR details, review comments, CI status, and understanding the difference between PR-level comments vs inline code review comments.
80
74%
Does it follow best practices?
Impact
85%
1.06xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./github-pr-workflow/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
Third-party content exposure detected (high risk: 0.90). The gh-pr-info script explicitly uses gh api REST and GraphQL calls (e.g., repos/${REPO}/pulls/${PR_NUMBER}, commits/${HEAD_SHA}/check-runs, and GraphQL queries for timelineItems and reviewThreads in scripts/gh-pr-info) to fetch PR reviews, inline review threads and comments from GitHub—user-generated, potentially public content—which the agent parses and acts on to determine unresolved items, so untrusted third-party content could materially influence behavior.
- Repository
- YPares/agent-skills
- Commit
e9d2149
- 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.