templates

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

Quality

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./docs/v19.7/configuration/agent/skills_external/antigravity-awesome-skills-main/skills/app-builder/templates/SKILL.md

Quality

Content

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 routing/index skill that excels at conciseness and progressive disclosure. Its main weakness is that all actionable content is deferred to template files that aren't available for evaluation, and the workflow lacks validation checkpoints for what is essentially a destructive operation (creating an entire project structure). The selective reading rule is a smart design choice for managing 12 templates efficiently.

Suggestions

Add a brief validation step to the workflow, e.g., 'After scaffolding, verify the project runs with the template's specified dev command' or a checklist of expected outputs.

Add a fallback instruction for when the user's request doesn't clearly match any template (e.g., 'If no template matches, ask the user to clarify or scaffold from scratch using closest match as reference').

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations—just a routing table and minimal usage instructions. Every token serves a purpose: directing Claude to the right template file.	3 / 3
Actionability	The routing table and usage steps provide clear direction on which template to select, but the skill itself contains no executable code or concrete scaffolding commands. The actual actionable content is deferred entirely to the referenced TEMPLATE.md files, which are not provided for evaluation.	2 / 3
Workflow Clarity	The 4-step usage workflow is clear and sequential, but it lacks any validation or error-handling guidance—e.g., what to do if the user's request doesn't match any template, or how to confirm the template was applied correctly. For a scaffolding skill that creates entire project structures, some verification step would be valuable.	2 / 3
Progressive Disclosure	Excellent progressive disclosure structure. The SKILL.md serves purely as a concise routing overview with a clear table pointing to 12 one-level-deep template files. The 'Selective Reading Rule' explicitly instructs Claude to read only the relevant template, which is ideal for token efficiency.	3 / 3
	Total	10 / 12 Passed

Description

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 provides a reasonable overview with an explicit 'Use when' clause, which is good for completeness. However, it lacks specificity about which tech stacks or frameworks are supported and misses common trigger terms users might naturally use like 'boilerplate,' 'starter,' or 'bootstrap.' Adding concrete stack names and more natural trigger keywords would significantly improve skill selection accuracy.

Suggestions

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

Add common user-facing synonyms to the trigger guidance, such as 'boilerplate,' 'starter project,' 'bootstrap,' 'initialize,' or 'init a new app.'

Dimension	Reasoning	Score
Specificity	It names the domain (project scaffolding templates) and mentions '12 templates for various tech stacks,' but does not list specific concrete actions or name which tech stacks are covered. The actions are implied rather than enumerated.	2 / 3
Completeness	It 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 keywords like 'scaffolding,' 'templates,' 'new projects,' and 'tech stacks,' but misses common user-facing variations such as 'boilerplate,' 'starter project,' 'initialize,' 'init,' 'bootstrap,' or specific stack names users might mention.	2 / 3
Distinctiveness Conflict Risk	The focus on project scaffolding is somewhat distinctive, but 'various tech stacks' is vague and could overlap with other code generation or project setup skills. Without naming specific stacks or frameworks, it's hard to distinguish from similar skills.	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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: duclm1x1/Dive-Ai
Commit: 20ba150

Reviewed: 5 months 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.