templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
69
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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 a clear structure with an explicit 'Use when' clause, which is good for completeness. However, it lacks specificity about which tech stacks or frameworks are supported, and the trigger terms miss common synonyms users would naturally use like 'bootstrap,' 'boilerplate,' or 'starter project.' Adding concrete stack names and more natural trigger terms would significantly improve skill selection accuracy.
Suggestions
List specific tech stacks or frameworks covered by the 12 templates (e.g., 'React, Node.js, Python Flask, Django') to improve specificity and trigger term coverage.
Add common synonyms users would naturally say, such as 'bootstrap,' 'boilerplate,' 'starter project,' 'init,' or 'setup new app' to the trigger guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project scaffolding) and mentions '12 templates for various tech stacks,' but does not list specific concrete actions or name which tech stacks are covered. 'Various tech stacks' is vague. | 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 'new applications,' but misses common user phrases like 'bootstrap,' 'starter,' 'boilerplate,' 'init,' or specific stack names (e.g., React, Node, Python) that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | 'Project scaffolding' and 'new projects' are somewhat specific but could overlap with code generation skills, project setup guides, or individual framework-specific skills. Listing specific tech stacks would make it more distinct. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
57%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-organized routing table and clear one-level-deep references to 12 template files. However, the boilerplate 'When to Use' and 'Limitations' sections waste tokens, the workflow lacks validation checkpoints (e.g., confirming user intent before scaffolding), and the skill itself contains no concrete executable guidance — all substance is deferred to the template files which aren't available for evaluation.
Suggestions
Remove the generic 'When to Use' and 'Limitations' boilerplate sections — they add no skill-specific value and waste tokens.
Add a validation step to the workflow, e.g., 'Confirm project name, directory, and any customization preferences before generating files.'
Add a brief concrete example of the expected interaction flow (e.g., user says 'create a SaaS app' → match to nextjs-saas → read TEMPLATE.md → scaffold with specific commands).
| 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 somewhat actionable. However, the actual actionable content (project scaffolding instructions) is entirely delegated to TEMPLATE.md files, and no concrete code, commands, or examples are shown in this file itself. The usage steps are generic ('Match to appropriate template') rather than specific. | 2 / 3 |
Workflow Clarity | The 4-step workflow is listed but is very thin — it lacks any validation checkpoints (e.g., confirming the match with the user before proceeding, verifying prerequisites). For a scaffolding skill that creates entire project structures, there should be guidance on confirming requirements before generating files. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure: a concise overview with a clear routing table pointing to 12 one-level-deep TEMPLATE.md files. The selective reading rule explicitly instructs to read only the relevant template, which is ideal for token efficiency and navigation. | 3 / 3 |
Total | 9 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
431bfad
- 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.