jbvc/django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
56
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
47%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 reads as a topic list rather than a functional skill description — it names relevant Django concepts but lacks action verbs describing what the skill actually does and has no 'Use when...' clause. The trigger terms are strong for Django developers but the absence of explicit trigger guidance and concrete actions significantly weakens its utility for skill selection.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Django project structure, DRF serializers, queryset optimization, or deploying Django to production.'
Rewrite with action verbs in third person, e.g., 'Guides Django architecture decisions, designs REST APIs with Django REST Framework, optimizes ORM queries, and configures caching, signals, and middleware for production-grade applications.'
Clarify scope boundaries to reduce overlap, e.g., distinguish from general Python or general REST API skills by emphasizing Django-specific patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Django) and lists several specific areas like REST API design with DRF, ORM best practices, caching, signals, and middleware, but these are topic areas rather than concrete actions (no verbs describing what the skill does). | 2 / 3 |
Completeness | Describes 'what' at a topic level but completely lacks any 'Use when...' clause or explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also more of a topic list than clear capability description, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Django', 'REST API', 'DRF', 'ORM', 'caching', 'signals', 'middleware' — these are terms developers naturally use when seeking Django help. | 3 / 3 |
Distinctiveness Conflict Risk | Django-specific terms like DRF, ORM, signals, and middleware provide some distinctiveness, but 'REST API design', 'caching', and 'production-grade apps' are generic enough to overlap with non-Django web framework skills. | 2 / 3 |
Total | 8 / 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 dumped into a single file. While the code examples are high quality and executable, the document is far too verbose for a skill file—most content is standard Django patterns that Claude already knows. It lacks any workflow guidance, validation steps, or progressive disclosure structure, making it a poor use of context window space.
Suggestions
Reduce to a concise overview (under 100 lines) covering only non-obvious patterns and project-specific conventions, with references to separate files like MODELS.md, DRF.md, CACHING.md for detailed examples.
Remove standard Django boilerplate that Claude already knows (default settings, basic model fields, standard middleware configuration) and focus on project-specific decisions and anti-patterns to avoid.
Add workflow sections with clear sequencing for common multi-step tasks like 'Setting up a new app', 'Adding a new API endpoint', or 'Implementing caching' with validation checkpoints.
Add a quick-reference decision tree or flowchart for when to use each pattern (e.g., when to use select_related vs prefetch_related, when to use signals vs service layer) rather than just listing all patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~600+ lines. Includes extensive boilerplate code that Claude already knows (standard Django settings, basic model definitions, standard middleware patterns). Much of this is standard Django documentation content rather than novel patterns or project-specific guidance. The split settings example alone is ~60 lines of mostly default Django configuration. | 1 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. Concrete patterns with real model definitions, serializers, viewsets, caching implementations, and middleware examples. Every section provides working Python code rather than pseudocode or abstract descriptions. | 3 / 3 |
Workflow Clarity | No multi-step workflows are defined. The skill is a reference catalog of patterns with no sequencing, validation checkpoints, or process flows. There's no guidance on when to apply which pattern, no migration workflow, no deployment steps, and no validation/verification steps for any of the operations described. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline in a single massive document. Given the breadth of topics (models, DRF, caching, signals, middleware, performance), this should be split into separate reference files with a concise overview in the main skill file. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 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 | 10 / 11 Passed | |
Reviewed
Table of Contents