django-patterns

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

1.14x

Quality

61%

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

53%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 dense, largely executable Django pattern reference with good topic structure and no padding of concepts Claude already knows, but it is entirely inlined at 733 lines with no progressive disclosure to reference files, contains duplicated sections, and omits validation guidance for its batch operations. Strongest as a quick-lookup catalog; weakest as an organized, navigable skill bundle.

Suggestions

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

Remove duplication in progressive disclosure's wake and conciseness: merge the low-level caching and QuerySet caching sections (identical pattern) and consolidate the three repeated Product model/index definitions into one canonical example.

Add validation/verification steps around the batch operations section (e.g., verifying counts or wrapping bulk_update/delete in a transaction with a dry-run check) so workflow_clarity can rise above the batch-operation cap of 3.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes Django competence, but there is noticeable duplication: the low-level caching and QuerySet caching sections repeat the identical cache.get/cache.set pattern, and the Product model with Meta.indexes is defined in three separate sections. This matches 'mostly efficient but includes some unnecessary content that could be tightened' rather than the minor-trim level of 4.	3 / 5
Actionability	Nearly all guidance is concrete, executable code (split settings, custom QuerySet, serializers, ViewSet, service layer, middleware). Minor gaps keep it below 5: 'SECRET_KEY = env(...)' with no environ import/setup, 'slugify' used in Product.save without import, and 'Count'/'timezone'/'logger' used without imports in the caching and middleware snippets.	4 / 5
Workflow Clarity	This is a pattern catalog organized by topic with a clear activation section ('いつ有効化するか'), not a sequenced workflow, so no explicit step sequence or validation checkpoints exist. The batch operations section (bulk_create, bulk_update, bulk delete via 'Product.objects.filter(stock=0).delete()') has no validation/verification steps, which caps workflow clarity at 3 per the rubric's destructive/batch guidance.	3 / 5
Progressive Disclosure	A monolithic 733-line SKILL.md with no bundle files (references/, scripts/, assets/ are absent) and zero references to separate files; entire detailed catalogs (serializers, ViewSets, four caching strategies, middleware) that clearly belong in reference files are fully inlined. Section headers exist, but with no references at all this fits anchor 2 ('content that clearly belongs in separate files is inlined') better than anchor 3, which presumes references are present.	2 / 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, distinctive description that names six concrete Django domains with good natural trigger terms, but it omits any 'when to use' guidance, capping completeness. Adding a 'Use when...' clause with explicit trigger phrases (e.g., 'Use when building or refactoring Django apps, designing DRF endpoints, or optimizing ORM queries') would make it fully strong.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g., 'Use when building or refactoring Django applications, designing Django REST Framework APIs, or optimizing ORM queries, caching, signals, or middleware.'

Spell out 'Django REST Framework' at least once and add common user phrases like 'models', 'serializers', and 'views' to broaden trigger-term coverage.

Convert topic nouns into concrete actions (e.g., 'Design REST APIs with DRF, optimize ORM queries, implement caching, signals, and middleware') to sharpen specificity.

Dimension	Reasoning	Score
Specificity	It lists several specific areas — 'REST API design with DRF', 'ORM best practices', 'caching, signals, middleware' — matching anchor 4 ('lists several specific actions; minor gaps'). Not 5 because these are topic nouns rather than concrete actions (no verbs like 'design', 'implement'), and not 3 because coverage spans six-plus distinct concrete areas with only minor gaps.	4 / 5
Completeness	It has a clear, comprehensive 'what' (Django architecture, DRF API design, ORM, caching, signals, middleware) but no 'Use when...' clause or equivalent trigger guidance at all, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good keyword coverage with natural terms users would say ('Django', 'REST API', 'DRF', 'ORM', 'caching', 'middleware') — matching anchor 4. Not 5 because common variations are missing: 'Django REST Framework' is never spelled out, and frequent user phrases like 'models', 'views', 'serializers', or 'migrations' are absent.	4 / 5
Distinctiveness Conflict Risk	It occupies a clear, well-defined niche — Django/DRF application development — with distinct trigger terms ('Django', 'DRF', 'ORM', 'signals') unlikely to fire for non-Django skills, matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').	5 / 5
	Total	16 / 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: 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.