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

68%

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

70%

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

The body is a well-structured, self-contained instruction skill with a clear sequenced procedure and an explicit pass-criteria checklist. It loses points on minor cross-section redundancy and abstract guidance for the summarization/next-steps generation steps.

Suggestions

Consolidate the summary/status/next-steps definition into one place to remove repetition across "Required Output" and Procedure step 3.

Add a short concrete example of a per-issue report entry to make the output format unambiguous.

Tighten the "suggested next steps" guidance with example action phrasings tied to common issue states (open/blocked/stale).

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the summary/status/next-steps structure is restated across "Required Output", Procedure step 3, and the table columns in step 4, so it could be tightened.	2 / 3
Actionability	Provides concrete, copy-paste-ready specifics (search query template, `github-pull-request_doSearch`, `github-pull-request_issue_fetch`, table columns), but the summary and "suggested next steps" generation guidance stays abstract ("propose concrete, minimal actions", "avoid generic filler") with no example output.	2 / 3
Workflow Clarity	Clear 4-step sequence (search → fetch → build summary → produce report) with an explicit Pass Criteria checklist, empty-result handling, and a "do not invent facts" integrity check; the read-only task does not require destructive-operation feedback loops.	3 / 3
Progressive Disclosure	A single self-contained SKILL.md with well-organized sections and no nested or external references; appropriate for a skill that needs no bundle files.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 well-scoped to a clear niche, with concrete actions and third-person voice. It is capped by the absence of an explicit "Use when..." trigger clause and only partial coverage of natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to triage or summarize SD.Next feature-request issues."

Broaden trigger terms to include natural phrasings like "feature requests", "feature tracker", or "triage".

Keep the concise action list but pair it with the when-to-use guidance to lift completeness to 3.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Read SD.Next GitHub issues with [Feature] in the title", "produce a phased markdown report: short summary first, then status, then suggested next steps" — matching the multi-action anchor. Voice is third person ("Read", "produce"), so no specificity penalty applies.	3 / 3
Completeness	Clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant keywords ("GitHub issues", "[Feature]", "markdown report") but lacks common natural variations a user would say (e.g. "feature requests", "triage", "summarize issues"); coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	Scoped to the SD.Next repository and "[Feature]"-titled issues, giving it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 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: 058a7f0

Reviewed: about 23 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.