add-to-project

Add addons or features (PWA, Tauri, Starlight/Fumadocs docs, Biome/Oxlint, Husky/Lefthook, Turborepo/Nx, the MCP addon, etc.) to an existing Better-T-Stack project. Use when the user wants to extend, enhance, or add tooling to a project that was created with Better-T-Stack.

Quality

87%

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

Quality

Content

86%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.

A tight, well-structured skill body that gives Claude an unambiguous plan-then-apply workflow for adding Better-T-Stack addons. The main improvement would be a brief explicit validation/retry step after applying addons and a pointer to where nested addon options live.

Suggestions

Add an explicit post-apply verification step (e.g., re-read bts.jsonc or run bts_get_schema to confirm the addon landed) with a retry loop if it failed, which would raise workflow clarity given the batch/install nature of the operation.

Briefly indicate where nested addonOption schemas can be confirmed (the note already references bts_get_schema) so Claude knows the lookup path without re-discovering it.

Consider listing the one or two most common nested addon options inline (e.g., Fumadocs template choice) so the common cases are copy-paste ready without an extra schema call.

Dimension	Reasoning	Score
Conciseness	The body is lean — it lists the workflow steps, available addons, and rules with no padding and no explanation of concepts Claude already knows; every line earns its place.	5 / 5
Actionability	Concrete tool names and specific MCP calls (bts_plan_addons, bts_add_addons, bts_get_schema) make the guidance executable, but the addon set and options are referenced rather than fully enumerated, leaving minor gaps for the common cases.	4 / 5
Workflow Clarity	A clear four-step sequence with an explicit plan-before-apply checkpoint and conflict-surfacing rule, but the plan step is described as a dry run without an explicit verify/retry loop after applying (only 'report what changed').	4 / 5
Progressive Disclosure	Well-organized single-file skill under 50 lines with clear sections (When this applies, Workflow, Available addons, Rules); no bundle files exist, so the self-contained structure is appropriate and navigable.	5 / 5
	Total	18 / 20 Passed

Description

88%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.

A strong, specific description that clearly conveys both the capabilities and the trigger conditions, well-scoped to Better-T-Stack projects. It would benefit from a few more synonymous trigger phrasings to round out keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions and the full addon inventory (PWA, Tauri, Starlight/Fumadocs docs, Biome/Oxlint, Husky/Lefthook, Turborepo/Nx, the MCP addon) — comprehensive coverage of concrete capabilities.	5 / 5
Completeness	Explicitly states the what ('Add addons or features ... to an existing Better-T-Stack project') and the when ('Use when the user wants to extend, enhance, or add tooling to a project that was created with Better-T-Stack'), with concrete trigger conditions.	5 / 5
Trigger Term Quality	Natural user phrases like 'add PWA support', 'switch to Biome', 'add Turborepo', and the 'extend, enhance, or add tooling' wording are strong, but there are not many synonymous variations of the core trigger phrase.	4 / 5
Distinctiveness Conflict Risk	Narrowly scoped to Better-T-Stack projects with a unique config marker (bts.jsonc); the 'existing project created with Better-T-Stack' qualifier minimizes overlap with the scaffold-project skill and others.	5 / 5
	Total	19 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: AmanVarshney01/create-better-t-stack
Path: plugin/skills/add-to-project/SKILL.md
Commit: 9627a7c

Reviewed: 24 minutes 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.