Content
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is an extensive capability catalog and persona description rather than executable guidance: it lists topics Claude largely already knows and provides no concrete code, commands, or validated workflow steps. It reads as a role prompt more than an actionable skill.
Suggestions
Replace abstract capability bullet lists and the persona/'Behavioral Traits' sections with a few concrete, copy-paste-ready code snippets or commands (e.g., a select_related/prefetch_related N+1 fix, a Celery task + config, an ASGI deployment snippet).
Turn 'Response Approach' into a real workflow with explicit validation checkpoints for risky operations — e.g., 'run makemigrations --check', 'python manage.py test', 'migrate on staging before production'.
Move the large Capabilities catalog and Example Interactions into reference files (e.g., CAPABILITIES.md, EXAMPLES.md) and keep SKILL.md as a lean overview that links one level deep, trimming content Claude already knows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly organized but padded with long bullet lists that restate general Django knowledge Claude already has ('Follows PEP 8 and Django coding style', 'Follows Django's batteries included philosophy') and generic boilerplate ('Clarify goals, constraints, and required inputs'). | 2 / 3 |
Actionability | No executable code, commands, or concrete examples anywhere in the body — 'Response Approach' ('Suggest Django-idiomatic solutions', 'Provide production-ready code') and 'Instructions' describe rather than instruct. | 1 / 3 |
Workflow Clarity | A numbered 'Response Approach' sequence exists, but it is abstract with no validation checkpoints or feedback loops despite covering risky operations (migrations, deployment), which caps it at 2. | 2 / 3 |
Progressive Disclosure | Well-sectioned but monolithic at ~170 lines with no bundle files; large capability catalogs and example interactions that should live in separate reference files are kept inline. | 2 / 3 |
Total | 7 / 12 Passed |