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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill django-view-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mainly of boilerplate metadata rather than useful content. It fails to explain what the skill does, provides redundant and limited trigger terms, and lacks any guidance on when Claude should use it. The description would be nearly useless for skill selection among multiple options.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Django views including function-based views, class-based views, API views, and viewsets with proper imports and URL routing'
Add a 'Use when...' clause with natural trigger terms like 'create django view', 'views.py', 'class-based view', 'CBV', 'function view', 'FBV', 'API endpoint', 'viewset'
Remove redundant trigger terms and expand to include variations users would naturally say when needing 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 code, 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. | 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', 'class-based view', 'function view', 'API endpoint'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Django View Generator' is somewhat specific to Django views, the lack of detail about what it actually does could cause confusion with other Django-related or general Python/web development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It describes what a Django view generator skill might do but provides zero actionable information, no code examples, no Django-specific guidance, and no workflow for generating views. The entire content could be deleted and replaced with actual Django view generation instructions.
Suggestions
Add concrete, executable Python code examples showing how to generate different types of Django views (function-based, class-based, generic views)
Include a clear workflow: 1) Identify view type needed, 2) Generate view code, 3) Add URL pattern, 4) Validate with Django's check command
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific Django patterns like ListView, CreateView, APIView examples
Add a quick reference section with common view patterns: CRUD operations, authentication-required views, pagination, and form handling
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information about Django views. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code examples, no specific commands, and no actual instructions for generating Django views. The entire content describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but includes none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no structure for actual learning. No references to detailed materials, no examples file, no API documentation - just empty promises of capabilities. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.