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

65%

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

65%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 body is a well-organized, mostly executable Django patterns reference, but it is a monolithic 730-line file with no progressive disclosure into reference files and no validation checkpoints around its batch/destructive operations. Splitting deep references and adding verification steps would address the two lowest dimensions.

Suggestions

Move the larger code catalogs (DRF serializers/viewsets, caching strategies, performance optimization) into separate reference files under references/ and link to them from SKILL.md with one-level-deep navigation.

Add validation/verification steps around batch and destructive operations, e.g. a dry-run count before `Product.objects.filter(stock=0).delete()` and a confirmation/re-verify after bulk_update/bulk_create.

Resolve the minor execution gaps (add the missing imports for slugify/timezone/logger/Count, define or note the env() django-environ setup, and include is_featured/created_by on the Product model or remove their use) so examples are fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with brief section headers and little concept padding; not a 5 because of minor redundancy (Meta indexes appear both inside the full Product model and again in the standalone indexing section) and a tutorial-style '# Mal / # Bien' N+1 framing that explains a concept Claude already knows.	4 / 5
Actionability	Concrete, largely copy-pasteable Django code across models, serializers, viewsets, services, caching, signals and middleware; not a 5 because of minor gaps such as undefined imports (slugify, timezone, logger, env, Count), referenced-but-undefined fields (is_featured, created_by), and '# ... campos ...' placeholders.	4 / 5
Workflow Clarity	The skill is a pattern catalog with good topical sections but no sequenced multi-step workflow or validation checkpoints, and destructive/batch operations (bulk delete, payment processing) lack validation feedback loops, capping this at 3 per the rubric guideline.	3 / 5
Progressive Disclosure	No bundle files exist and all ~730 lines are inlined in SKILL.md with reasonable section headers and a quick-reference table; not a 4 because substantial content (DRF patterns, caching strategies, signals/middleware) that clearly belongs in one-level-deep reference files is inlined rather than split out.	3 / 5
	Total	14 / 20 Passed

Description

66%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 Django-distinct with solid natural trigger terms, but it omits any explicit 'Use when...' activation guidance, which caps completeness at 3. Adding a trigger clause would lift the strongest remaining weakness.

Suggestions

Add an explicit 'Use when...' clause in Spanish, e.g. 'Úsalo cuando el usuario construya o revise aplicaciones Django, APIs con DRF, o necesite patrones de ORM/caché/señales/middleware de producción.'

Spell out at least one abbreviation for natural phrasing, e.g. 'Django REST Framework (DRF)', to broaden trigger-term coverage.

Lead with a concrete action verb per area (e.g. 'Diseña', 'Implementa', 'Optimiza') rather than noun phrases to raise specificity from 4 toward 5.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete capability areas — 'arquitectura Django', 'diseño de API REST con DRF', 'buenas prácticas de ORM', 'caché, señales, middleware' — with only minor gaps; not a 5 because they are topic areas rather than fully fleshed concrete actions.	4 / 5
Completeness	Clearly states what the skill covers but contains no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline; not a 4 because 'when' is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	Natural terms a Django user would say ('Django', 'API REST', 'DRF', 'ORM', 'caché', 'señales', 'middleware') are present with good coverage; not a 5 because full-name synonyms (e.g., 'Django REST Framework') and variations are missing.	4 / 5
Distinctiveness Conflict Risk	Anchored to a clear Django niche with distinct triggers and minimal conflict with non-Django skills; not a 5 because it is broad within Django (DRF, ORM, cache, signals, middleware), so it could overlap with more focused sibling Django skills.	4 / 5
	Total	15 / 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/everything-claude-code
Path: docs/es/skills/django-patterns/SKILL.md
Commit: d8409a4

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