Content
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable Django testing examples covering models, views, serializers, APIs, mocking, and integration tests. However, it is far too verbose for a skill file—it reads like a full tutorial rather than a concise reference, explaining many concepts Claude already knows. The monolithic structure with no progressive disclosure makes it a poor fit for the context window budget.
Suggestions
Reduce content by 60-70%: remove generic testing advice (DO/DON'T lists, 'Remember: Tests are documentation'), trivial docstrings, and explanations of concepts Claude already knows. Keep only project-specific patterns and configurations.
Split into multiple files: keep SKILL.md as a concise overview (~50-80 lines) with quick-start examples, then reference separate files like FACTORIES.md, API_TESTING.md, and MOCKING.md for detailed examples.
Add a clear workflow section with validation steps: e.g., 'Write test → Run pytest → If red, implement → Run pytest → If green, refactor → Run coverage → Verify targets met'.
Remove the coverage goals table and best practices lists—these are generic advice that doesn't add actionable value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Explains basic concepts Claude already knows (what TDD is, what factories are, basic pytest usage). The DO/DON'T lists are generic testing advice Claude doesn't need. Docstrings like '"""Factory for User model."""' and '"""Test User model."""' add zero value. Much of this is a Django testing tutorial rather than a concise skill reference. | 1 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready. Includes complete pytest.ini configuration, test settings, conftest.py fixtures, factory definitions, and full test examples for models, views, serializers, and API endpoints. Commands like 'pytest --cov=apps --cov-report=html' are specific and runnable. | 3 / 3 |
Workflow Clarity | The TDD Red-Green-Refactor cycle is mentioned but only superficially demonstrated. The integration test shows a clear multi-step flow. However, there are no validation checkpoints or feedback loops for the overall testing workflow (e.g., what to do when tests fail, how to debug, when to run coverage). The skill reads more as a reference catalog than a guided workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. All content—setup, factories, model tests, view tests, API tests, mocking, integration tests, best practices, coverage—is inlined in a single massive document. This would benefit enormously from splitting into separate files (e.g., FACTORIES.md, API_TESTING.md, MOCKING.md) with a concise overview in the main skill. | 1 / 3 |
Total | 7 / 12 Passed |