django-project-setup
Set up a new Django 6.0 project with modern tooling (uv, direnv, HTMX, OAuth, DRF, testing). Use when the user wants to create a Django project from scratch with production-ready configuration.
80
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%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 is a well-crafted skill description that excels across all dimensions. It provides specific capabilities with named tools, includes natural trigger terms, has an explicit 'Use when...' clause, and is distinctive enough to avoid conflicts with other skills. The description uses proper third-person voice and is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 'Django 6.0 project', 'modern tooling (uv, direnv, HTMX, OAuth, DRF, testing)', and 'production-ready configuration'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Set up a new Django 6.0 project with modern tooling') and when ('Use when the user wants to create a Django project from scratch with production-ready configuration'). Has explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Django', 'project', 'create', 'from scratch', plus specific tool names (uv, HTMX, OAuth, DRF) that users familiar with the ecosystem would mention. Covers both general ('Django project') and specific triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific version (Django 6.0), specific tooling stack (uv, direnv, HTMX, OAuth, DRF), and clear scope (new project setup). Unlikely to conflict with general Python skills or other web framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable with excellent workflow clarity and complete, executable code examples. However, it severely violates token efficiency by including extensive explanations of concepts Claude knows (type hints benefits, what each tool does), duplicating verification steps, and embedding a full implementation guide that should be in separate reference files. The content would be 3-4x more effective at 200-250 lines.
Suggestions
Remove the 'AI Tooling Compatibility' and 'Why This Matters' sections entirely - Claude understands type annotation benefits
Move the entire 'Implementation Guide' section (Steps 0-13) to a separate IMPLEMENTATION.md file, keeping only the execution steps in the main skill
Consolidate the duplicate verification/success criteria sections into a single checklist
Remove explanatory comments from code blocks (e.g., '# Custom User model' above AUTH_USER_MODEL) - the code is self-documenting
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~800+ lines. Contains extensive explanations Claude already knows (what HTMX is, what OAuth does, how factories work), redundant checklists (AI tooling compatibility section explains obvious benefits of type hints), and duplicated information (verification steps appear multiple times in different forms). | 1 / 3 |
Actionability | Provides fully executable code throughout - complete Python files, bash commands, configuration files, and templates. All code is copy-paste ready with proper imports and type annotations. The implementation guide contains concrete, working examples. | 3 / 3 |
Workflow Clarity | Clear 15-step execution sequence with explicit validation checkpoints (Step 14: Verify Setup), conditional branching for Docker vs Supabase paths, error handling section, and success criteria. Includes feedback loops for database setup verification. | 3 / 3 |
Progressive Disclosure | References external templates in `templates/` directory but includes massive inline implementation guide that could be separate. The skill tries to be both an overview and complete reference, resulting in a monolithic document. Related skills are mentioned but core content isn't well-layered. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (1259 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- jpoutrin/product-forge
- Commit
0ebe7ae
- 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.