github-issues
Create, triage, label, assign GitHub issues via gh or REST.
60
71%
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 ./skills/github/github-issues/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
In SKILL.md, the “Viewing Issues” and “Issue Triage Workflow” sections call the GitHub Issues API and then read the issue `body` (outsider-authored text from GitHub issue submissions) into the processing pipeline at runtime via `curl ... issues/... | python ... print(f\"\\n{i['body']}\")` (and implicitly for “Read and categorize” in triage).
- Repository
- NousResearch/hermes-agent
- Commit
2635035
- 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.