CtrlK
BlogDocsLog inGet started
Tessl Logo

django-tdd

Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs. Use when writing Django or DRF tests with pytest-django, or driving a Django feature test-first.

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A comprehensive, highly actionable catalog of executable Django/DRF testing patterns with clear section organization. Its main weaknesses are redundancy across code blocks and the lack of any progressive-disclosure file splitting for what is a large single-file skill.

Suggestions

Deduplicate the api_client fixture (defined in both conftest.py and TestProductAPI) and consolidate the two test_models.py snippets to tighten conciseness.

Split the large reference material (factory_boy setup, API viewset patterns, coverage config) into files under references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit validation checkpoints to the TDD and integration workflows (e.g., 'run pytest after GREEN; only refactor when all tests pass') to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly code-forward and lean with brief section intros, but contains redundancy (api_client fixture defined in both conftest.py and TestProductAPI; test_models.py shown twice) and minor fluff like the closing 'Tests are documentation' line.

4 / 5

Actionability

Fully executable, copy-paste-ready code across models, views, serializers, API viewsets, mocking, and integration flows, covering the common Django/DRF testing cases concretely.

5 / 5

Workflow Clarity

The Red-Green-Refactor TDD cycle and the 6-step integration checkout flow give clear sequences, though validation checkpoints are implicit rather than called out as explicit feedback loops.

4 / 5

Progressive Disclosure

Well-organized with section headers, but at ~730 lines it is a monolithic single file with no references/scripts/assets bundle and no pointers to split-out reference material, so structure is only moderate.

3 / 5

Total

16

/

20

Passed

Description

96%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.

A strong, third-person description that concretely enumerates capabilities and provides explicit 'Use when' trigger guidance with natural synonyms. The only mild risk is overlap with a generic TDD/pytest skill on the test-first trigger.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs') and when ('Use when writing Django or DRF tests with pytest-django, or driving a Django feature test-first').

5 / 5

Trigger Term Quality

Natural trigger phrases users would say ('writing Django or DRF tests with pytest-django', 'driving a Django feature test-first') with synonyms (Django/DRF, tests/test-first/TDD); file extensions are not applicable to a methodology skill.

5 / 5

Distinctiveness Conflict Risk

Clear Django+DRF+pytest-django niche with distinct triggers, but 'driving a Django feature test-first' could overlap with a generic TDD skill, giving minor conflict risk.

4 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.