Install any skill in seconds. Free to start, no credit card required.
Get Started Free →evgeniiperov/qa
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language.
Passed 5 of 11 test cases with the skill, and 6 of 11 without it.
3 fixed6 passed either way8 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We just finished filing issue #45 for the navigation menu bug. What should you ask me immediately after printing the issue link?
| Checked | Without skill | With skill |
|---|---|---|
| Asks the user whether to proceed to the next issue or conclude the QA session. | Missed | Passed |
The instructions your model reads when the skill loads.
Run an interactive QA session. The user describes problems they're encountering. You clarify, explore the codebase for context, and file GitHub issues that are durable, user-focused, and use the project's domain language.
Let the user describe the problem in their own words. Ask at most 2-3 short clarifying questions focused on:
Do NOT over-interview. If the description is clear enough to file, move on.
While talking to the user, kick off an Agent (subagent_type=Explore) in the background to understand the relevant area. The goal is NOT to find a fix — it's to:
This context helps you write a better issue — but the issue itself should NOT reference specific files, line numbers, or internal implementation details.
Before filing, decide whether this is a single issue or needs to be broken down into multiple issues.
Break down when:
Keep as a single issue when:
test cases passed, vs 6 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.