django-patterns

Patrones de arquitectura Django, diseño de API REST con DRF, buenas prácticas de ORM, caché, señales, middleware y aplicaciones Django de nivel producción.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/es/skills/django-patterns/SKILL.md

Quality

Content

50%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 well-organized but monolithic Django pattern reference: the code is concrete and mostly actionable, yet it duplicates standard Django/DRF knowledge Claude already has, contains several duplicated sections, and inlines ~730 lines that belong in separate reference files. Batch/destructive operations lack validation steps.

Suggestions

Split the body into one-level-deep reference files (e.g., references/models.md, references/drf.md, references/cache-signals-middleware.md, references/performance.md) and keep SKILL.md as a concise overview with clearly signaled links, cutting the main file to a fraction of its size.

Remove content Claude already knows and deduplicate: drop the second low-level cache example ('Caché de QuerySet'), the repeated Meta.indexes block, and boilerplate signal/middleware stubs, keeping only non-obvious production guidance.

Add validation/feedback steps around the bulk operations section (e.g., verify counts before/after bulk_update, wrap delete in a transaction, test after bulk changes) so batch and destructive operations cannot silently fail.

Fix undefined symbols so examples are copy-paste ready: define/import `env` (django-environ or os.environ), `slugify`, `timezone`, `logger`, and `generic`.

Dimension	Reasoning	Score
Conciseness	A ~730-line inline catalog largely restating standard Django/DRF knowledge Claude already has (AbstractUser boilerplate, ModelSerializer/ViewSet patterns, post_save signals, middleware stubs), with duplicated sections ("Caché de Bajo Nivel" vs "Caché de QuerySet" are the same pattern; "Indexación de Base de Datos" repeats the Meta.indexes already shown in Product). Fits anchor 2 ('noticeably verbose; several unnecessary... padded sections'), not 3 — the bulk of the file adds little beyond what Claude knows. Not 1 because the prose is not tutorial-style explanatory fluff; it is dense reference code.	2 / 5
Actionability	Concrete, mostly executable code throughout (settings split, custom QuerySet/Manager, serializers, ViewSets, service layer, caching). Minor gaps keep it from 5: `env()` is used with no import/definition in settings, `slugify`, `timezone`, `logger` and `generic` are undefined, and `Cart`/`PaymentGateway` are referenced but never defined. Not 3 because the code is real and complete-looking rather than pseudocode or high-level hints.	4 / 5
Workflow Clarity	Well-organized topical sections, but it is a pattern catalog with no multi-step workflow or validation checkpoints, and it includes batch/destructive operations (bulk_create, bulk_update, `filter(stock=0).delete()`) with no validation or feedback loop, capping this dimension at 3 per the scoring notes. Not 2 because the section organization is coherent and each pattern is internally well-sequenced.	3 / 5
Progressive Disclosure	Clear section headers organize the material, but there are no bundle files at all (no references/, scripts/, assets/) — the entire ~730-line reference body is inlined in SKILL.md, which matches anchor 3 ('some structure... content that should be separate is inline'). Not 2 because the structure is real and navigable; not 4 because nothing is split out into separate files where it clearly belongs.	3 / 5
	Total	12 / 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.

A specific, well-scoped Django/DRF description with good natural trigger terms and a clear niche. Its main weakness is the complete absence of a 'when to use' clause, which caps completeness and leaves triggering to keyword inference.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Usar cuando se construyan aplicaciones Django, se diseñen APIs con Django REST Framework, o se trabaje con modelos, caché, señales o middleware de Django.'

Spell out 'Django REST Framework' alongside 'DRF' and add common trigger words users naturally say ('modelos', 'serializers', 'proyecto Django', 'migraciones') to improve keyword coverage.

Use third-person concrete verbs ('Diseña APIs REST con DRF', 'Optimiza consultas del ORM') instead of topic nouns to strengthen the specificity of the capability list.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("diseño de API REST con DRF", "buenas prácticas de ORM", "caché, señales, middleware") beyond just naming the domain. Not 5 because these are topic nouns rather than concrete actions, and coverage has gaps (e.g., testing, deployment, project setup).	4 / 5
Completeness	The "what" is clear ("Patrones de arquitectura Django... aplicaciones Django de nivel producción") but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. Not 2 because the "what" is specific and multi-faceted.	3 / 5
Trigger Term Quality	Contains natural terms users would say: "Django", "DRF", "API REST", "ORM", "caché", "señales", "middleware". Not 5 because common variations are missing ("Django REST Framework" spelled out, "modelos", "serializers", "proyecto Django").	4 / 5
Distinctiveness Conflict Risk	Clear niche ("Django", "DRF", "ORM") with distinct triggers and minimal conflict risk against non-Django skills. Not 4 because the term set is unambiguously Django-specific, not merely 'mostly distinct'.	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 (735 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/es/skills/django-patterns/SKILL.md
Commit: c70874f

Reviewed: 1 day 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.