templates

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

Quality

70%

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 ./.agents/skills/app-builder/templates/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

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

The content is an exemplary lean routing skill with a clean template-discovery table and a clear usage workflow. Its one material defect is that every referenced TEMPLATE.md file is missing, breaking the progressive-disclosure navigation it is built around.

Suggestions

Ship the 13 referenced TEMPLATE.md files (e.g. nextjs-fullstack/TEMPLATE.md) so the table links resolve; without them the skill's core navigation is broken.

Add a brief confirm-match step to the Usage workflow (e.g. 'Confirm the matched template with the user before reading TEMPLATE.md') to serve as a validation checkpoint.

Verify each table link path matches an actual file to avoid dangling references.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview table plus a four-step usage list with no padding or explanation of concepts Claude already knows, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'.	5 / 5
Actionability	Provides concrete routing guidance (match project type, read only that template's TEMPLATE.md, follow its tech stack), but the actual executable detail lives in template files that are not present, leaving minor gaps consistent with 'Mostly executable guidance; concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The four-step Usage sequence (user says 'create [type] app' → match to template → read only that template → follow its tech stack) is clear and unambiguous, but lacks an explicit confirm-match checkpoint, fitting 'Clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	The overview-with-table design is well-signaled and one-level-deep in intent, but all 13 referenced TEMPLATE.md paths do not exist in the bundle, so the references cannot actually be navigated, matching 'references present but not clearly signaled / could be better organized' due to broken referenced paths.	3 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 clearly communicates a focused niche (new-project scaffolding) with an explicit 'Use when' trigger, and is appropriately concise. Its main weakness is generic trigger phrasing and lack of enumerated concrete capabilities.

Suggestions

Add concrete trigger phrases users would say, e.g. 'Use when the user asks to create, scaffold, or bootstrap a new app or project from scratch'.

List a couple of concrete actions or representative stacks (e.g. 'scaffolds Next.js, FastAPI, Express, and mobile apps') to lift specificity and trigger coverage.

Include common synonyms like 'bootstrap' or 'starter' to broaden natural term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Project scaffolding templates for new applications') and one concrete action (scaffolding new projects) but does not enumerate the specific capabilities, matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'.	3 / 5
Completeness	Explicitly states what ('Project scaffolding templates for new applications') and when ('Use when creating new projects from scratch'), but the 'when' is somewhat generic rather than enumerating concrete trigger phrases, matching 'Has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	Relevant phrases like 'creating new projects from scratch', 'scaffolding', and 'new applications' are present, but common variations a user might say ('scaffold an app', 'bootstrap a project', stack-specific terms) are missing, fitting 'Some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	The new-project scaffolding niche is distinct and unlikely to trigger for unrelated skills, but 'various tech stacks' is broad enough to risk minor overlap with framework-specific skills, fitting 'Mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 13 missing	Warning

	Total	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/app-builder/templates/SKILL.md
Commit: 549ba3d

Reviewed: 4 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.