Pytest patterns for Python APIs -- httpx AsyncClient, conftest fixtures, database isolation, parametrize edge cases, error response testing, auth flows, factory fixtures
99
99%
Does it follow best practices?
Impact
100%
1.23xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that hits all the marks. It provides specific, concrete capabilities (fixture organization, parametrize, database isolation), uses natural trigger terms that developers would actually say, explicitly states when to use it, and carves out a clear niche in Python API testing that distinguishes it from general testing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'httpx AsyncClient setup, conftest.py fixture organization, fixture scoping, parametrize for edge cases, factory fixtures, database isolation, testing error responses and auth flows.' | 3 / 3 |
Completeness | Clearly answers both what (pytest patterns, fixture organization, database isolation, etc.) AND when ('Triggers when writing tests for any Python web API, adding test coverage, or building a new API that needs tests'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Pytest', 'testing Python APIs', 'FastAPI', 'Flask', 'conftest.py', 'fixture', 'parametrize', 'test coverage', 'web API', 'tests'. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on Python API testing with pytest; distinct triggers like 'FastAPI', 'Flask', 'httpx AsyncClient', 'conftest.py' make it unlikely to conflict with general testing or non-API Python skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill that provides comprehensive, actionable pytest patterns for API testing. It's concise yet thorough, with executable code examples throughout, clear workflow guidance on fixture scoping and database isolation, and a valuable common mistakes table. The content respects Claude's intelligence while providing the specific patterns and gotchas that would otherwise require experience to learn.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient throughout. It assumes Claude knows Python, pytest basics, and web frameworks. Every section provides actionable patterns without explaining what APIs or testing are. The common mistakes table is dense with value. | 3 / 3 |
Actionability | Every section includes complete, executable code examples with proper imports and context. The fixtures are copy-paste ready, and the parametrize examples show real validation scenarios. Even the setup includes the exact pip install command and pyproject.toml config. | 3 / 3 |
Workflow Clarity | The skill clearly sequences test setup (conftest organization, fixture hierarchy), explains fixture scoping decisions with explicit rationale, and includes validation patterns (asserting response shapes, testing error cases). The database cleanup section explicitly states 'reset before, not after' with clear reasoning. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear numbered sections that progress from basic setup to advanced patterns. The skill appropriately keeps all content inline since it's a cohesive reference, and links to verifiers at the end for hands-on practice. No unnecessary nesting or external file chains. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents