django-expert
tessl i github:jeffallan/claude-skills --skill django-expertUse when building Django web applications or REST APIs with Django REST Framework. Invoke for Django models, ORM optimization, DRF serializers, viewsets, authentication with JWT.
Review Score
67%
Validation Score
12/16
Implementation Score
42%
Activation Score
90%
Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata |
body_examples | No examples detected (no code fences and no 'Example' wording) |
Implementation
Suggestions 4
Score
42%Overall Assessment
This skill has excellent progressive disclosure with a well-organized reference table, but critically lacks actionable code examples. The content reads more like a role description than executable guidance. The constraints are useful but the absence of concrete Django/DRF code snippets significantly limits its practical value.
Suggestions
- Add executable code examples for key patterns: a model with select_related usage, a DRF serializer with validation, and a viewset with permissions
- Replace the abstract workflow steps with specific commands or code patterns (e.g., 'Run python manage.py makemigrations && python manage.py migrate' for step 2)
- Remove the role-playing framing ('You are a senior Python engineer...') and knowledge reference keyword list - these don't add actionable value
- Add a validation checkpoint in the workflow, such as 'Run tests before committing: pytest --cov'
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary framing ('Senior Django specialist with 10+ years experience') and role-playing setup that Claude doesn't need. The constraints section is useful but could be more compact. The knowledge reference section is just a keyword list with limited value. |
Actionability | 1/3 | The skill provides no executable code examples, only abstract guidance like 'Use select_related/prefetch_related' without showing how. The workflow is high-level description rather than concrete implementation steps. Output templates describe what to provide but don't show examples. |
Workflow Clarity | 2/3 | The core workflow lists 5 steps but they are vague ('Analyze requirements', 'Design models') without specific actions or validation checkpoints. No feedback loops for error handling or verification steps are included. |
Progressive Disclosure | 3/3 | Excellent use of a reference table with clear topics, file paths, and 'Load When' guidance. References are one level deep and well-signaled. The structure appropriately keeps the main skill as an overview pointing to detailed materials. |
Activation
Suggestions 1
Score
90%Overall Assessment
This is a strong skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that it lists components/topics rather than describing concrete actions Claude can perform. Converting the noun list to action phrases would improve specificity.
Suggestions
- Reframe component list as concrete actions: 'Creates Django models, optimizes ORM queries, builds DRF serializers and viewsets, configures JWT authentication' instead of just listing topics.
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (Django, DRF) and mentions specific components (models, ORM optimization, serializers, viewsets, JWT authentication), but reads more like a list of topics than concrete actions. Missing action verbs like 'create', 'optimize', 'configure'. |
Completeness | 3/3 | Explicitly answers both what (Django web apps, REST APIs, models, ORM, serializers, viewsets, JWT auth) and when ('Use when building Django web applications', 'Invoke for Django models...'). Has clear trigger guidance with 'Use when' and 'Invoke for' clauses. |
Trigger Term Quality | 3/3 | Excellent coverage of natural terms users would say: 'Django', 'REST APIs', 'Django REST Framework', 'DRF', 'models', 'ORM', 'serializers', 'viewsets', 'JWT', 'authentication'. These are all terms developers naturally use when working in this domain. |
Distinctiveness Conflict Risk | 3/3 | Highly distinctive with Django-specific terminology (DRF, serializers, viewsets, ORM) that clearly separates it from generic web development or other Python framework skills. Unlikely to conflict with Flask, FastAPI, or general Python skills. |