django-patterns

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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

The skill is highly actionable with complete, executable code examples, but it is a monolithic inline reference lacking split-out references and validation checkpoints around its batch/destructive operations. Splitting advanced material into bundle files and adding verification steps would raise the weaker dimensions.

Suggestions

Move large reference blocks (full split-settings boilerplate, advanced caching strategies, signal/middleware patterns) into files under references/ and link to them from a concise overview, improving progressive disclosure.

Add explicit validation/verification checkpoints around destructive and batch operations — e.g. verify affected row counts after bulk_update/bulk_delete, or assert OrderItem creation before clearing the cart in the service layer.

Trim full boilerplate lists (INSTALLED_APPS, MIDDLEWARE) to the essential additions and reference Django defaults, tightening conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference code with minimal explanation of concepts Claude already knows, but full boilerplate dumps (complete INSTALLED_APPS and MIDDLEWARE lists, entire settings files) could be tightened or moved out, matching the score-2 anchor.	2 / 3
Actionability	Throughout the document the guidance is fully executable, copy-paste-ready code (serializers, viewsets, QuerySets, managers, services, caching, signals, middleware) rather than pseudocode or abstract description.	3 / 3
Workflow Clarity	This is a pattern reference rather than a sequenced workflow, and the batch/destructive operations (bulk_update, bulk_delete, order creation) lack validation or verification checkpoints, which the rubric caps at 2.	2 / 3
Progressive Disclosure	All content lives inline in one ~700-line SKILL.md with no bundle files or split-out references; content that could be separate (full settings, advanced caching, signal patterns) is inline, matching the score-2 anchor.	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.

The description is specific and distinctive with strong natural trigger terms, but it omits an explicit "Use when..." clause, which limits its completeness score. Adding trigger guidance would round it out.

Suggestions

Append an explicit trigger clause, e.g. "Use when building or refactoring Django apps, designing DRF APIs, or optimizing the ORM, caching, signals, or middleware."

Consider adding common phrasings users say (e.g. "Django REST Framework", "Django models", "Django views") to broaden trigger-term coverage.

Reframe some noun-list capabilities as concrete verbs (e.g. "Design REST APIs with DRF", "Optimize ORM queries") to sharpen specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities across the domain ("architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware") rather than vague actions, matching the score-3 anchor for listing several specific capabilities.	3 / 3
Completeness	Clearly answers "what" via the enumerated capabilities, but there is no explicit "Use when..." trigger clause; per the rubric guideline a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Contains natural developer keywords users would actually say — "Django", "REST API", "DRF", "ORM", "caching, signals, middleware" — giving good coverage of natural terms rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	The Django/DRF niche is clearly delineated 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 (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
Commit: 4130457

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.