github-features

Read SD.Next GitHub issues with [Feature] in the title and produce a phased markdown report: short summary first, then status, then suggested next steps per issue.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/github-features/SKILL.md

Quality

Content

80%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 concise, well-structured instruction skill with concrete tool guidance, held back mainly by missing validation/error-recovery checkpoints for a batch operation.

Suggestions

Add an explicit validation checkpoint after the search step (e.g., confirm matched issue count and handle zero matches or rate limits before fetching details).

Include an error-recovery feedback loop for failed issue fetches (retry or skip with a noted gap).

Show a concrete example invocation of the search and fetch tools to make guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no over-explanation of concepts Claude already knows; every section earns its place and assumes Claude's competence.	5 / 5
Actionability	Provides a concrete search query template, named tools (github-pull-request_doSearch, github-pull-request_issue_fetch), and specific output columns, but lacks literal copy-paste invocations for all cases.	4 / 5
Workflow Clarity	The four-step sequence is clear, but this batch operation (multiple issues) has no explicit validation checkpoint or error-recovery feedback loop, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	A short, single-purpose skill under 50 lines with well-organized sections and no need for external references, qualifying for the simple-skill exception.	5 / 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.

A specific, well-scoped description with concrete actions and low conflict risk, weakened only by the absence of an explicit 'when to use' trigger clause and slightly incomplete synonym coverage.

Suggestions

Add an explicit 'Use when...' clause naming trigger phrases (e.g., feature-request triage, status summaries for [Feature] issues).

Broaden trigger terms with synonyms like 'feature requests' and 'triage' so users searching those words land on the skill.

Use third-person verb form consistently to keep the trigger phrasing natural for invocation.

Dimension	Reasoning	Score
Specificity	Names the domain ('SD.Next GitHub issues with [Feature] in the title') and lists multiple concrete actions ('produce a phased markdown report: short summary first, then status, then suggested next steps per issue'), giving comprehensive coverage.	5 / 5
Completeness	The 'what' is clearly stated but there is no explicit 'Use when...' trigger clause, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms like 'GitHub issues', '[Feature]', 'status', and 'next steps' that users would say, but misses common synonyms such as 'feature requests' or 'triage'.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (SD.Next [Feature] issues) with distinct triggers, so conflict with other skills is minimal.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: vladmandic/sdnext
Path: .github/skills/github-features/SKILL.md
Commit: c40fc01

Reviewed: ~17 hours ago

Table of Contents

Discovery Implementation Validation

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.