Scaffold a production-ready Django 5.x project with REST Framework, split settings, apps structure, and pytest-django.
66
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./backend-python/django-project-starter/SKILL.mdQuality
Discovery
50%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 excels at specificity by naming exact technologies and versions (Django 5.x, REST Framework, pytest-django) and has a clear distinctive niche. However, it critically lacks any 'Use when...' guidance, which means Claude won't know when to select this skill from a large skill library. The trigger terms could also be expanded to include common user phrasings.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to start a new Django project, create a Django REST API, or scaffold a Django application'
Include common user variations of trigger terms: 'DRF', 'Django project setup', 'new Django app', 'Django boilerplate', 'Django starter'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scaffold a production-ready Django 5.x project' with specific components including 'REST Framework, split settings, apps structure, and pytest-django'. | 3 / 3 |
Completeness | Clearly describes WHAT it does (scaffold Django project with specific components) but completely lacks a 'Use when...' clause or any explicit trigger guidance for WHEN Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Contains good technical keywords like 'Django 5.x', 'REST Framework', 'pytest-django', but missing common user variations like 'DRF', 'Django project', 'new Django app', 'start Django', or 'create Django'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Django 5.x with a particular stack (REST Framework, split settings, pytest-django). Unlikely to conflict with other skills due to the specific technology combination. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a highly actionable Django starter skill with excellent, production-ready code examples covering the full stack from settings to tests. However, it's verbose for a skill file, lacking validation checkpoints in the workflow, and would benefit from splitting advanced integration topics into separate reference documents.
Suggestions
Add validation checkpoints after key steps (e.g., 'Verify migrations applied: python manage.py showmigrations' or 'Test server starts without errors before proceeding')
Split integration notes (Docker, Celery, Channels, CI) into a separate INTEGRATIONS.md file and reference it from the main skill
Remove explanatory phrases Claude already knows (e.g., 'Changing later is painful', 'Keep apps small and focused') to improve conciseness
Add error recovery guidance for common scaffold failures (e.g., database connection issues, missing dependencies)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbose sections. The 'Key Conventions' section explains concepts Claude likely knows (e.g., 'Changing later is painful' for custom user models). Some code examples could be trimmed, though most content earns its place. | 2 / 3 |
Actionability | Excellent actionability with fully executable code throughout - complete pyproject.toml, settings files, models, serializers, views, tests, and management commands. All code is copy-paste ready with specific commands for every step. | 3 / 3 |
Workflow Clarity | The 'First Steps After Scaffold' section provides a clear sequence, but lacks validation checkpoints. No verification steps after migrations, no checks that the scaffold command succeeded, and no error recovery guidance for common issues like database connection failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document with ~400 lines of code inline. Advanced topics like Celery, Channels, and Docker integration could be split into separate reference files. No external file references are provided. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
181fcbc
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.