gh-issue

Create structured GitHub issues with sub-tasks and proper formatting. Use when organizing development work into trackable issues, breaking down features into parent/child issues, converting discussions into tracked work, or creating issues from conversation context.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/gh-issue/skills/gh-issue/SKILL.md

Quality

Content

38%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 well-structured but thin on substance: it rephrases the description rather than giving Claude executable guidance. It lacks concrete gh commands, issue templates, and verification steps for an outward-facing operation.

Suggestions

Add executable examples: show the actual `gh issue create` commands (with `--title`, `--body`, parent/child linking) instead of only describing that the agent uses the gh CLI.

Provide a concrete issue-body template (title format, acceptance-criteria section, sub-task checklist) so output is consistent and copy-paste ready.

Add a verification step in How It Works (e.g., confirm each issue URL resolves and sub-tasks are linked to the parent) since issue creation is an outward-facing batch operation.

Trim the Overview, Tips, and Integration sections, which restate the description and add padding without new actionable detail.

Dimension	Reasoning	Score
Conciseness	The body largely restates the description across Overview, When to Use, How It Works, Agent Delegation, Tips, and Integration sections without adding technical knowledge Claude lacks, matching anchor 2's 'noticeably verbose; several unnecessary explanations or padded sections'.	2 / 5
Actionability	It provides only high-level hints ('Clear, descriptive titles', 'Detailed descriptions with acceptance criteria') with no executable code, gh CLI commands, or issue-body templates, fitting anchor 2's 'minimal concrete guidance; missing the specific steps to execute'.	2 / 5
Workflow Clarity	How It Works lists a 3-step sequence (analyze context, delegate to agent, provide links) but includes no validation or verification checkpoints that an outward-facing issue-creation operation warrants, matching anchor 3's 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	Content is organized into clearly labeled sections with no nested references and no bundle files to mismanage, giving good structure; it is not a clean anchor 5 only because some inline sections (Tips, Integration) could be trimmed.	4 / 5
	Total	11 / 20 Passed

Description

83%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 well-crafted: it pairs a concrete statement of capability with an explicit 'Use when' clause listing multiple natural trigger phrases. It is specific, complete, and largely distinct from other skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Create structured GitHub issues with sub-tasks and proper formatting', 'breaking down features into parent/child issues', 'converting discussions into tracked work') but they are variations of issue creation rather than comprehensive coverage, so it sits at anchor 4 rather than 5.	4 / 5
Completeness	Explicitly states what it does ('Create structured GitHub issues with sub-tasks and proper formatting') and when to use it ('Use when organizing development work... breaking down features... converting discussions...'), matching the anchor 5 example of clearly answering both what and when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('GitHub issues', 'sub-tasks', 'parent/child issues', 'break down features') with good coverage, though a few synonyms like 'tickets' are missing, placing it just below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The GitHub-issues-with-sub-tasks niche is mostly distinct with clear triggers, but 'organizing development work into trackable issues' risks minor overlap with general task-management or todo skills, keeping it just below anchor 5.	4 / 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: freightCognition/linehaulai-claude-marketplace
Path: plugins/gh-issue/skills/gh-issue/SKILL.md
Commit: 88571a6

Reviewed: 5 days 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.