Name: choose-ecosystem-integrations
Rating: 64 (1 reviews)
Author: TanStack

choose-ecosystem-integrations

Map tanstack ecosystem partner metadata to installable add-on ids using tanstack ecosystem --json, tanstack create --list-add-ons --json, and tanstack create --addon-details --json. Covers exclusive categories, provider options, and router-only compatibility constraints.

Quality

77%

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/choose-ecosystem-integrations/SKILL.md

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 and highly actionable, with executable commands throughout and clean one-level-deep references. Its main weakness is workflow clarity: the scaffold flow lacks explicit validation checkpoints and error-recovery feedback for a destructive batch operation.

Suggestions

Add an explicit validation/verification step after scaffolding (e.g., run a build or inspect generated add-on config) to close the feedback loop for the destructive 'create ... -y' command.

Number the core discover -> inspect -> choose -> scaffold steps so the multi-step process is sequenced rather than only implied by the pattern headings.

Add a brief recovery note for what to do when an exclusive-category or router-only constraint is violated (e.g., re-run with a single add-on or drop --deployment).

Dimension	Reasoning	Score
Conciseness	The body is lean, leading with executable bash commands and keeping prose to domain-specific, non-obvious facts (e.g., 'Router-only mode ignores deployment integration'); no generic concepts Claude already knows are explained, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	Every section provides concrete, copy-paste-ready commands with specific flags, and the Wrong/Correct mistake blocks give executable examples, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	Core Patterns imply a discover -> inspect -> enforce sequence, but there are no explicit validation checkpoints and the 'create my-app ... -y' scaffold is a batch/destructive operation with no validate/fix/retry loop, so per the guidelines workflow clarity is capped at 2; not 1 because a sequence is present, not 3 because checkpoints are missing.	2 / 3
Progressive Disclosure	Sections are well-organized (Setup, Core Patterns, Common Mistakes, References) and the References section links three real, one-level-deep files (verified to exist and not nest further), matching 'clear overview with well-signaled one-level-deep 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 distinct, naming concrete CLI commands and constraint areas, but it omits any explicit 'Use when...' trigger guidance and leans on technical jargon rather than natural user terms. These gaps cap completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when selecting tanstack integrations such as auth, data layer, or deployment for a new or existing tanstack app.'

Soften jargon by surfacing natural terms users would say ('add-ons', 'integrations', 'auth/database providers') alongside the CLI flags.

Clarify when not to use this skill (e.g., plain scaffolding without integration choices) to reduce overlap with the required scaffold and discovery skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (map partner metadata to add-on ids) plus three exact CLI commands and named constraint areas, matching the 'lists multiple specific concrete actions' anchor; not 2 because it goes beyond naming a domain and some actions.	3 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Contains relevant keywords ('tanstack', 'ecosystem', 'add-on', 'provider') but buries them in CLI jargon ('--json', 'partner metadata', 'compatibility constraints') and lacks natural user phrasings, matching 'some relevant keywords but missing common variations'; not 1 because real keywords are present, not 3 because they are not the terms a user would naturally say.	2 / 3
Distinctiveness Conflict Risk	Scoped to a narrow tanstack CLI niche (ecosystem partner -> installable add-on id mapping) with distinct constraints (exclusive categories, router-only), making it unlikely to fire for unrelated skills; matches 'clear niche with distinct triggers'.	3 / 3
	Total	10 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: TanStack/cli
Path: packages/cli/skills/choose-ecosystem-integrations/SKILL.md
Commit: efbc8d5

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