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.

73

Quality

90%

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

92%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.

A well-structured, actionable instruction skill with concrete `gh` commands, an explicit approval gate, and a close-recommendation checkpoint that satisfy the validation requirements for batch/destructive operations. Minor conciseness gains are available by deduplicating the standalone rules/heuristics sections with the workflow steps.

Suggestions

Fold the "Reply Rules" and "Closing Heuristics" bullets into their corresponding workflow steps (or reference them once) to remove the restatement and tighten the body.

Optionally extract the "Suggested Command Pattern" into a references/ file if the skill grows, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient with no padding of concepts Claude already knows, but "Reply Rules" and "Closing Heuristics" partly restate guidance already embedded in the workflow steps and could be tightened.

4 / 5

Actionability

Copy-paste-ready commands with concrete flags (`gh issue list --repo <owner/repo> --state open --limit <n>`, `gh issue view ... --json number,title,body,author`, `--comments`) plus a precise per-issue output loop cover the common cases.

5 / 5

Workflow Clarity

A clear 6-step sequence with explicit approval gate ("Do not post the comment until the user explicitly approves") and a close-decision checkpoint, providing the validation feedback loop required for this batch/destructive (`gh issue close`) operation.

5 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the single SKILL.md is well-organized into clear sections (Overview, Workflow, Reply Rules, Closing Heuristics, Suggested Command Pattern, Output Pattern), satisfying the simple-skill exception for a self-contained skill.

5 / 5

Total

19

/

20

Passed

Description

88%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.

A strong, specific description that clearly states both capabilities and trigger conditions, anchored to a concrete workflow and real CLI commands. Slight deductions for niche jargon (PigeonPod/Codex) that limits natural trigger-term coverage and creates minor overlap ambiguity.

Suggestions

Add broader natural synonyms a maintainer might say (e.g., "release follow-up", "close resolved issues") alongside the PigeonPod/Codex-specific framing to improve trigger-term coverage.

Consider making the tool name (Codex) less load-bearing so the trigger reads naturally for any maintainer doing release-note-driven issue triage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ("Find open GitHub issues", "draft issue replies in the issue author's language", "post approved comments with `gh issue comment`", "recommend whether each issue should be closed") with a real command, giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both "what" (multiple concrete actions) and "when" ("Use when Codex needs to turn a shipped release into structured GitHub issue follow-up") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Natural terms a maintainer would say ("release note", "GitHub issues", "issue replies", "closed") are present, but coverage is niche/jargon-heavy (PigeonPod, Codex) and missing common synonyms.

4 / 5

Distinctiveness Conflict Risk

Clear niche (release-note to issue follow-up) scoped by specific tooling (`gh issue comment`) and distinct triggers; minor overlap risk with general GitHub-issue skills.

4 / 5

Total

18

/

20

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.

Validation — 16 / 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.