github-issues

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

Quality

87%

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

Quality

Content

100%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 body is a tight, actionable, well-sequenced workflow with explicit validation guidance and no padding or unnecessary external references. It is exemplary for a single-purpose reporting skill.

Dimension	Reasoning	Score
Conciseness	Lean, section-organized body with no padded concept explanations; nearly every line is actionable or directive, with only minor redundancy in the reporting-rules ordering note.	5 / 5
Actionability	Provides an exact search query template, concrete state-filter flags, named tool calls (github-pull-request_doSearch, github-pull-request_issue_fetch), and explicit output columns — fully executable guidance.	5 / 5
Workflow Clarity	Clear 4-step sequence with explicit checkpoints: empty-result handling ('no matches' report), sparse-body assumptions, and a Pass Criteria checklist that acts as a validation/feedback loop.	5 / 5
Progressive Disclosure	Single-purpose, self-contained skill with well-organized sections and no nested references; no bundle files are needed or present, so the well-organized overview suffices.	5 / 5
	Total	20 / 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 clearly distinct, but omits an explicit 'when to use' trigger clause, which caps its completeness. Adding a natural trigger sentence would lift the completeness and trigger-term scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks for issue triage or status summaries for SD.Next [Issue] tracker items.'

Add natural synonyms like 'triage' and 'issue tracker' to broaden trigger-term coverage.

Keep the existing concrete action list; it already anchors specificity well.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Read SD.Next GitHub issues', 'produce a phased markdown report', 'short summary first, then status, then suggested next steps' — with comprehensive coverage of the deliverable structure.	5 / 5
Completeness	Clearly states what the skill does, but includes no 'Use when...' or equivalent explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like 'GitHub issues', 'report', 'summary', 'status', 'next steps', and 'SD.Next', but lacks common synonyms such as 'triage' and has no file-extension-style triggers.	4 / 5
Distinctiveness Conflict Risk	Targets a very specific niche (SD.Next repo + the literal '[Issue]' title string) with distinct triggers and minimal overlap with other skills.	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-issues/SKILL.md
Commit: c40fc01

Reviewed: ~16 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.