What is qualify-issue?

A workflow that asks an external GitHub issue reporter structured follow-up questions until a bug report or feature request has enough detail for requirements work.

Use it to review an issue's existing discussion, identify unanswered questions, ask clarification questions in rounds, and stop when the issue is complete or the reporter stops responding.

It fills in missing information early, reducing back-and-forth and preventing under-specified issues from moving into implementation.

qualify-issue — Skill for Claude Code by tomzx/agents

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tomzx/agents --skill qualify-issue

Clone the repo

git clone --depth 1 https://github.com/tomzx/agents

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomzx/agents/qualify-issue/github.svg)](https://agentmods.dev/skills/tomzx/agents/qualify-issue)

Your own site

<a href="https://agentmods.dev/skills/tomzx/agents/qualify-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/qualify-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tomzx/agents/qualify-issue"><img src="https://agentmods.dev/badge/skills/tomzx/agents/qualify-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,639 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.01639
Opus 5.5	$0.00010	$0.00656
Sonnet 5.5	$0.00005	$0.00328
Haiku 4.5	$0.00003	$0.00164

Measured 22d ago against content hash a95725c1bf5d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qualify-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/qualify-issue/SKILL.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Qualify Issue

Takes an externally submitted GitHub issue (feature request or bug report) and drives a structured Q&A loop with the reporter until the issue contains enough information to proceed to /create-requirements.

Assumes review-issue has already been run and identified what is missing. This skill owns the iterative clarification loop. It stops when the issue is fully qualified or the reporter is unresponsive.

Prerequisites

Apply the shared SDLC conventions in skills/sdlc/references/shared.md.
If no argument is provided, target the issue from $ISSUE_NUMBER (and $REPO).
gh CLI authenticated with write access to the target repository
Issue URL or number ($1), and optionally repository in owner/repo format ($2)
Read any files present under .sdlc/context/ and apply any artifact style rules found there

Skill attribution (GitHub)

Before posting any comment with ghx, read ../github-post-attribution/SKILL.md and append the Posted with footer for SKILL_DIR = qualify-issue.

Communication guidelines (outbound text)

Before composing any text posted or drafted on the user's behalf, apply communication-guidelines/SKILL.md.

Workflow

Fetch issue + comment history
           |
           v
Identify open questions
           |
           v
All answered?
   /          \
 Yes            No
  |              |
  v              v
Update issue   Post questions
body + signal  as comment
"qualified"         |
                    v
              Wait for reporter
              (skill stops here)
                    |
                    v
              Re-invoke when
              replies arrive

Steps

1. Fetch the issue and full comment history

ghx issue view $1 [--repo $2] --comments

Extract:

Issue type (bug / feature request)
What is already known (background, version, steps, ACs, etc.)
What is still missing or ambiguous
Any prior clarification comments and their answers

Read the full file on GitHub · 206 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

22d ago Changed · +6 lines a95725c1bf5d
27d ago Changed 7f60aa2af569
28d ago Changed · +4 lines 69e98074a1a0
1mo ago First seen · 196 lines · 25 tokens per session scan A 1ad20927af07

Subscribe to this mod's changes

qualify-issue is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,639 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Planning Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

qa-project-bootstrap

Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…

petrkindlmann/qa-skills · 124 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens