django-tdd

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

1.24x

Quality

80%

Does it follow best practices?

Impact

98%

1.24x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 content is highly actionable and token-efficient, packed with executable pytest-django/factory_boy/DRF examples and clear sequencing. Its main weakness is monolithic structure: large code references that would benefit from being split into separate files are inlined in SKILL.md.

Suggestions

Move the larger code blocks (factories, full model/view/API test suites, coverage tables) into reference files under references/ and link to them with clearly signaled one-level-deep pointers.

Add an explicit feedback loop to the TDD workflow (e.g. "on failure: read the assertion error, fix the code or test, re-run until green") to strengthen validation checkpoints.

Add a short "Quick start" section at the top that points to the setup, factories, and per-layer test sections so navigation is front-loaded.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable code with terse comments and avoids explaining concepts Claude already knows; every section earns its tokens.	5 / 5
Actionability	It provides copy-paste-ready conftest fixtures, factory_boy factories, and full model/view/serializer/API/mocking test examples plus concrete commands like `pytest --cov=apps --cov-report=html`.	5 / 5
Workflow Clarity	The Red-Green-Refactor cycle and the integration flow are clearly sequenced with assertion checkpoints, but there is no explicit validate→fix→retry feedback loop for the test workflow itself.	4 / 5
Progressive Disclosure	The skill is well over 50 lines and inlines a large volume of material (factories, full test suites, coverage tables) that could live in separate reference files, with no bundle references signaled; section headers provide some structure.	3 / 5
	Total	17 / 20 Passed

Description

75%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 clearly distinct, naming concrete tools and the testing domain well, but it omits an explicit "when to use" trigger clause, which caps its completeness. Adding a "Use when..." sentence would raise the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or configuring tests for a Django project, including DRF APIs, with pytest-django and factory_boy."

Include natural user phrasings/synonyms such as "write tests for Django", "test Django REST APIs", and the "DRF" abbreviation to broaden trigger-term coverage.

Lead with the core action (e.g. "Writes and configures Django tests...") in third person so the "what" is immediately concrete before listing the toolset.

Dimension	Reasoning	Score
Specificity	"Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs" names the domain plus multiple concrete tools and techniques, giving comprehensive coverage.	5 / 5
Completeness	It clearly states "what" the skill does but lacks any explicit "Use when..." trigger clause; per the judging guidelines a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms like "Django testing", "pytest-django", "mocking", "coverage", and "Django REST Framework" are present, but a few common phrasings users would say (e.g. "write tests for Django", "DRF") are missing.	4 / 5
Distinctiveness Conflict Risk	The Django-testing niche is clearly scoped with distinct triggers (pytest-django, factory_boy, DRF), giving minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 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: affaan-m/ECC
Path: docs/ja-JP/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.