django-patterns

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

1.14x

Quality

58%

Does it follow best practices?

Impact

100%

1.14x

Average score across 6 eval scenarios

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/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.

The skill is a thorough, mostly executable Django/DRF pattern reference with good internal structure, but it is held back by verbosity from inlined standard boilerplate, missing validation around batch/destructive operations, and the absence of any reference-file split for a ~700-line body.

Suggestions

Split the detailed code patterns into reference files (e.g., references/models.md, references/drf.md, references/caching.md) and keep SKILL.md as a lean overview with one-level-deep, clearly signaled links.

Trim standard Django boilerplate (full INSTALLED_APPS and MIDDLEWARE lists, default settings blocks) that Claude already knows, keeping only the non-obvious patterns such as the split-settings structure and production security flags.

Add explicit validation/checkpoint steps around batch and destructive operations (e.g., verify counts before bulk_delete, confirm update_fields before bulk_update) so the destructive-operation workflow is not left uncapped.

Dimension	Reasoning	Score
Conciseness	The ~700-line body inlines substantial standard Django boilerplate Claude already knows (full INSTALLED_APPS/MIDDLEWARE lists, complete base/development/production settings, default model fields) and redefines the Product model multiple times across sections, making it noticeably verbose with several padded sections rather than lean.	2 / 5
Actionability	Most sections give concrete, executable code (settings, models, QuerySets, serializers, ViewSets, services, caching, signals, middleware), but examples have minor gaps such as undefined imports (slugify, timezone, logger, Count, env, generic) and referenced-but-undefined models (Cart, Category, Tag, Order, PaymentGateway) that prevent fully copy-paste-ready execution.	4 / 5
Workflow Clarity	The skill is organized as a topical reference rather than a sequenced workflow, and the batch/destructive operations it covers (bulk_create, bulk_update, bulk_delete) include no validation or verification checkpoints, which the rubric caps at 3.	3 / 5
Progressive Disclosure	The body is well-structured with clear section headers and a quick-reference table, but no bundle files exist and all detailed code patterns are inlined in SKILL.md; content that clearly belongs in separate reference files is kept inline, which fits the "structure present but content should be separate" anchor.	3 / 5
	Total	12 / 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 clearly names the Django/DRF domain and many relevant capability areas with natural trigger terms, but it lacks an explicit "Use when..." trigger clause, which caps completeness. It is solid but not exemplary.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger situations (e.g., "Use when building Django web apps, designing DRF APIs, or modeling data with the Django ORM").

Replace slightly padded abstractions ("architecture patterns", "best practices") with more concrete actions such as "design custom QuerySets", "write DRF serializers and ViewSets", or "configure split settings".

Include a few more natural synonyms users say ("serializers", "views", "models", "Django REST Framework") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("REST API design with DRF", "ORM best practices", "caching, signals, middleware") rather than a single vague domain, though terms like "architecture patterns" and "best practices" lean slightly abstract rather than discrete actions, keeping it below a 5.	4 / 5
Completeness	The description gives a clear "what" but has no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3; the "when" is only weakly implied by the listed topics.	3 / 5
Trigger Term Quality	Natural Django-developer terms ("Django", "REST API", "DRF", "ORM", "caching", "signals", "middleware") give good keyword coverage, but it omits common synonyms like "serializers", "views", "models", and the full "Django REST Framework" name, so it is not comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	The Django + DRF niche is mostly distinct from non-Django skills, but the broad topic sweep (architecture, ORM, caching, signals, middleware) creates minor overlap risk with other potential Django-focused skills, so it stops at 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (734 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: docs/ja-JP/skills/django-patterns/SKILL.md
Commit: e04ea0b

Reviewed: 2 days 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.