Name: add-addons-existing-app
Rating: 58.4 (1 reviews)
Author: TanStack

add-addons-existing-app

Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.

Quality

67%

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 ./packages/cli/skills/add-addons-existing-app/SKILL.md

Quality

Content

76%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 body is highly actionable with executable commands and well-chosen Wrong/Correct examples backed by source citations, and it is well-structured and concise. Its main weakness is the lack of an explicitly sequenced workflow with validation feedback loops for project-modifying add-on operations.

Suggestions

Promote the id-resolution / addon-validation / apply steps into an explicit ordered workflow with numbered checkpoints (1. resolve ids, 2. validate addon details, 3. apply, 4. verify).

Add a validation/verification feedback loop, e.g. re-run 'create --list-add-ons --json' after applying to confirm the add-ons registered and dependencies resolved.

Tighten the Windows-path and 'Tension' entries to one line each to reclaim token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with copy-paste commands and one-line domain-specific explanations (e.g. why missing .cta.json breaks add flows) rather than generic padding, but the Windows-path and 'Tension' entries are slightly narrative and could be trimmed.	4 / 5
Actionability	Every pattern and mistake pairs a Wrong/Correct block with fully executable, copy-paste-ready commands (e.g. 'npx @tanstack/cli create --list-add-ons --json', 'npx @tanstack/cli create --addon-details prisma --json') and cites real source paths, covering the common cases.	5 / 5
Workflow Clarity	Useful patterns exist (resolve ids, validate addon details, then apply) but they are presented as parallel 'Core Patterns' rather than an explicitly ordered workflow, and there are no validation feedback loops for these project-modifying (batch/destructive) operations, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so structure is judged on the body: clear Setup / Core Patterns / Common Mistakes sections with a single well-signaled one-level cross-reference ('See also: maintain-custom-addons-dev-watch/SKILL.md'), though it is self-contained rather than an overview pointing to detailed materials.	4 / 5
	Total	16 / 20 Passed

Description

58%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 conveys a specific, third-person 'what' with several concrete capabilities, but omits any 'when to use' trigger guidance and leans on internal mechanism jargon over natural user phrasing. It is distinctive but would benefit from explicit trigger terms.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when adding integrations like clerk or drizzle to an existing TanStack-scaffolded app via tanstack add'.

Replace internal jargon ('add-on id resolution', 'option prompts', '.cta.json preconditions') with user-facing phrasing or move those details into the body.

Include common synonyms and concrete add-on names (clerk, drizzle, prisma, tanstack-query) so the description matches terms users actually say.

Dimension	Reasoning	Score
Specificity	Names the domain ('Apply integrations to existing projects with tanstack add') and several concrete sub-capabilities ('add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions'), but some items are mechanism descriptions rather than discrete user-facing actions, leaving minor gaps.	4 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric, a missing when-clause caps completeness at 3.	3 / 5
Trigger Term Quality	A few natural terms appear ('integrations', 'existing projects', 'tanstack add'), but the description is loaded with internal jargon ('add-on id resolution', 'dependency chains', 'option prompts', 'preconditions') that users would not naturally say, and common synonyms ('add-ons', 'install clerk/drizzle') are missing.	3 / 5
Distinctiveness Conflict Risk	The niche is clear and specific (tanstack add onto existing, already-scaffolded projects), giving minimal conflict risk, but the body itself notes tension with maintain-custom-addons-dev-watch, indicating minor overlap with a closely related skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: TanStack/cli
Path: packages/cli/skills/add-addons-existing-app/SKILL.md
Commit: 4f7744c

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