Same testing methodology as `/qa`, but report-only. It is for bug finding without any code edits.
Works with
Same testing methodology as /qa, but report-only. It is for bug finding without any code edits. Imported from qa-only/SKILL.md in garrytan/gstack.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionqa-onlyExecute the skills CLI command in your project's root directory to begin installation:
Fetches qa-only from garrytan/gstack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate qa-only. Access via /qa-only in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
0
upvotes
Run in your terminal
0
installs
0
this week
—
stars
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
garrytan/gstack
garrytan/gstack
garrytan/gstack
garrytan/gstack
garrytan/gstack
garrytan/gstack
We added qa-only from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
qa-only has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for qa-only matched our evaluation — installs cleanly and behaves as described in the markdown.
qa-only fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: qa-only is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added qa-only from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in qa-only — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added qa-only from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
qa-only fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend qa-only for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 70