django-patterns
Django架构模式，使用DRF设计REST API，ORM最佳实践，缓存，信号，中间件，以及生产级Django应用程序。
34
31%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-CN/skills/django-patterns/SKILL.mdQuality
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 provides a reasonable topic-level overview of Django-related capabilities but reads as a comma-separated list of topics rather than a well-structured skill description. It critically lacks any 'Use when...' clause to guide skill selection, and the capabilities are stated as topics rather than concrete actions. The Chinese language is fine but the content needs more structure and explicit trigger guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Django project architecture, building REST APIs with Django REST Framework, optimizing Django ORM queries, or deploying Django applications to production.'
Convert the topic list into concrete action phrases, e.g., 'Designs REST APIs using Django REST Framework, optimizes ORM queries, implements caching strategies, configures middleware and signals for Django applications.'
Include common natural language trigger terms users might say, such as 'Django project', 'Django views', 'serializers', 'Django deployment', 'Django database', 'Django performance'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Django) and lists several specific areas like DRF REST API design, ORM best practices, caching, signals, middleware, and production-grade Django apps. However, it reads more like a topic list than concrete actions — it doesn't use action verbs like 'design', 'implement', or 'configure' consistently. | 2 / 3 |
Completeness | The description addresses 'what' (Django architecture patterns and 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 somewhat weak (topic list rather than clear capabilities), a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'Django', 'DRF', 'REST API', 'ORM', 'caching', 'signals', 'middleware' that users might mention. However, it misses common variations and natural language terms users might say (e.g., 'Django project', 'Django views', 'serializers', 'database queries', 'Django deployment'). | 2 / 3 |
Distinctiveness Conflict Risk | The Django + DRF focus provides some distinctiveness, but the broad scope covering architecture, ORM, caching, signals, and middleware could overlap with general Python skills, web development skills, or database skills. It's somewhat specific to Django but not sharply delineated. | 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 cookbook dumped into a single file. While the code examples are high-quality and executable, the document is far too verbose for a skill file—it explains patterns Claude already knows well and provides extensive boilerplate that adds little value. It lacks any workflow structure, validation steps, or progressive disclosure, making it a poor fit for the SKILL.md format.
Suggestions
Reduce content to ~50-80 lines focusing only on project-specific conventions and non-obvious patterns (e.g., the specific project structure, naming conventions, service layer boundaries) rather than standard Django/DRF boilerplate.
Split detailed examples into separate bundle files (e.g., MODELS.md, DRF_PATTERNS.md, CACHING.md) and reference them from a concise overview in SKILL.md.
Add workflow sequences with validation checkpoints, such as: 'Creating a new app: 1. Create app → 2. Register in settings → 3. Add URLs → 4. Run makemigrations → 5. Verify migration file → 6. Run migrate'.
Remove explanatory comments that state the obvious (e.g., '# Separate query for each product', 'Create profile when user is created') and trust Claude's existing Django knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines. Much of this is standard Django boilerplate that Claude already knows (settings configuration, basic model definitions, standard DRF patterns). The split settings example alone is ~60 lines of configuration Claude could generate from a one-line instruction. Comments like 'Custom user model extending AbstractUser' and 'Return only active products' explain the obvious. | 1 / 3 |
Actionability | All code examples are concrete, executable, and copy-paste ready. Includes complete model definitions, serializers, viewsets, middleware, caching patterns, and service layer examples with proper imports and realistic field configurations. | 3 / 3 |
Workflow Clarity | There are no sequenced workflows or validation checkpoints. The skill is a reference catalog of patterns rather than a guide through any multi-step process. There's no guidance on order of operations for setting up a project, no migration workflow, no deployment checklist, and no validation/verification steps for any of the patterns shown. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline in a single massive document with no bundle files to support it. Content like the full settings configuration, complete serializer examples, and detailed middleware code should be split into separate reference files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%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
928076c
- Reviewed
Table of Contents
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.