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]
72
61%
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.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively communicates specific capabilities around GitHub issue management and automated PR workflows, giving it a clear niche. However, it lacks an explicit 'Use when...' clause, and the heavy CLI flag documentation takes up space that could be used for natural trigger terms. The description reads more like a CLI help page than a skill selection guide.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to automatically fix GitHub issues, create pull requests from issues, or monitor and respond to PR review feedback.'
Replace or supplement the verbose CLI flag list with natural language trigger terms like 'bug fixes', 'pull requests', 'code review comments', 'automated issue resolution', 'GitHub automation'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: fetch GitHub issues, spawn sub-agents to implement fixes, open PRs, monitor PR review comments, and address review comments. These are clear, actionable capabilities. | 3 / 3 |
Completeness | The 'what' is well covered (fetch issues, implement fixes, open PRs, monitor reviews). However, there is no explicit 'Use when...' clause or equivalent trigger guidance — the 'Usage:' line describes CLI syntax, not when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains good keywords like 'GitHub issues', 'PRs', 'PR review comments', 'fixes', but the description is heavily dominated by CLI flag documentation rather than natural language terms users would say. Missing natural phrases like 'bug fixes', 'pull requests', 'code review'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: automated GitHub issue triage, fix implementation via sub-agents, and PR lifecycle management. The specific command '/gh-issues' and detailed flags make it clearly distinguishable from other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is exceptionally thorough and actionable with excellent workflow clarity, validation checkpoints, and concrete executable commands throughout all phases. However, it is severely over-long for a single SKILL.md file — the monolithic structure with repeated token resolution blocks, massive inline sub-agent prompts, and no progressive disclosure makes it extremely token-inefficient. The content would benefit enormously from being split into a main overview with referenced sub-files for sub-agent templates, claim tracking logic, and phase-specific details.
Suggestions
Extract the two large sub-agent prompt templates (fix agent and review handler) into separate referenced files (e.g., TEMPLATES/fix-agent.md and TEMPLATES/review-handler.md) to dramatically reduce the main file size.
Consolidate the token resolution logic (repeated 4+ times across main skill and sub-agent prompts) into a single referenced script or shared section.
Remove explanations of basic concepts Claude already knows (e.g., HTTPS vs SSH URL format parsing, how to extract owner/repo from a git remote URL) and replace with concise one-liners.
Split Phase 4 (pre-flight checks with 7 sub-steps) and Phase 6 (review handler with 6 sub-steps) into separate referenced files, keeping only summaries in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Massive amounts of inline detail that could be split into referenced files. The sub-agent prompt templates are enormous and repeated (token resolution appears 4+ times). Much content explains things Claude already knows (how to parse JSON, how git remotes work, HTTPS vs SSH URL formats). The claim-based tracking, cursor file logic, and embedded review parsing are all inlined when they could be separate references. | 1 / 3 |
Actionability | Highly actionable with concrete, executable curl commands, git commands, and specific API endpoints. Every step includes copy-paste ready code with proper headers, URL patterns, and error handling. The sub-agent prompts are fully specified with real commands rather than pseudocode. | 3 / 3 |
Workflow Clarity | Excellent multi-phase workflow with clear sequencing (6 phases), explicit validation checkpoints (token verification, remote access checks, existing PR detection, claim-based dedup, dirty tree warnings), and error recovery paths (retry logic in tests, timeout handling, watch mode loops). Feedback loops are well-defined throughout. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files or external references. The entire skill is one massive document. Sub-agent prompt templates (which are substantial) are inlined rather than referenced. The review handler logic, claim tracking, and cursor management could all be separate files. No bundle files are provided to support this content. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
63%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 7 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (866 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 7 / 11 Passed | |
- Repository
- trpc-group/trpc-agent-go
- Commit
9f4b734
- Reviewed
Table of Contents
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.