django-tdd

Django 测试策略，包括 pytest-django、TDD 方法、factory_boy、模拟、覆盖率以及测试 Django REST Framework API。

1.28x

Quality

70%

Does it follow best practices?

Impact

96%

1.28x

Average score across 3 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/django-tdd/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The body is a rich, mostly-executable Django TDD reference with strong actionability and clear workflows, but it is a large monolithic file with no progressive disclosure and a few duplicated/undefined-fixture gaps. Splitting detailed material into referenced bundle files would notably improve it.

Suggestions

Move the large factory definitions and full per-layer test suites into referenced bundle files (e.g. references/factories.md, references/api-tests.md), keeping SKILL.md a concise overview with one-level-deep links.

Remove the duplicate tests/test_models.py block and the redundant api_client fixture in TestProductAPI (already provided by conftest) to tighten conciseness.

Define or stub the fixtures referenced but not shown (category, product, order, TagFactory) so every code example is runnable as written.

Dimension	Reasoning	Score
Conciseness	Almost entirely executable code with minimal prose padding and no re-explanation of concepts Claude already knows; minor inefficiencies remain (a duplicate tests/test_models.py block and a redundant api_client fixture redefined inside TestProductAPI despite existing in conftest).	4 / 5
Actionability	Provides copy-paste-ready pytest config, settings, conftest fixtures, factories, and full test classes across models/views/serializers/API/integration; minor gaps exist where undefined fixtures (category, product, order, TagFactory) are referenced.	4 / 5
Workflow Clarity	The red-green-refactor TDD loop and the numbered 6-step checkout integration flow give clear sequences with assertion-based checkpoints; general best-practice do/don't lists are present but no explicit validate-fix-retry feedback loop is spelled out.	4 / 5
Progressive Disclosure	Section headers organize the content well and a quick-reference table aids navigation, but with no bundle files the ~730-line body is entirely inline monolithic content that could be split into referenced files (factories, API reference, full test suites).	3 / 5
	Total	15 / 20 Passed

Description

70%Weight 40%Scale 1-5

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 and well-targeted to Django testing with concrete tooling, but it omits any explicit use-when trigger guidance, which caps its completeness. Trigger-term coverage is strong but could add a few synonyms.

Suggestions

Add an explicit 'Use when ...' trigger clause (e.g. 'Use when writing or running Django/DRF tests, setting up pytest-django, or building test factories') to raise completeness.

Include a couple of natural synonyms/users' phrases such as the English 'test', 'fixtures', or 'test coverage' alongside the Chinese terms.

Reframe a few tool names as concrete actions (e.g. 'write TDD tests', 'build factory_boy factories', 'measure coverage') to push specificity toward 5.

Dimension	Reasoning	Score
Specificity	Names the Django-testing domain and several specific concrete elements (pytest-django, TDD, factory_boy, mocking, coverage, DRF API testing), but these are tool/topic names rather than verb-based actions, leaving minor coverage gaps.	4 / 5
Completeness	It clearly states 'what' (Django testing strategy across named areas) but provides no explicit 'when'/Use-when trigger clause, so per the guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say (Django, 测试/testing, pytest-django, TDD, factory_boy, 模拟/mocking, 覆盖率/coverage, Django REST Framework API), though a few natural synonyms (e.g. the English word 'test', 'fixtures') are absent.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (Django + pytest-django + factory_boy + DRF testing) with distinct triggers and minimal overlap risk against generic pytest or Python skills.	5 / 5
	Total	16 / 20 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: affaan-m/ECC
Path: docs/zh-CN/skills/django-tdd/SKILL.md
Commit: e04ea0b

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.