issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the standard chain with a PR exit. Trigger with /hyperflow:issue, "work on issue #N", "fix this issue <url>", "implement this issue", "triage issue #N and raise a PR".

Quality

94%

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

92%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.

A tight, highly actionable orchestrator skill body with concrete commands, gated outward actions, explicit validation, and clean one-level-deep references. Only minor redundancy between inline rules and the consolidated 'Iron rules' section keeps conciseness just off the top anchor.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence — no padding explaining GitHub/issues — but the 'Iron rules' section restates invariants already stated inline in Steps 2 and 5 (injection guard, force-push), adding minor redundant tokens.	4 / 5
Actionability	Fully executable guidance for an instruction-only skill: concrete `gh issue view <n> --json ...` commands, literal spec path `.hyperflow/specs/issue-<n>-<slug>.md`, branch naming `feat/issue-<n>-<slug>`, and a copy-paste `Skill` invocation with explicit args.	5 / 5
Workflow Clarity	Steps 0–5 are clearly sequenced with explicit validation checkpoints (auth check, closed-issue confirm, already-solved check) and an error-handling table providing feedback loops for gh-missing, not-found, rate-limited, and headless cases; outward actions are gated.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview with well-signaled one-level-deep references to sibling materials (task-triage.md, trace/dispatch/pr SKILL.md, DOCTRINE/git-workflow/output-style); appropriately no inlined bulk content and no bundle files needed for an orchestrator.	5 / 5
	Total	19 / 20 Passed

Description

96%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.

A strong, dense description that answers what and when with concrete actions and natural trigger phrases in third-person voice. Slight overlap risk with sibling hyperflow skills keeps distinctiveness just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'triaged, planned, dispatched, and reviewed pull request', 'Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply)', 'synthesizes a spec from the issue's own acceptance criteria', 'runs the standard chain with a PR exit' — giving comprehensive coverage of the chain stages.	5 / 5
Completeness	Explicitly answers both 'what' (turn an issue into a triaged/planned/dispatched/reviewed PR) and 'when' ('Use when starting a chain from a GitHub issue') with concrete trigger phrases in the second paragraph.	5 / 5
Trigger Term Quality	Includes several natural phrases users would actually say — 'work on issue #N', 'fix this issue <url>', 'implement this issue', 'triage issue #N and raise a PR' — alongside the /hyperflow:issue invocation, covering common variations.	5 / 5
Distinctiveness Conflict Risk	Has a clear niche (GitHub issue entry point) with distinct issue-oriented triggers, but belongs to a family of closely related hyperflow chain skills (plan, dispatch, pr) creating minor overlap risk.	4 / 5
	Total	19 / 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 9 suspicious	Warning

	Total	13 / 16 Passed

Repository: jeremylongshore/tons-of-skills-marketplace
Path: plugins/ai-agency/hyperflow/skills/issue/SKILL.md
Commit: 88dcf65

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.