django-tdd

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

1.28x

Quality

—

Does it follow best practices?

Impact

96%

1.28x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

A highly actionable, code-rich Django TDD reference that scores well on executable guidance. It loses points on conciseness and progressive disclosure due to its monolithic length and duplicated fixtures, and on workflow clarity for missing explicit validation checkpoints.

Suggestions

Move large reference blocks (serializer/API/integration test suites) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce token load.

Remove duplicated fixtures (the api_client fixture is defined both in conftest.py and redefined in test_api.py) and consolidate the two `tests/test_models.py` sections to tighten conciseness.

Add explicit validation checkpoints to the TDD workflow (e.g. 'run pytest, confirm RED fails for the expected reason, then implement to GREEN') to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is ~720 lines of mostly concrete code with little conceptual padding, but it is voluminous and contains redundancy (e.g. api_client is redefined in test_api.py after being defined in conftest.py, and `tests/test_models.py` appears under two sections), so it is mostly efficient but could be tightened.	2 / 3
Actionability	It provides extensive executable, copy-paste-ready code for fixtures, factories, model/view/serializer/API tests, mocking and integration flows, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	The red-green-refactor loop and setup steps give a sequence, but the document reads as a catalog of test types with no explicit validation/verification checkpoints or feedback loops, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	All content is inline in a single ~720-line SKILL.md with no references/ or other bundle files; detailed sections (serializers, API, integration) that could be split into separate files are inlined, so structure exists but separation is lacking.	2 / 3
	Total	9 / 12 Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description that names concrete tools and natural trigger terms for the Django testing domain. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when writing or running Django tests, setting up pytest-django, building factory_boy fixtures, or testing DRF APIs.'

Lead with the core action verbs (e.g. 'Write and run Django tests...') to make the 'what' read as concrete actions rather than a topic list.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete capabilities — "pytest-django、TDD 方法、factory_boy、模拟、覆盖率以及测试 Django REST Framework API" — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Terms like "Django 测试", "pytest-django", "TDD", "factory_boy", "模拟" and "Django REST Framework" are natural phrases a developer would say when needing this skill, giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	The Django-specific testing niche with named tooling (pytest-django, factory_boy, DRF) is clearly distinct and unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 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: affaan-m/everything-claude-code
Commit: 4130457

Reviewed: about 20 hours 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.