django-tdd

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

65%

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 extensive executable, copy-paste-ready test code, but it is a monolithic wall of inline material with implicit TDD feedback loops and no progressive disclosure into separate reference files. Tightening redundancies and splitting deep references would raise conciseness and progressive_disclosure.

Suggestions

Add explicit validation checkpoints to the TDD workflow — e.g. 'Run pytest → confirm RED → implement minimal code → re-run pytest → confirm GREEN → refactor → re-run'.

Move the large, reusable blocks (factory_boy guide, coverage targets, full test settings) into separate reference files (e.g. FACTORIES.md, COVERAGE.md) and link to them from SKILL.md.

Remove the duplicated api_client fixture inside TestProductAPI since the same fixture is already defined in conftest.py, and trim the full settings.py to only the testing-relevant overrides.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable code with brief headers and little concept padding, but at ~720 lines it includes some content that could be tightened — e.g. a full settings module and a redundant api_client fixture redefined in TestProductAPI that already exists in conftest.	2 / 3
Actionability	It provides copious concrete, executable, copy-paste-ready code across models, views, serializers, DRF API tests, mocking, and an integration flow with specific assertions.	3 / 3
Workflow Clarity	The Red-Green-Refactor cycle and a numbered checkout flow are present, but there are no explicit validation checkpoints or run→fail→fix→re-run feedback loops for the TDD process, which the rubric caps at 2 for such workflows.	2 / 3
Progressive Disclosure	It is a monolithic single file with no bundle references and no external file split; much of this broad multi-topic reference (factories, coverage, API patterns) could be separated, leaving content that should be split inline.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 names a specific, distinctive niche with several concrete capabilities, but lacks an explicit 'Use when...' trigger clause and uses capability-list phrasing rather than natural user utterances. Adding trigger guidance and natural trigger terms would lift completeness and trigger_term_quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or running tests for a Django project, setting up pytest-django, building factory_boy factories, or testing DRF endpoints.'

Include natural trigger terms users would actually say ('test my Django app', 'write Django tests', 'pytest my Django project') alongside the capability list.

Convert the description to active third-person capability verbs ('Tests Django applications...') to sharpen specificity and avoid the enumeration style.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'TDD 方法论、factory_boy、Mock 模拟、测试覆盖率以及测试 Django REST Framework API' — naming distinct capabilities rather than vague abstractions.	3 / 3
Completeness	It clearly answers what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords ('Django 测试', 'TDD', '测试覆盖率', 'Django REST Framework API') but reads as a capability enumeration, missing common natural variations a user would actually say like 'test my Django app' or 'pytest'.	2 / 3
Distinctiveness Conflict Risk	The niche is specific — Django with pytest, TDD, factory_boy, and DRF — with distinct triggers unlikely to fire for non-Django or non-testing skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (730 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

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

Reviewed: 2 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.