templates
Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill templates80
Quality
70%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/app-builder/templates/SKILL.mdDiscovery
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.
This description has a solid structure with explicit 'what' and 'when' components, earning full marks for completeness. However, it lacks specificity about which tech stacks are supported and misses common trigger terms users might use when requesting project scaffolding. The vague 'various tech stacks' phrase reduces both specificity and distinctiveness.
Suggestions
List specific tech stacks covered (e.g., 'React, Node.js, Python Flask, Django') to improve specificity and distinctiveness
Add common trigger term variations like 'bootstrap', 'boilerplate', 'starter project', 'init', or 'create-react-app style' to the description
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (project scaffolding) and mentions templates, but doesn't list specific concrete actions beyond 'creating new projects'. The mention of '12 templates for various tech stacks' hints at capabilities but doesn't specify what those stacks are. | 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', and 'tech stacks', but misses common variations users might say like 'bootstrap', 'starter', 'boilerplate', 'init', or specific stack names. | 2 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to project scaffolding/templates, but 'various tech stacks' is vague and could overlap with other code generation or project setup skills. Listing specific stacks would improve distinctiveness. | 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 Claude to the appropriate template. Its strength is extreme conciseness and clear progressive disclosure. However, it lacks concrete scaffolding commands in the main file and could benefit from fallback guidance when no template matches.
Suggestions
Add a brief fallback instruction for when user's project type doesn't match any template (e.g., 'If no template matches, ask user to clarify or suggest closest match')
Consider adding one concrete example command showing what a template execution looks like (e.g., 'After reading template, run: npx create-next-app...')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations, just a clear table of templates with direct links. Every token serves a purpose. | 3 / 3 |
Actionability | Provides clear template selection guidance and links, but the actual actionable content (scaffolding steps, commands) is deferred to linked files. The 4-step usage is helpful but generic. | 2 / 3 |
Workflow Clarity | The 4-step workflow is clear but minimal. No validation checkpoints or error handling guidance. For a routing/index skill this is acceptable, but lacks guidance on what to do if no template matches. | 2 / 3 |
Progressive Disclosure | Excellent structure as an index file. Clear one-level-deep references to 12 template files with well-organized table navigation. The 'Selective Reading Rule' explicitly guides Claude to load only relevant content. | 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- 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.