django-tdd

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/django-tdd/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable, copy-paste-ready Django testing code, but it is a long monolithic document that could be split across reference files and tightened, and its TDD workflow lacks explicit validation checkpoints.

Suggestions

Move the larger reference blocks (factory definitions, full model/view/serializer/API test suites, coverage details) into separate reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit validation checkpoints to the TDD workflow (e.g. 'run pytest, confirm the new test fails, implement, re-run until green, then refactor and re-run').

Trim redundant near-duplicate test files and verbose per-test docstrings to reduce token overhead while preserving the executable examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — it does not explain concepts Claude already knows — but at ~725 lines with several near-complete duplicate test files (models, views, serializers, API) and verbose docstring comments, it could be tightened, matching the score-2 anchor of 'mostly efficient but includes some unnecessary content'.	2 / 3
Actionability	It provides fully executable, copy-paste-ready material — pytest.ini config, test settings, conftest fixtures, factory_boy factories, complete test classes, mocking examples, and coverage commands — matching the score-3 anchor of fully executable code with specific examples.	3 / 3
Workflow Clarity	A TDD red-green-refactor sequence and a 'when to enable' section are present, but the workflow is shown as a single commented code block with no explicit validation checkpoint or fix-retry feedback loop, matching the score-2 anchor of steps listed with implicit or missing checkpoints.	2 / 3
Progressive Disclosure	No bundle/reference files exist and the entire guide sits in one monolithic SKILL.md well over 50 lines, with content (factories, model/view/serializer/API tests, coverage) that could be split into separate reference files kept inline, matching the score-2 anchor of 'content that should be separate is inline' despite clear section organization.	2 / 3
	Total	9 / 12 Passed

Description

72%Weight 40%Scale 1-3

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 is specific, well-keyworded, and clearly distinct, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness and leaves the 'when to use' guidance implicit.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or debugging Django tests, setting up pytest-django, or testing DRF APIs'.

Lead with concrete actions (verbs) rather than 'strategies with', e.g. 'Write and run Django tests with pytest-django, build test data with factory_boy, mock external services, and measure coverage'.

Keep the strong keyword coverage but ensure the phrase reads as actionable capability, not just a tool list.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Django testing strategies') and several concrete tools ('pytest-django, TDD methodology, factory_boy, mocking, coverage, ... Django REST Framework APIs'), but it lists tools/strategies rather than enumerating specific concrete actions (verbs), matching the score-2 anchor of naming domain and some actions without being fully comprehensive.	2 / 3
Completeness	It clearly answers 'what does this do', but there is no explicit 'Use when...' clause or equivalent trigger guidance for when Claude should invoke it; per the rubric guideline, a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms a user would actually say — 'Django', 'pytest', 'pytest-django', 'factory_boy', 'mocking', 'coverage', 'TDD', 'Django REST Framework', 'APIs' — giving good coverage without descending into low-level jargon, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	The Django-specific testing toolchain (pytest-django, factory_boy, DRF APIs) carves a clear niche with distinct triggers that is unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 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	15 / 16 Passed

Repository: xu-xiang/everything-claude-code-zh
Path: docs/ja-JP/skills/django-tdd/SKILL.md
Commit: dfbf946

Reviewed: 28 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.