CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-issues

Triage GitHub issues, select safe candidates, implement focused fixes, open pull requests, and address actionable review feedback.

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/ekko-agent/skills/gh-issues/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a well-sequenced, actionable issue-to-PR workflow with strong validation checkpoints and lean prose. Minor gaps in actionability (placeholder commands) and progressive disclosure (all content inline) keep it just short of maximum.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, using concrete commands instead of explanatory padding; a few sentences (e.g. "gh issue list excludes pull requests") could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides concrete, mostly copy-paste-ready `gh` and `git` commands throughout, though several use placeholders (OWNER/REPO, <n>) requiring substitution and the delegate_task path is instructional rather than executable.

4 / 5

Workflow Clarity

A clearly numbered 1–5 sequence plus Review feedback and Report sections, with explicit validation checkpoints (dry run, dirty-checkout handling, auth-stop, diff review, test-evidence rule) and feedback loops for destructive/batch operations.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned with clear headers and no nested references, though some inline content (PR body template, delegate_task context list) could conceptually be split out.

4 / 5

Total

17

/

20

Passed

Description

75%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 and distinctive, naming concrete actions across the issue-to-PR pipeline. Its main weakness is the absence of an explicit "Use when…" trigger clause, which caps completeness at 3.

Suggestions

Append an explicit "Use when…" clause, e.g. "Use when the user asks to fix GitHub issues, turn issues into PRs, or address review feedback on PRs."

Add common synonyms/variants like "PR", "fix issues", and "issue to PR" to broaden natural trigger coverage.

Keep the concrete action list as-is — it is already comprehensive and specific.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across the full pipeline — "Triage GitHub issues", "select safe candidates", "implement focused fixes", "open pull requests", and "address actionable review feedback" — giving comprehensive coverage.

5 / 5

Completeness

The "what" is clearly stated, but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("GitHub issues", "pull requests", "review feedback"), but misses common synonyms/variants such as "PR", "fix issues", or "issue to PR".

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (issues-to-PR workflow) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
EKKOLearnAI/hermes-studio
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.