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
Quality
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 placeholder with no substantive content. It relies entirely on the skill name without explaining capabilities, use cases, or providing meaningful trigger terms. The auto-generated format with redundant triggers and category labels provides no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Django views including class-based views (CBVs), function-based views, API views, and CRUD operations'
Include a 'Use when...' clause with natural trigger terms like 'create django view', 'views.py', 'API endpoint', 'ListView', 'DetailView', 'REST endpoint'
Remove redundant trigger terms and replace with varied natural language users would actually use when requesting Django view help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Django View Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating views, handling requests, generating class-based or function-based views, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. The 'Triggers on' line is not a proper usage guide. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('django view generator' listed twice) and overly specific. Missing natural variations users would say like 'create django view', 'views.py', 'API endpoint', 'CBV', 'FBV', or 'django controller'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Django View Generator' is somewhat specific to Django views, the lack of detail about what it actually generates could cause confusion with other Django-related skills or general Python/web development 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 template with no actual Django view generation content. It consists entirely of generic boilerplate phrases that could apply to any skill, providing zero actionable guidance on how to generate Django views, what patterns to follow, or what code to produce.
Suggestions
Add executable Python code examples showing how to generate different types of Django views (function-based, class-based, generic views)
Include specific patterns for common view types: ListView, DetailView, CreateView, UpdateView, DeleteView with concrete code snippets
Define a clear workflow: 1) Identify view type needed, 2) Generate view code, 3) Add URL pattern, 4) Validate with specific checks
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual Django-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Django view generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate a Django view. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content only lists vague capabilities without any sequence of actions, validation steps, or concrete process for generating Django views. | 1 / 3 |
Progressive Disclosure | The content is a flat, generic template with no structure for discovery. No references to detailed documentation, examples, or related files. The sections present are boilerplate rather than organized 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
994edc4
- 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.