tdg-personal/django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
49
49%
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 provides a reasonable list of Django-related topics and includes good trigger keywords, but it reads more like a tag cloud than an actionable skill description. It lacks concrete action verbs describing what the skill does and entirely omits a 'Use when...' clause, making it difficult for Claude to know precisely when to select this skill over others.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Django project structure, DRF serializers/viewsets, Django ORM queries, or deploying Django to production.'
Replace topic nouns with concrete action phrases, e.g., 'Designs Django REST APIs with DRF serializers and viewsets, optimizes ORM queries, configures caching strategies, implements custom middleware and signals.'
Ensure the description uses third-person verb phrases throughout (e.g., 'Guides architecture decisions for production-grade Django applications') to match expected voice conventions.
| 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 like 'create', 'configure', 'optimize'). | 2 / 3 |
Completeness | Describes 'what' at a topic level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak (topics not actions), warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Django', 'REST API', 'DRF', 'ORM', 'caching', 'signals', 'middleware', and 'production-grade'. These cover many common terms a developer would use when seeking Django help. | 3 / 3 |
Distinctiveness Conflict Risk | Django-specific terms like DRF, signals, and middleware provide some distinctiveness, but broad terms like 'REST API design', 'caching', and 'production-grade apps' could overlap with general web development or other framework-specific 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 with high-quality, executable code examples but severe issues with conciseness and organization. It dumps extensive boilerplate and standard Django patterns that Claude already knows, without any workflow guidance or progressive disclosure. The content would benefit enormously from being split into referenced sub-files and trimmed to only include non-obvious patterns and project-specific conventions.
Suggestions
Drastically reduce content to only non-obvious patterns and project-specific conventions—remove standard Django boilerplate (default settings, basic model fields, standard middleware setup) that Claude already knows.
Split into multiple files: a concise SKILL.md overview with references to separate files like MODELS.md, DRF_PATTERNS.md, CACHING.md, and PERFORMANCE.md.
Add workflow sequences with validation checkpoints, e.g., a step-by-step process for setting up a new Django app, running migrations, or deploying to production with verification steps.
Replace the exhaustive code examples with brief, targeted snippets showing only the non-obvious parts (e.g., just the custom QuerySet chaining pattern, not the full model definition).
| 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 shown. | 1 / 3 |
Progressive Disclosure | Monolithic wall of text with all content inline. No references to external files for detailed patterns. The entire content (~600+ lines) is in a single file with no progressive disclosure structure. Topics like DRF patterns, caching strategies, and model design could each be separate referenced 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 | |
Reviewed
Table of Contents