CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

69%

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

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 clean reference structure, but it presents patterns rather than a validated sequenced workflow for destructive scaffold operations.

Suggestions

Add an explicit numbered generation workflow with a validation checkpoint (e.g., re-run 'create --addon-details' or inspect generated config) before and after 'create my-app -y' to satisfy the destructive-operation cap.

Reduce repeated command invocations across patterns by referencing a shared setup step once.

Move the per-provider option details from the inline Wrong/Correct blocks into the existing reference files to keep the overview leaner.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with no concept over-explanation; a few command invocations repeat across patterns and could be tightened.

4 / 5

Actionability

Provides fully executable, copy-paste bash commands in Setup, Core Patterns, and Wrong/Correct blocks covering the common integration cases.

5 / 5

Workflow Clarity

Content is organized as parallel patterns rather than a sequenced workflow, and scaffold generation with '-y' is destructive yet lacks validation checkpoints, capping this at 3.

3 / 5

Progressive Disclosure

SKILL.md is an overview with three well-signaled one-level-deep reference files that exist on disk; some mistake/tension detail is inlined that could be split out.

4 / 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 is specific and clearly scoped to a distinct niche, but it omits an explicit 'Use when' trigger clause and relies on technical jargon over natural user phrasing.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when scaffolding a TanStack app and choosing ecosystem integrations or add-ons') to raise completeness.

Add natural trigger synonyms users would actually say ('TanStack integrations', 'add-ons', 'choosing auth/database/deployment providers') alongside the technical terms.

Lead with the concrete action verb and outcome, then list the commands, so the trigger terms surface before the jargon.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('Map tanstack ecosystem partner metadata to installable add-on ids') and enumerates three specific CLI commands plus coverage areas, with only minor gaps.

4 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Some relevant terms appear ('add-ons', 'ecosystem') but the phrasing leans technical ('partner metadata', 'router-only compatibility constraints') and omits natural variations a user would say.

3 / 5

Distinctiveness Conflict Risk

Scoped tightly to tanstack CLI ecosystem add-on mapping with distinctive triggers, giving it a clear niche and minimal conflict risk.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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