templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
75
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description has good structure with an explicit 'Use when' clause and clearly communicates its purpose for project scaffolding. However, it lacks specificity about what templates are available and which tech stacks are supported, and misses common trigger terms like 'boilerplate' or 'starter project' that users might naturally use.
Suggestions
List specific tech stacks or template types (e.g., 'React, Node.js, Python Flask, Django') to improve specificity and distinctiveness
Add common trigger term variations like 'boilerplate', 'starter', 'init', 'bootstrap', 'setup new app'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project scaffolding) and mentions templates for tech stacks, but doesn't list specific concrete actions or what types of projects/stacks are supported. '12 templates for various tech stacks' is vague about actual capabilities. | 2 / 3 |
Completeness | Clearly answers both what ('Project scaffolding templates for new applications') and when ('Use when creating new projects from scratch') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes some relevant terms like 'scaffolding', 'templates', 'new projects', 'new applications', but misses common variations users might say like 'boilerplate', 'starter', 'init', 'bootstrap', or specific stack names. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to project creation/scaffolding, but 'various tech stacks' is vague and could overlap with other code generation or template skills. Doesn't specify which stacks to help distinguish from similar tools. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured index/navigation skill that efficiently directs to 12 project templates. Its strength is conciseness and progressive disclosure - it's an excellent routing document. However, it lacks concrete actionable content within itself and could benefit from basic validation steps for template selection.
Suggestions
Add a brief example showing the complete flow: user request → template selection → expected output structure
Include guidance for ambiguous cases (e.g., 'If user wants a web app with payments, prefer nextjs-saas over nextjs-fullstack')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, just a clear table of templates with direct links. Every token serves a purpose. | 3 / 3 |
Actionability | Provides clear navigation to templates but no concrete code or commands in this file itself. The actual actionable content is delegated to linked TEMPLATE.md files, making this more of an index than executable guidance. | 2 / 3 |
Workflow Clarity | The 4-step usage section provides a basic workflow but lacks validation checkpoints. No guidance on what to do if template matching is ambiguous or if scaffolding fails. | 2 / 3 |
Progressive Disclosure | Excellent structure as an index file with one-level-deep references. Clear table format makes navigation easy, and the selective reading rule explicitly tells Claude to only load relevant content. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 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.