senior-qa

I was digging through the skill marketplace and noticed senior-qa came in pretty thin on the PDA side—looks like there's a lot of opportunity to make this more token-efficient without sacrificing the core value. Want to walk through some ideas on trimming the fat while keeping the teeth?

Links:

• GitHub
• Your agentic skill in the SkillzWave marketplace

The TL;DR

You're at 33/100, which puts this in F territory. This one's got the spec compliance piece locked down (12/15), but the utility and ease of use sides are really struggling. The core issue: everything reads like a template outline, not an actual working skill. The references are boilerplate, the scripts are empty shells, and there's not much here a developer could actually use.

What's Working Well

• Spec compliance is solid - Valid YAML, proper naming conventions, frontmatter is clean
• Trigger terms are decent - "test automation", "qa automation", "testing patterns" should help discoverability
• Structure exists - You've got the reference files and scripts scaffolded out, which means there's a foundation to build on

The Big One: Empty Reference Files & Scripts

This is your main blocker. All three reference files (test_automation_patterns.md, qa_best_practices.md, testing_strategies.md) are identical placeholder content with lines like "Detailed explanation of the pattern" and "Scenario 1, Scenario 2, Scenario 3" that don't actually tell someone how to do QA.

Same with the scripts—they're hollow Python templates with comments like "# Main logic here" instead of actual test generation, coverage analysis, or E2E scaffolding.

The fix: Replace these with real content. If this skill is about testing React/Next.js projects, give me actual patterns (Page Object Model, test data builders, test pyramid strategy). Make the scripts do something tangible—parse Jest coverage reports, generate Playwright test stubs, scaffold test suites from component files. This alone could push you +15-20 points.

Other Things Worth Fixing

1. Strip the marketing language - Lines like "Complete toolkit", "Comprehensive guide", "Expert-level automation" sound like sales copy, not developer docs. Just be direct: "Generates test suites for React projects" is better than "Expert-level automation for production-grade output"

2. Add a table of contents - 210 lines without a TOC is rough navigation. Add one after the intro so people can jump to what they need (+2 points)

3. Rename the skill - "senior-qa" is too vague. Something like "react-testing-framework" or "test-suite-generator" tells people exactly what it does

4. Make workflows actionable - Your development workflow section talks about "following patterns" but references empty files. Walk through actual steps: run the generator → review output → run tests → check coverage

Quick Wins

• Replace 3 reference files with real testing patterns and QA best practices (~+12 pts)
• Implement actual logic in Python scripts instead of empty templates (~+10 pts)
• Cut the marketing language, keep it technical (~+3 pts)
• Add TOC + fix skill name for discoverability (~+4 pts)

You've got a solid foundation structurally. The missing piece is real substance—either document actual QA patterns or build real tooling that generates tests. Either way, you're looking at a meaningful jump from here.

Checkout your skill here: SkillzWave.ai | SpillWave We have an agentic skill installer that install skills in 14+ coding agent platforms. Check out this guide on how to improve your agentic skills.