django-tdd

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

Quality

73%

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 ./skills/django-tdd/SKILL.md

The canonical home for this skill is jbvc/django-tdd

Quality

Content

65%

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

Highly actionable with thorough executable examples, but it is verbose for a SKILL.md and presents everything inline with no progressive disclosure or bundle references. Tightening duplication and splitting detailed catalogs into referenced files would improve it.

Suggestions

Move the factory, model, view, serializer, and API test catalogs into reference files (e.g., references/factories.md, references/api-testing.md) and keep SKILL.md as a concise overview with one-level-deep links to lift progressive_disclosure.

De-duplicate the repeated tests/test_models.py block and trim the DO/DON'T and Quick Reference lists to the non-obvious items only, reducing token cost.

Add an explicit TDD workflow sequence with validation checkpoints (write failing test → run pytest → implement → run again → refactor → run), so the Red-Green-Refactor loop reads as a real feedback loop rather than code comments.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable code without over-explaining known concepts, but at ~720 lines it carries padding — notably duplicated file paths (tests/test_models.py appears twice) — so it could be tightened rather than earning the lean anchor.	2 / 3
Actionability	Provides fully executable, copy-paste-ready artifacts: pytest.ini, test settings, conftest fixtures, factory_boy factories, and complete model/view/serializer/API test classes, matching the executable-code anchor.	3 / 3
Workflow Clarity	The Red-Green-Refactor cycle is illustrated only as code comments rather than a sequenced process, and there are no explicit validation checkpoints or feedback loops (run tests → fix → re-run) for the multi-step TDD workflow.	2 / 3
Progressive Disclosure	Sections are well-organized, but the skill is a monolithic 720-line wall with no bundle files; reference material (factories, API testing patterns, best-practices lists) that should be split into separate files is kept inline.	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, third-person description with strong trigger terms and a clear niche, but it lacks an explicit 'Use when…' trigger clause, which caps completeness. Adding a when-to-use phrase would raise it to full marks.

Suggestions

Append an explicit 'Use when…' clause (e.g., 'Use when writing or testing Django apps, DRF APIs, or setting up pytest-django test infrastructure.') to satisfy the completeness dimension.

Optionally include common phrasings users say ('Django tests', 'pytest Django', 'test DRF serializers') to broaden trigger coverage further.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'testing strategies', 'TDD methodology', 'factory_boy', 'mocking', 'coverage', and 'testing Django REST Framework APIs' — matching the multiple-concrete-actions anchor.	3 / 3
Completeness	It clearly states what the skill does but provides no 'Use when…' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Covers natural terms a user would actually say (Django testing, pytest-django, TDD, factory_boy, mocking, coverage, DRF APIs), giving good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	The description carves a clear Django-testing niche with distinct triggers, making it unlikely to fire 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 (731 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/django-tdd/SKILL.md
Commit: 754b8dd

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.