CtrlK
BlogDocsLog inGet started
Tessl Logo

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]

65

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with a well-sequenced, validation-rich workflow, but it pays for that in length and repetition, and it keeps everything in one large file rather than splitting detailed material into references.

Suggestions

Move the two large sub-agent prompt templates (Phase 5 fix agent, Phase 6 review agent) into separate reference files and point to them, reducing SKILL.md to an overview.

Factor the repeated token-resolution snippet into a single shared block referenced once instead of duplicated across phases.

Trim explanations of basic git/API behavior that Claude already knows, keeping only the skill-specific command details.

DimensionReasoningScore

Conciseness

The body is mostly efficient and action-oriented, but token-resolution logic is repeated three times (Phase 2, fix sub-agent step 0, review sub-agent step 0) and some git/API mechanics Claude already knows are spelled out, so it could be tightened.

3 / 5

Actionability

Provides exact curl commands, GitHub REST API endpoints, git commands, and fully templated sub-agent prompts with variables — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Six phases are clearly sequenced with explicit validation checkpoints (dirty-tree check, token validity, existing-PR/branch/claim checks, confidence gate) and feedback loops (validate → fix → retry) for these batch/destructive operations.

5 / 5

Progressive Disclosure

Headers and phase numbering give clear in-file structure, but the ~860-line body is monolithic with no bundle files and large sub-agent prompt templates inlined that would fit better in separate reference files.

3 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

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 is specific, actionable, and distinct, clearly conveying a multi-step GitHub issue automation workflow. Its main weakness is the absence of natural-language trigger phrases beyond the slash-command usage syntax.

Suggestions

Add a 'Use when the user wants to automatically fix GitHub issues or address PR review comments' clause to make the trigger context explicit.

Include synonyms like 'pull requests' and 'bug reports' alongside 'PRs' and 'issues' for broader natural-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Fetch GitHub issues', 'spawn sub-agents to implement fixes and open PRs', 'monitor and address PR review comments' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

A clear 'what' is present and the 'Usage: /gh-issues ...' clause provides explicit invocation trigger guidance, but it lacks natural-language 'Use when...' phrasing describing the situations that call for the skill.

4 / 5

Trigger Term Quality

Includes natural terms like 'GitHub issues', 'PRs', and 'review comments', but misses common synonyms such as 'pull requests' or 'bug reports' that a user might say.

4 / 5

Distinctiveness Conflict Risk

The auto-fix-GitHub-issues-via-sub-agents niche is specific with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (871 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

Total

13

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.