speckit-taskstoissues

Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-taskstoissues/SKILL.md

Quality

Content

67%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 delivers a clear, actionable, well-guarded workflow for converting tasks to GitHub issues, with strong sequencing and validation checkpoints. Its main weakness is the near-duplicate pre/post extension-hook blocks, which add verbosity that could be factored out.

Suggestions

De-duplicate the Pre-Execution and Post-Execution hook sections by defining the hook-handling procedure once and referencing it for both phases.

Specify the exact GitHub MCP tool call for issue creation (e.g. tool name and required fields) rather than the generic "use the GitHub MCP server to create a new issue".

Add a brief error-recovery feedback loop for issue creation failures (e.g. retry on rate limit, report partial success) to reach full workflow-clarity maturity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational instruction, but the Pre-Execution and Post-Execution hook blocks are nearly identical ~15-line duplications that could be tightened into a shared procedure, leaving some avoidable padding.	3 / 5
Actionability	Concrete commands are provided (check-prerequisites.ps1 invocation, git config remote.origin.url, hook EXECUTE_COMMAND format), but the core "use the GitHub MCP server to create a new issue" step lacks the specific MCP tool call, leaving a minor gap.	4 / 5
Workflow Clarity	A clear numbered sequence is present with explicit CAUTION guardrails (only proceed if remote is GitHub; never create issues in non-matching repos) serving as validation checkpoints, though no error-recovery feedback loop is given for failed issue creation.	4 / 5
Progressive Disclosure	Content is well-organized under clear section headers (User Input, Pre/Post-Execution Checks, Outline) with no bundle files, but the substantial duplicated hook-handling detail could be factored into a reference, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

53%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 clearly states what the skill does and occupies a distinct niche, but lacks any explicit "Use when..." trigger guidance and only names a single concrete action, capping completeness and specificity at mid-range.

Suggestions

Add an explicit trigger clause such as "Use when converting spec-kit tasks into GitHub issues or when the user asks to create issues from a task list."

List a few more concrete actions (e.g. "resolves dependencies between issues, applies labels, links issues to the feature") to lift specificity toward comprehensive coverage.

Include natural synonyms users might say ("create GitHub issues", "turn tasks into tickets", "generate issues from tasks") to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	"Convert existing tasks into actionable, dependency-ordered GitHub issues" names the domain and one concrete action with modifiers, but does not list several distinct actions, matching the 1-2 concrete-actions anchor rather than the comprehensive 5.	3 / 5
Completeness	The "what" is clear (convert tasks to dependency-ordered GitHub issues), but there is no "Use when..." clause or equivalent trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural keywords like "tasks" and "GitHub issues" appear, but common variations or synonyms a user would say (e.g. "create issues", "turn tasks into tickets") are missing, placing it at the some-relevant-keywords anchor.	3 / 5
Distinctiveness Conflict Risk	The tasks-to-issues-with-dependencies niche is mostly distinct with only minor overlap risk against closely related GitHub/spec-kit skills, fitting the mostly-distinct anchor above the midpoint.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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

Validation for skill structure

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

	Total	14 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-taskstoissues/SKILL.md
Commit: eaa505e

Reviewed: 3 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.