python-testing

I took a look at your python-testing skill and wanted to share some thoughts.

Links:

• GitHub
• Your skill in the SkillzWave marketplace

The TL;DR

You're at 89/100, solidly in B territory. This skill has strong fundamentals—the utility pillar scored 18/20, meaning it actually solves real pytest problems. Your Progressive Disclosure Architecture is clean (26/30), with a nice hub-and-spoke structure across 6 focused modules. The weak spots are in the details: missing navigation aids in longer modules, a Quick Start that's too high-level, and some consistency issues in voice.

What's Working Well

• Excellent utility: You're covering real testing needs comprehensively—sync/async testing, mocking patterns, CI/CD integration. The pyproject.toml and CI templates are copy-paste ready, which is exactly what developers want.
• Smart architecture: The 6-module structure with progressive loading makes sense. Each module is focused, estimated tokens are included, and the hub-and-spoke design from SKILL.md keeps things navigable.
• Rich examples and triggers: Your triggers section is specific ("pytest async", "mock dependencies") and your code examples throughout actually show patterns developers can use immediately.
• Exit criteria checklist: This is solid. It gives users a concrete way to know when they've successfully applied the skill.

The Big One: Missing Navigation in Longer Modules

Your async-testing.md module is 192 lines with no table of contents. When modules get this long, developers need signposts. Right now they hit the file and have to scroll to find what they need.

The fix: Add a ## Table of Contents section after the frontmatter that links to your major sections (e.g., "### Running Async Tests", "### Async Fixtures", etc.). Same for any other modules over 100 lines. This is a +1 point improvement and makes the skill way more usable.

Other Things Worth Fixing

1. Quick Start needs actual commands (SKILL.md:40-45) — Right now it's abstract ("Configure pytest", "Implement Tests"). Give concrete examples: "Run pytest --cov=src to generate coverage reports" or link to the test-infrastructure module. +2 points.

2. Second-person voice slips (SKILL.md:74-80) — Phrases like "your needs" should be "project requirements". Imperative voice is more objective. Small but adds polish. +1 point.

3. Add verification steps to code examples — Show developers how to validate patterns work. After each code block, add something like "Run pytest -v tests/test_example.py to verify." Feedback loops matter. +1 point.

4. Boost your description triggers — You only have 1-2 trigger phrases. Add a few more: "unittest replacement", "test coverage", "pytest fixtures". Better discoverability in the marketplace. +1 point.

Quick Wins

• Add TOCs to modules >100 lines
• Flesh out Quick Start with actual commands
• Fix second-person voice ("your" → "project")
• Add post-example verification steps
• Expand description trigger phrases

These four moves would bump you from 89 to 95+, landing you firmly in A territory.

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.