Django测试策略,包括pytest-django、TDD方法论、factory_boy、模拟、覆盖率以及测试Django REST Framework API。
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill django-tdd62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description effectively lists specific Django testing tools and methodologies, demonstrating good technical specificity. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The Chinese language may also limit trigger matching for English-speaking users.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when writing Django tests, setting up test fixtures, mocking Django models, or testing DRF endpoints'
Include common user phrases in both Chinese and English such as 'unit tests', 'test coverage', '单元测试', 'API testing'
Add natural language triggers that users would say, such as 'write tests for my Django app' or 'set up pytest for Django'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Only describes 'what' (Django testing strategies and tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'Django', 'pytest-django', 'TDD', 'factory_boy', 'REST Framework', but missing common user variations like 'unit tests', 'integration tests', 'test cases', or English equivalents that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to Django testing ecosystem with distinct tools mentioned (pytest-django, factory_boy), but could overlap with general Python testing skills or broader Django development skills without clearer boundaries. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive Django testing skill with excellent actionable code examples covering pytest setup, factory_boy, model/view/API testing, and mocking. However, it's overly long for a single SKILL.md file and includes some obvious guidance that doesn't add value. The TDD workflow section could benefit from explicit validation checkpoints and error recovery patterns.
Suggestions
Split advanced topics (integration testing, mocking patterns, coverage configuration) into separate reference files and link from the main SKILL.md
Remove or significantly condense the 'Do's and Don'ts' section - these are standard testing principles Claude already knows
Add explicit validation steps to the TDD workflow, such as 'Run pytest after each change to verify test status' and guidance for debugging failing tests
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the 'Do's and Don'ts' section which largely states obvious testing principles Claude already knows. The coverage targets table and some explanatory text could be trimmed. | 2 / 3 |
Actionability | Excellent actionability with fully executable code examples throughout - pytest configuration, factory definitions, model tests, view tests, API tests, and mocking patterns are all copy-paste ready with complete, working code. | 3 / 3 |
Workflow Clarity | The TDD Red-Green-Refactor cycle is mentioned but lacks explicit validation checkpoints. The integration test shows a multi-step flow but doesn't include verification steps between stages or error recovery guidance for when tests fail. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in a single monolithic file. Advanced topics like integration testing, mocking strategies, and coverage configuration could be split into separate reference files for better navigation. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (729 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.