github-issues

Create, triage, label, assign GitHub issues via gh or REST.

Quality

71%

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 ./skills/github/github-issues/SKILL.md

Quality

Content

76%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 content is highly actionable and well-structured with executable dual-path examples, but its workflows lack validation checkpoints—most notably the destructive bulk-close operation—holding workflow clarity to the rubric's cap.

Suggestions

Add an explicit validation/confirmation step before destructive batch operations, e.g. list the matched issues and require confirmation before closing each, with a dry-run flag.

Insert a verification checkpoint in the triage workflow (e.g. re-view the issue after labeling/assigning to confirm state).

Consider moving the bug/feature templates and bulk-operations recipes into reference files to shorten the main body and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is code-first with minimal prose and no beginner-concept padding; the dual gh/curl coverage intentionally doubles length rather than padding it.	4 / 5
Actionability	Copy-paste executable gh and curl examples, a realistic issue body, issue templates, and a quick-reference table cover the common cases fully.	5 / 5
Workflow Clarity	The triage workflow is sequenced but lacks validation checkpoints, and the §5 bulk-close is a destructive batch operation with no verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	A single well-organized file with clear section headers and a quick-reference table, no nested references; minor opportunities to split templates/bulk-ops into separate files.	4 / 5
	Total	16 / 20 Passed

Description

66%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 well-targeted to GitHub issues with natural trigger terms, but it omits any explicit "Use when…" usage guidance, leaving the "when" half of completeness unaddressed.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating, triaging, labeling, or assigning GitHub issues, or when the user mentions bug reports or issue tracking."

Broaden trigger-term coverage with synonyms users actually say, such as "bug reports" or "tickets".

Mention additional core actions (search, comment, close) to make the capability list more comprehensive.

Dimension	Reasoning	Score
Specificity	"Create, triage, label, assign" lists four concrete actions on the GitHub-issues domain, with minor coverage gaps (no comment/close/search/view).	4 / 5
Completeness	The "what" is clear but there is no "Use when…" trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	"GitHub issues", "triage", "label", "assign", and "create" are natural user terms, though a few synonyms (e.g. bug reports, tickets) are missing.	4 / 5
Distinctiveness Conflict Risk	"GitHub issues" is a distinct niche separate from the related github-pr-workflow skill, with only minor overlap risk.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: NousResearch/hermes-agent
Path: skills/github/github-issues/SKILL.md
Commit: 2635035

Reviewed: 1 day 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.