CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The body is concise, highly actionable, and well-organized with concrete commands and traceable sources. Its main gap is the lack of an explicit sequenced workflow with a post-run validation checkpoint for an operation that modifies an existing project.

Suggestions

Add an explicit numbered workflow that sequences the steps (resolve candidate ids → inspect optionized add-ons → install with required dependencies) and ends with a verification step (e.g., confirm '.cta.json' was updated and the project still builds).

Add a brief precondition check (verify '.cta.json' exists in the project root) before the first 'add' command, turning the CRITICAL mistake into an explicit gate.

DimensionReasoningScore

Conciseness

The body is lean: it assumes Claude's competence, never explains what TanStack or add-ons are, and gives each mistake a single one-line rationale plus a compact 'Source:' citation, so nearly every token earns its place.

3 / 3

Actionability

It provides copy-paste-ready 'npx @tanstack/cli' commands with specific flags ('--list-add-ons --json', '--addon-details prisma --json') and explicit Wrong/Correct blocks, fully executable without pseudocode.

3 / 3

Workflow Clarity

Headings like 'Resolve candidate ids before applying' and 'Validate optionized add-ons before install' imply ordering, but there is no explicit numbered sequence and no validation/verification checkpoint after the project-modifying 'add' command, which caps workflow clarity at 2 for a destructive/batch-style operation.

2 / 3

Progressive Disclosure

With no bundle files present, the self-contained body is organized into clear Setup / Core Patterns / Common Mistakes sections, and the one cross-skill reference ('See also: maintain-custom-addons-dev-watch/SKILL.md') is a clearly signaled one-level-deep pointer with no nested references.

3 / 3

Total

11

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 is specific and distinctive, clearly conveying what the skill does for an existing-project add-on flow. It is held back by the absence of an explicit 'Use when...' trigger clause and by trigger terms that lean heavily on internal jargon rather than natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when adding integrations like auth or database layers to an existing TanStack CLI project').

Replace or supplement internal jargon ('add-on id resolution', 'option prompts', '.cta.json project metadata preconditions') with user-facing terms ('add an integration', 'resolve the right add-on id', 'check add-on options') so the description matches what a user would actually say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 'Apply integrations', 'add-on id resolution', 'dependency chains', 'option prompts', and '.cta.json project metadata preconditions' — matching the anchor for naming several specific concrete actions.

3 / 3

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'tanstack add' and 'integrations' are natural user terms, but most of the phrase — 'add-on id resolution', 'dependency chains', 'option prompts', '.cta.json project metadata preconditions' — is internal jargon users would not naturally say, so coverage of common variations is incomplete.

2 / 3

Distinctiveness Conflict Risk

It is tightly niched to 'tanstack add' on 'existing projects' gated by '.cta.json' metadata, giving it a clear niche with distinct triggers unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
TanStack/cli
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.