gh-issues
Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]
79
Quality
72%
Does it follow best practices?
Impact
100%
2.00xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/gh-issues/SKILL.mdSecurity
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
W007: Insecure credential handling detected in skill instructions
What this means
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Why it was flagged
Insecure credential handling detected (high risk: 1.00). The prompt instructs agents to read GH_TOKEN from config/env and embed it in curl headers and git remote URLs (and even echo the token prefix), which requires the LLM to handle or print secret values verbatim, creating a high exfiltration risk.
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 skill explicitly fetches and parses user-generated GitHub content (issues, issue bodies, PR bodies, review comments and inline comments) via the GitHub REST API in Phase 2 (Fetch Issues) and Phase 6 (PR Review Handler) and then reads/acts on that content (sub-agents decide whether to implement fixes, what code to change, and what actions to take), which allows untrusted third-party text to influence tool use and agent behavior.
- Repository
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.