Name: django-patterns
Rating: 57.599999999999994 (1 reviews)
Author: affaan-m

django-patterns

Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.

Quality

67%

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

The canonical home for this skill is django-patterns in affaan-m/ECC

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 skill is a dense, actionable Django patterns catalog with strong executable examples, but it is a single monolithic file with no progressive disclosure and lacks validation checkpoints for its batch operations, which caps workflow clarity. Splitting reference material into bundled files and adding validation guidance would materially raise the score.

Suggestions

Move the detailed per-topic code catalogs (serializers, viewsets, caching, signals, middleware) into bundled reference files under references/ and link to them from SKILL.md so the main file stays a lean overview.

Add an explicit validation/checkpoint step to the bulk operations section (e.g. verify counts before/after bulk_update, run migrations/check after schema-affecting changes) to lift workflow clarity above 3.

Remove the duplicated Product model redefinitions across QuerySet/Manager/Indexing sections and fix missing imports ('env', 'slugify', 'timezone', 'logger', 'Count') so examples are fully copy-paste executable.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable code with minimal prose and assumes Claude's Django knowledge, but the Product model is redefined across the QuerySet, Manager, and Indexing sections and the closing 'Remember:...' line is generic, giving minor redundancy that keeps it just below 5.	4 / 5
Actionability	Code examples are largely copy-paste ready and cover the common Django cases (models, serializers, viewsets, caching, signals, middleware, performance), but several examples reference undefined names ('env', 'slugify', 'timezone', 'logger', 'Count') that a user would need to import, leaving minor gaps versus fully executable 5.	4 / 5
Workflow Clarity	Content is organized into clear topical sections with a 'When to Activate' list, but there is no multi-step workflow with validation checkpoints, and the bulk operations section performs batch create/update/delete with no validation step, which per the rubric caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Section headers give reasonable structure, but at 730 lines the skill is a monolithic inlined reference with no bundle files and no 'see X.md' references to split out detail, so content that would belong in separate files is inlined and navigation is single-level only.	3 / 5
	Total	14 / 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.

The description is specific, Django-distinctive, and rich in natural trigger terms, but it lacks an explicit 'Use when...' trigger clause, which caps its completeness. Adding a one-sentence activation clause would lift it into the top band.

Suggestions

Append an explicit activation clause, e.g. 'Use when building or reviewing Django web apps, DRF APIs, or ORM models.'

Swap generic nouns ('patterns', 'best practices') for concrete verbs where possible ('structure projects, design DRF serializers, optimize ORM queries') to push specificity toward 5.

Add common synonyms or qualifiers users might say (e.g. 'Django REST Framework', 'Django ORM') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific Django sub-domains ('REST API design with DRF, ORM best practices, caching, signals, middleware') with broad coverage, though the verbs ('patterns', 'design', 'best practices') are somewhat generic rather than concrete actions, keeping it below a 5.	4 / 5
Completeness	The 'what' is clearly stated (Django architecture patterns, DRF, ORM, caching, signals, middleware), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms a user would say ('Django', 'REST API', 'DRF', 'ORM', 'caching', 'signals', 'middleware') are present with good coverage; falls short of 5 only because no synonyms or file-extension variants are offered, which is a minor gap for a framework skill.	4 / 5
Distinctiveness Conflict Risk	The description carves a clear, distinct niche (Django + DRF + ORM + signals + middleware) with trigger terms unlikely to fire for unrelated skills, giving minimal conflict risk.	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: .kiro/skills/django-patterns/SKILL.md
Commit: d8409a4

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.