CtrlK
BlogDocsLog inGet started
Tessl Logo

maintain-custom-addons-dev-watch

Build and iterate custom add-ons/templates with tanstack add-on init, add-on compile, add-on dev, and tanstack create --dev-watch, including sync loop preconditions, watch-path validation, and project metadata constraints.

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/maintain-custom-addons-dev-watch/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-structured with executable commands and well-sourced common-mistake guidance. Its one gap is workflow clarity: the dev-watch/apply loop describes preconditions but lacks explicit validation checkpoints and a retry loop.

Suggestions

Add an explicit validate→fix→retry loop for the sync/apply workflow, e.g. after 'add-on dev' or 'add', check the target app picked up changes and re-run compile if metadata errors appear.

Insert a numbered sequence for the full authoring loop (init → compile → dev → edit → re-compile → apply) with an explicit checkpoint between compile and apply, rather than listing patterns as isolated commands.

DimensionReasoningScore

Conciseness

The body is lean — tight code blocks, one-line explanations, and source references — and avoids explaining concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Provides fully executable commands with flags and copy-paste-ready Wrong/Correct pairs (e.g. 'npx @tanstack/cli create my-sandbox --dev-watch ../path/to/framework-dir'), matching the 'fully executable, specific examples' anchor.

3 / 3

Workflow Clarity

Steps and preconditions are present (setup, dev loop, re-run compile before apply), but the sync/apply workflow lacks explicit validation checkpoints or a validate→fix→retry feedback loop; validation is framed implicitly as 'fails before...' preconditions.

2 / 3

Progressive Disclosure

Content is well-organized under clear sections (Setup, Core Patterns, Common Mistakes) with a single clearly-signaled one-level cross-reference ('See also: add-addons-existing-app/SKILL.md § Common Mistakes'); no bundle files exist to require deeper splitting.

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, naming concrete TanStack CLI add-on authoring commands and constraints. Its main weakness is the absence of an explicit 'Use when...' trigger clause and a reliance on command jargon over natural user phrasing.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when locally authoring and iterating custom TanStack add-ons and syncing compiled output into a target app via dev-watch.'

Soften CLI-command jargon in the description with natural user-facing terms (e.g. 'developing add-ons live', 'watching an add-on package') alongside the command names to improve trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'add-on init, add-on compile, add-on dev, and tanstack create --dev-watch, including sync loop preconditions, watch-path validation, and project metadata constraints' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly states what the skill does but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.

2 / 3

Trigger Term Quality

Relevant domain keywords are present ('custom add-ons/templates', 'dev-watch') but most terms are CLI-command jargon ('add-on init', 'sync loop preconditions', 'watch-path validation') rather than natural phrases a user would say, missing common variations.

2 / 3

Distinctiveness Conflict Risk

Targets a narrow niche (TanStack CLI custom add-on dev-watch workflows) with distinct triggers, making it unlikely to activate for the wrong skill.

3 / 3

Total

10

/

12

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.