django-patterns

Django架构模式，使用DRF设计REST API，ORM最佳实践，缓存，信号，中间件，以及生产级Django应用程序。

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 body is a highly actionable, well-organized Django/DRF patterns catalog with copy-paste-ready code, but it is a monolithic single file with no progressive disclosure and no sequenced workflows or validation checkpoints around its batch/destructive operations.

Suggestions

Split the catalog into one-level-deep reference files (e.g., models.md, drf.md, caching.md, performance.md) and keep SKILL.md as a concise overview with signaled links, improving progressive disclosure.

Add a brief decision workflow with validation checkpoints around risky operations (e.g., validate before bulk_update, run migrations/check after schema changes) to raise workflow clarity.

Trim code that restates standard Django patterns Claude already knows and remove redundant model redefinitions to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Prose is tight and section-driven (no 'what is Django' filler), but the ~735-line body supplies extensive standard Django/DRF code Claude already knows with some redundancy (Product model re-shown across QuerySet, index, and N+1 sections); not a 3 because the volume exceeds what Claude doesn't already know, and not a 1 because it avoids conceptual explanation.	2 / 3
Actionability	Examples are fully executable, complete with imports, and copy-paste ready across settings, models, serializers, ViewSets, services, caching, signals, and middleware; not below 3 because concrete runnable code dominates over pseudocode.	3 / 3
Workflow Clarity	Content is organized by topic with no sequenced multi-step workflow or validation checkpoints, and the batch/destructive operations (bulk_create/bulk_update/bulk_delete) and transactional service layer include no validation/verification steps, capping this at 2; not a 1 because sections are clearly labeled and ordered.	2 / 3
Progressive Disclosure	No bundle files exist and the entire reference lives inline in one ~735-line SKILL.md with content (DRF, caching, models) that could be split into separate reference files; not a 1 because section headers keep it well-organized rather than a disorganized wall of text, and not a 3 because nothing is offloaded to one-level-deep references.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 scopes a Django-specific niche with strong natural trigger terms, but it lists topic areas rather than concrete actions and omits any explicit 'Use when' trigger guidance, capping completeness at 2.

Suggestions

Reframe the topic nouns as concrete verbs (e.g., 'Design DRF serializers and ViewSets, model business logic in a service layer, optimize ORM queries with select_related/prefetch_related').

Add an explicit 'Use when...' clause, e.g., 'Use when building or reviewing Django/DRF applications, designing models, or implementing caching, signals, or middleware.'

Include common user phrasings like 'Django REST Framework' and 'Django ORM' alongside DRF/ORM to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Django domain and several capability areas ('使用DRF设计REST API', 'ORM最佳实践', '缓存，信号，中间件'), but they are stated as topics/nouns rather than concrete verbs like 'extract, fill, merge', matching the level-2 anchor; not a 3 because no list of multiple distinct concrete actions.	2 / 3
Completeness	It states what the skill covers but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 2; not a 1 because the 'what' is clearly present.	2 / 3
Trigger Term Quality	Contains natural terms a user would say when needing this skill — 'Django', 'DRF', 'REST API', 'ORM', plus caching/signals/middleware — giving good coverage; not below 3 because the core terms are exactly what users invoke.	3 / 3
Distinctiveness Conflict Risk	Django-specific niche with DRF/ORM/middleware triggers is clearly distinguishable and unlikely to fire for non-Django skills; not below 3 because the domain scoping is unambiguous.	3 / 3
	Total	10 / 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/everything-claude-code
Commit: 4130457

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