Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
75
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/skills/app-builder/templates/SKILL.mdQuality
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/routing skill that efficiently directs to appropriate templates. Its strength is conciseness and clear progressive disclosure. However, it lacks actionable content in itself (all execution is delegated) and the workflow could benefit from guidance on handling edge cases or ambiguous requests.
Suggestions
Add guidance for handling ambiguous requests (e.g., 'If user request matches multiple templates, ask for clarification on: X, Y, Z')
Include a brief example of the expected output format or first steps after selecting a template to make the skill more actionable standalone
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, just a clear table of templates and minimal usage instructions. Every token serves a purpose. | 3 / 3 |
Actionability | Provides clear navigation to templates but no concrete code or commands in this file itself. The actionability depends entirely on the referenced TEMPLATE.md files which aren't shown. | 2 / 3 |
Workflow Clarity | Simple 4-step workflow is clear but lacks any validation or error handling guidance. What if no template matches? What if the user's request is ambiguous between templates? | 2 / 3 |
Progressive Disclosure | Excellent structure as a routing document. Clear one-level-deep references to 12 templates with well-organized table showing tech stack and use cases. Perfect for a template index. | 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 | |
332e58b
Table of Contents
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.