django-view-generator
Django View Generator - Auto-activating skill for Backend Development. Triggers on: django view generator, django view generator Part of the Backend Development skill category.
32
3%
Does it follow best practices?
Impact
78%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/django-view-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond its own name repeated, and lacks any explicit 'Use when...' guidance. It would be nearly useless for Claude to differentiate this skill from others in a large skill library.
Suggestions
Add concrete actions the skill performs, e.g., 'Generates Django class-based and function-based views, CRUD endpoints, URL configurations, and serializers for REST APIs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create Django views, build API endpoints, scaffold views.py, or set up Django REST framework viewsets.'
Remove the redundant duplicate trigger term and instead diversify with natural variations users would say, such as 'Django API', 'Django endpoint', 'views.py', 'Django CRUD', 'Django REST view'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'Django View Generator' but does not describe any concrete actions like generating class-based views, function-based views, CRUD endpoints, or serializers. It only states it's for 'Backend Development' which is vague. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is essentially absent—there is no 'Use when...' guidance, just a redundant trigger listing. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'django view generator' repeated twice. It misses natural user phrases like 'create a Django view', 'Django API endpoint', 'Django CRUD', 'views.py', 'Django REST', or 'Django URL routing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Django' and 'View Generator' provides some specificity that distinguishes it from generic backend skills, but the lack of concrete detail about what kinds of views or patterns it generates means it could overlap with other Django-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of boilerplate meta-descriptions about what the skill supposedly does without providing any actual Django view generation instructions, code examples, or patterns. It fails on every dimension because there is no real content to evaluate.
Suggestions
Add concrete, executable Django view code examples (e.g., function-based views, class-based views, DRF viewsets) with specific patterns and when to use each.
Define a clear workflow for generating Django views: e.g., 1) Determine view type, 2) Generate view code, 3) Create URL configuration, 4) Add serializers if DRF, 5) Validate with tests.
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') and replace with actionable content like code templates, common patterns, and configuration examples.
Add references to related files for advanced topics (e.g., PERMISSIONS.md, SERIALIZERS.md, TESTING.md) to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual Django view generation guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no examples of Django views, no specific patterns. The 'Example Triggers' section just lists ways to ask for help rather than providing actionable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed materials, no links to examples or advanced guides, and no meaningful structural organization of actual content. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- Reviewed
Table of Contents
Is this your skill?
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.