CtrlK
BlogDocsLog inGet started
Tessl Logo

release-issue-responder

Find open GitHub issues that are covered by a specific release note, draft issue replies in the issue author's language, post approved comments with `gh issue comment`, and recommend whether each issue should be closed. Use when Codex needs to turn a shipped release into structured GitHub issue follow-up, especially for PigeonPod release-note-driven maintainer workflows.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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

The content is actionable and well-sequenced with explicit approval and close-decision checkpoints, and it is sensibly organized as a single file. Its only weakness is redundant restatement of the workflow across the Workflow, Closing Heuristics, and Output Pattern sections.

Suggestions

Collapse the 'Output Pattern' loop into a reference to the Workflow steps, or merge them, to remove the duplicated state-match → draft → approve → post → close sequence.

Fold the 'Closing Heuristics' bullets into step 6 so the close/keep-open criteria appear once instead of twice.

DimensionReasoningScore

Conciseness

The body is mostly lean and assumes Claude's competence, but the 'Output Pattern' loop restates Workflow steps 4-6 and 'Closing Heuristics' repeats step 6's close/keep-open criteria, so it could be tightened.

2 / 3

Actionability

It provides concrete, executable `gh` commands with flags (list, view --json, comment, close) plus specific close/keep-open criteria, giving copy-paste-ready guidance for an instruction-only skill.

3 / 3

Workflow Clarity

Six steps are clearly sequenced with an explicit approval gate ('Do not post the comment until the user explicitly approves') and a close-decision checkpoint ('Wait for the user's decision'), including feedback loops for the outward-facing comment/close operations.

3 / 3

Progressive Disclosure

It is a single-file skill with no external references needed, organized into clearly headed sections (Overview, Workflow, Reply Rules, Closing Heuristics, Commands, Output Pattern), which satisfies the simple-skill allowance for a score of 3.

3 / 3

Total

11

/

12

Passed

Description

85%Weight 40%Scale 1-3

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 complete with an explicit 'Use when' trigger and a distinctive niche. Its main weakness is the trigger clause's reliance on tool/product-internal terms ('Codex', 'PigeonPod') rather than natural user phrasing.

Suggestions

Rewrite the 'Use when' clause around user-natural phrasing (e.g. 'Use when you want to follow up on open GitHub issues after shipping a release') rather than naming 'Codex' or 'PigeonPod'.

Add common trigger variations users might say, such as 'release follow-up', 'reply to issues from a changelog', or 'close issues fixed by a release'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Find open GitHub issues', 'draft issue replies in the issue author's language', 'post approved comments with gh issue comment', and 'recommend whether each issue should be closed' — matching the multi-action score-3 anchor rather than the partial score-2.

3 / 3

Completeness

It clearly states what the skill does and includes an explicit 'Use when Codex needs to turn a shipped release into structured GitHub issue follow-up' trigger, satisfying both the what and the when at the score-3 level.

3 / 3

Trigger Term Quality

It includes relevant natural terms ('GitHub issues', 'release note', 'issue replies'), but the explicit trigger leans on product-internal jargon ('Codex', 'PigeonPod release-note-driven maintainer workflows') rather than phrasing a user would naturally say, leaving common variations uncovered.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche — release-note-driven issue follow-up with an approval gate and close recommendation — with distinct triggers unlikely to overlap with generic skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
aizhimou/pigeon-pod
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.