Use when building Django web applications or REST APIs with Django REST Framework. Invoke when working with settings.py, models.py, manage.py, or any Django project file. Creates Django models with proper indexes, optimizes ORM queries using select_related/prefetch_related, builds DRF serializers and viewsets, and configures JWT authentication. Trigger terms: Django, DRF, Django REST Framework, Django ORM, Django model, serializer, viewset, Python web.
95
92%
Does it follow best practices?
Impact
97%
1.14xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly communicates what the skill does and when to use it. It provides specific concrete actions, comprehensive trigger terms covering both formal names and common abbreviations, and explicit 'Use when' / 'Invoke when' guidance. The description is well-scoped to the Django/DRF ecosystem, making it highly distinctive and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating Django models with proper indexes, optimizing ORM queries using select_related/prefetch_related, building DRF serializers and viewsets, and configuring JWT authentication. | 3 / 3 |
Completeness | Clearly answers both 'what' (creates models, optimizes queries, builds serializers/viewsets, configures JWT auth) and 'when' (building Django web apps or REST APIs, working with Django project files), with explicit 'Use when' and 'Invoke when' clauses plus listed trigger terms. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: Django, DRF, Django REST Framework, Django ORM, Django model, serializer, viewset, Python web, plus file-specific triggers like settings.py, models.py, manage.py. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche around Django and DRF specifically. The mention of Django-specific files (settings.py, models.py, manage.py), Django-specific patterns (select_related/prefetch_related), and DRF-specific concepts (serializers, viewsets) make it very unlikely to conflict with generic Python or web development skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong skill with excellent actionability through a complete, executable example that demonstrates all key constraints. The progressive disclosure via the reference table is well-designed with clear loading conditions. Minor weaknesses include some unnecessary introductory framing and a redundant keyword list, but overall the content is well-structured and practical.
Suggestions
Remove the introductory tagline ('Senior Django specialist...') and the 'Knowledge Reference' keyword list at the bottom—they consume tokens without adding actionable value.
Trim or remove the 'When to Use This Skill' section since it largely duplicates the skill description in the frontmatter.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Senior Django specialist with deep expertise...') and the 'Knowledge Reference' line at the end is just a keyword list that adds little value. The 'When to Use This Skill' section largely duplicates the frontmatter description. However, the code examples and constraints are well-targeted. | 2 / 3 |
Actionability | The minimal working example is fully executable, covering models, serializers, viewsets, and tests with copy-paste ready code. Constraints are specific and concrete (select_related, parameterized SQL, environment variables for secrets). The code demonstrates indexed fields, N+1 prevention, validation, and permissions in a cohesive example. | 3 / 3 |
Workflow Clarity | The core workflow has clear sequencing with explicit validation checkpoints: step 2 includes migration verification before proceeding, step 4 requires endpoint validation before adding auth. The constraints section provides clear guardrails. The workflow is well-suited for the iterative nature of Django development. | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' conditions pointing to topic-specific files one level deep. The SKILL.md serves as a concise overview with a working example, while detailed guidance for models, serializers, viewsets, auth, and testing is appropriately delegated to separate reference files. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
3d95bb1
Table of Contents
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.