django-patterns

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/django-patterns/SKILL.md

Quality

Content

57%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 content is a thorough, executable Django pattern reference with strong actionability, but it is a monolithic catalog lacking procedural sequencing and validation checkpoints for its batch/destructive operations, and it does not use progressive disclosure despite its volume.

Suggestions

Add validation/verification steps to the batch and destructive operations (e.g., verify counts after bulk_update, confirm before bulk delete, check transaction outcomes) to lift workflow clarity above the cap.

Move large reference blocks (settings variants, serializer catalog, caching strategies) into separate files under ./references/ and link to them from SKILL.md to apply progressive disclosure.

Remove redundant redefinitions of the Product model and the duplicate '快速参考' table content to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code with little explanatory prose, but it repeats concepts (the Product model is redefined multiple times, index/field examples recur) and the '快速参考' table restates section content, so it could be tightened.	3 / 5
Actionability	It provides extensive copy-paste-ready code across settings, models, QuerySets, serializers, ViewSets, services, caching, signals, and middleware covering common cases, but some blocks omit imports (slugify, timezone, Count, env, generic, logger) and include stubs ('Email sending logic / pass').	4 / 5
Workflow Clarity	This is a topic-organized pattern catalog rather than a sequenced workflow, and it covers batch/destructive operations (bulk_create/update/delete, transaction.atomic, payment processing) with no validation or verification checkpoints; per the rubric, missing validation for such operations caps workflow clarity at 3.	3 / 5
Progressive Disclosure	It is a ~730-line monolithic catalog with clear section headers but no external references, and large blocks (settings, serializers, caching) that would benefit from being split into separate files are inlined, matching the anchor where content that should be separate is inline with some structure.	3 / 5
	Total	13 / 20 Passed

Description

61%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 scopes the skill to production Django development across several concrete concerns and is fairly distinctive, but it lacks an explicit 'Use when...' trigger clause and frames capabilities as domains rather than discrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building Django web apps, designing DRF APIs, or working with ORM, caching, signals, or middleware.'

Reframe domains as concrete actions (e.g., 'Design REST APIs with DRF, optimize ORM queries, configure caching') instead of noun phrases like 'ORM最佳实践'.

Include common synonyms/extensions users say naturally (e.g., 'Django REST Framework', ' serializers', ' .py') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	It names several concrete domains ("使用DRF设计REST API", "ORM最佳实践", "缓存，信号，中间件") but describes them as areas rather than discrete actions, matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	A clear "what" is given (architecture patterns across multiple Django concerns), but there is no "Use when..." trigger clause; per the rubric guidelines, a missing explicit trigger guidance caps completeness at 3.	3 / 5
Trigger Term Quality	Natural terms users would say are present ("Django", "DRF", "REST API", "ORM", "缓存", "信号", "中间件") with good coverage, though some common synonyms and variations are missing.	4 / 5
Distinctiveness Conflict Risk	Django-specific triggers (DRF, ORM, signals, middleware) make it mostly distinct with only minor overlap risk against other Django/web skills.	4 / 5
	Total	14 / 20 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
Path: docs/zh-CN/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.