templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
55
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/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 a solid structure with an explicit 'Use when' clause and communicates the general purpose well. However, it lacks specificity about which tech stacks or frameworks are supported, and it misses common trigger terms 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 (e.g., 'React, Node.js, Python Flask, Django') instead of saying 'various tech stacks' to improve specificity and trigger term coverage.
Add common synonyms and trigger terms users would naturally say, such as 'bootstrap,' 'boilerplate,' 'starter project,' 'init,' or 'set up a new app.'
| 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. The phrase 'various tech stacks' is vague. | 2 / 3 |
Completeness | Clearly 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 '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 | The concept of 'project scaffolding' is fairly distinct, but 'various tech stacks' and 'new applications' are broad enough that it could overlap with code generation skills, framework-specific skills, or general project setup skills. | 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 clean routing table to 12 templates and an explicit selective reading rule. However, the boilerplate 'When to Use' and 'Limitations' sections waste tokens, and the actual workflow guidance is too thin — it lacks fallback behavior, edge case handling, and any concrete examples of template usage or adaptation.
Suggestions
Remove the generic 'When to Use' and 'Limitations' sections — they are boilerplate that Claude doesn't need and waste context window tokens.
Add guidance for edge cases: what to do when no template matches, or when the user wants a hybrid of two templates.
Add a brief concrete example showing a user request and the expected matching/scaffolding behavior (e.g., 'User: create a SaaS app → use nextjs-saas template').
| 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 usage steps are clear but very thin — just 'match to template and follow it.' There's no guidance on what to do if a user's request doesn't match any template, no fallback behavior, and no example of how to adapt a template. The actual actionable content is deferred entirely to the TEMPLATE.md files. | 2 / 3 |
Workflow Clarity | The 4-step usage workflow is simple and sequenced, but lacks any validation or error handling. What if no template matches? What if the user wants a hybrid? There are no checkpoints or decision points beyond 'match to template.' | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure: a clear overview table with 12 well-signaled one-level-deep references to individual TEMPLATE.md files. The selective reading rule explicitly tells Claude to only read the relevant template, which is ideal for token efficiency. | 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
- sickn33/antigravity-awesome-skills
- Commit
43af20c
- 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.