templates

Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/app-builder/templates/SKILL.md

Quality

Content

57%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill excels at progressive disclosure with a well-structured routing table and a smart selective reading rule that minimizes unnecessary context loading. However, the boilerplate 'When to Use' and 'Limitations' sections detract from conciseness, and the skill itself contains no executable content — all actionable guidance is delegated to template files that aren't provided in the bundle. The workflow could benefit from edge-case handling (no match found, ambiguous requests).

Suggestions

Remove the generic 'When to Use' and 'Limitations' boilerplate sections — they add no skill-specific value and waste tokens.

Add a fallback step in the workflow for when the user's request doesn't clearly match any template (e.g., 'If no template matches, ask the user to clarify their tech stack preferences').

Consider adding a brief post-scaffolding verification step (e.g., 'After generating files, verify the project runs with the template's specified start command').

Dimension	Reasoning	Score
Conciseness	The template table and selective reading rule are efficient and well-structured. However, the 'When to Use' and 'Limitations' sections are boilerplate filler that add no value — Claude already knows to ask for clarification and not skip validation. These waste tokens.	2 / 3
Actionability	The skill provides a clear routing table and a simple 4-step usage flow, which is concrete enough for template selection. However, the actual actionable content is entirely delegated to the TEMPLATE.md files (none of which are provided in the bundle), so the skill itself contains no executable code, commands, or concrete scaffolding instructions.	2 / 3
Workflow Clarity	The 4-step usage flow is clear and sequenced, but it lacks any validation or error-handling steps — e.g., what happens if the user's request doesn't match any template, or if a template file is missing. For a scaffolding skill that creates project structures (a somewhat destructive/batch operation), the absence of verification steps is a gap.	2 / 3
Progressive Disclosure	Excellent progressive disclosure: the SKILL.md is a lean routing overview with a clear table pointing to 12 one-level-deep TEMPLATE.md files. The selective reading rule explicitly instructs Claude to read only the relevant template, which is ideal for token efficiency and navigation.	3 / 3
	Total	9 / 12 Passed

Description

67%Scale 1-3

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 a solid structure with an explicit 'Use when' clause and communicates the general purpose clearly. However, it lacks specificity about which tech stacks or frameworks are supported and misses common user trigger terms like 'boilerplate,' 'bootstrap,' or 'starter project.' Adding concrete details about the 12 templates would significantly improve both specificity and distinctiveness.

Suggestions

List specific tech stacks or frameworks covered by the 12 templates (e.g., 'React, Django, Express, Spring Boot') to improve specificity and trigger term coverage.

Add common user trigger terms like 'boilerplate,' 'bootstrap,' 'starter project,' 'init,' or 'create app' to the 'Use when' clause.

Include specific actions beyond 'scaffolding' such as 'generates directory structure, config files, and dependency manifests' to make capabilities more concrete.

Dimension	Reasoning	Score
Specificity	Names the domain (project scaffolding) and mentions '12 templates for various tech stacks,' but does not list specific actions or concrete capabilities like which tech stacks, what files are generated, or what configuration is set up.	2 / 3
Completeness	Answers both 'what' (project scaffolding templates for new applications, 12 templates for various tech stacks) 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,' and 'tech stacks,' but misses common user phrases like 'bootstrap,' 'starter,' 'boilerplate,' 'init,' 'create app,' or specific stack names that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	'Project scaffolding' and 'new projects' are somewhat specific but could overlap with other skills related to project setup, configuration, or code generation. The lack of specific tech stack names or distinguishing details reduces distinctiveness.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: popey/claude-code-skills
Path: skills/app-builder/templates/SKILL.md
Commit: a5a6601

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.