django-patterns

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

Quality

31%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-CN/skills/django-patterns/SKILL.md

Quality

Discovery

32%

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 essentially a comma-separated list of Django-related topics without action verbs or explicit trigger guidance. While it covers a reasonable breadth of Django concepts, it lacks the 'Use when...' clause critical for skill selection and reads more like a course syllabus than an actionable skill description. The Chinese language is fine but the content needs restructuring to be effective for skill matching.

Suggestions

Add an explicit 'Use when...' clause, e.g., '当用户需要构建Django项目、设计REST API、优化数据库查询或配置Django中间件/信号/缓存时使用'

Convert the topic list into concrete action phrases, e.g., '设计Django REST Framework API端点，优化ORM查询性能，配置缓存策略和中间件管道'

Add common user-facing trigger terms and file/framework references like 'Django REST Framework', 'models.py', 'views.py', 'serializers', 'settings.py', 'queryset optimization'

Dimension	Reasoning	Score
Specificity	Names the domain (Django) and lists several specific areas like DRF REST API design, ORM best practices, caching, signals, middleware, and production-grade apps. However, it reads more like a topic list than concrete actions — it doesn't use action verbs like 'design', 'implement', 'configure'.	2 / 3
Completeness	The description only addresses 'what' (Django-related topics) but completely lacks any 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also only a topic list rather than clear capability statements, this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Django', 'DRF', 'REST API', 'ORM', 'caching', 'signals', 'middleware' which users might mention. However, it misses common variations like 'Django REST Framework' (spelled out), 'database queries', 'views', 'serializers', 'models', or 'deployment'.	2 / 3
Distinctiveness Conflict Risk	The Django focus provides some distinctiveness, but the broad scope covering architecture, APIs, ORM, caching, signals, and middleware could overlap with general Python skills, web development skills, or API design skills. It's somewhat specific to Django but covers so many sub-topics it could conflict with more focused skills.	2 / 3
	Total	7 / 12 Passed

Implementation

29%

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

This skill is essentially a Django/DRF cheat sheet that dumps hundreds of lines of boilerplate code Claude already knows how to produce. While the code examples are high quality and executable, the content massively wastes token budget by explaining standard Django patterns without any project-specific constraints, novel techniques, or workflow guidance. It lacks any sequential process, validation steps, or progressive disclosure structure.

Suggestions

Reduce content by 80%+ - remove standard Django patterns Claude already knows (basic model definitions, standard serializer patterns, N+1 explanations) and focus only on project-specific conventions or non-obvious decisions.

Add workflow sequences with validation checkpoints, e.g., 'Setting up a new app: 1. Create app structure → 2. Register in settings → 3. Run makemigrations → 4. Verify migration file → 5. Run migrate'.

Split into multiple files: keep SKILL.md as a concise overview with links to separate files like MODELS.md, DRF_PATTERNS.md, CACHING.md, PERFORMANCE.md.

Replace generic examples with project-specific constraints and conventions that Claude wouldn't know by default (e.g., specific naming conventions, required base classes, deployment-specific configurations).

Dimension	Reasoning	Score
Conciseness	Extremely verbose - over 500 lines of code that Claude already knows how to write. Explains basic Django concepts (settings splitting, model Meta classes, basic serializers, N+1 queries) that Claude is deeply familiar with. The entire file reads like a Django tutorial rather than novel, project-specific guidance.	1 / 3
Actionability	The code examples are fully executable, concrete, and copy-paste ready. Serializers, ViewSets, middleware, signals, and service layer patterns all include complete, runnable code with proper imports and realistic field configurations.	3 / 3
Workflow Clarity	There are no sequenced workflows, no validation checkpoints, and no step-by-step processes. The content is a collection of code patterns without guidance on when to apply them, in what order to set things up, or how to verify correctness. For a skill covering project setup and production deployment patterns, this is a significant gap.	1 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. All content is inline - the settings examples, model patterns, DRF patterns, caching, signals, and middleware could each be separate referenced files. No navigation structure beyond flat headings.	1 / 3
	Total	6 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: affaan-m/everything-claude-code
Commit: 5df943e

Reviewed: about 18 hours 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.