CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-app-scaffold

Scaffold a TanStack app with tanstack create using --framework, --build-tool, --template, --toolchain, --deployment, --add-ons, --blank, and --router-only. Covers flag compatibility, non-interactive defaults, and intent-preserving command construction.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, highly actionable skill body: executable commands throughout, Wrong/Correct mistake pairs with sources, and well-organized one-level-deep references. The only notable improvements are inlining the command-construction order and trimming the redundant Setup/Tension sections.

Suggestions

Move the command-construction order (currently only in references/create-flag-compatibility-matrix.md) into the body as a short numbered sequence so the workflow is explicit in SKILL.md.

Drop or merge the Setup example into the first Core Patterns example, since they are nearly identical commands.

Compress the two "Tension" subsections into one-line cross-references (e.g., "For integration selection, see choose-ecosystem-integrations/SKILL.md § Common Mistakes") to save tokens.

DimensionReasoningScore

Conciseness

The body is dominated by copy-paste commands with short, CLI-specific explanations (e.g., "Router-only compatibility mode ignores template, deployment, and add-on intent"), and it never explains concepts Claude already knows. Not 5 because the Setup section largely duplicates the first Core Patterns example, and the two "Tension" subsections are commentary that could be trimmed to one-line cross-references; not 3 because there is no real padding or over-explanation.

4 / 5

Actionability

Every section is a fully executable npx command, and each Common Mistake gives a Wrong/Correct pair (e.g., "npx @tanstack/cli create my-app --add-ons -y" vs. "--add-ons clerk,drizzle -y") covering the common cases: build tool choice, non-interactive runs, blank presets, router-only, and templates. This matches the copy-paste-ready anchor exactly.

5 / 5

Workflow Clarity

For a single-purpose skill the action is unambiguous ("build a deterministic tanstack create command before running generation") and the Wrong/Correct pairs act as inline checkpoints, but the actual command-construction sequence (framework -> mode -> add-ons -> toolchain -> -y) lives only in references/create-flag-compatibility-matrix.md rather than in the body. Not 5 because the ordering is not stated in SKILL.md itself; not 3 because the patterns plus mistake catalog make the sequence and failure modes largely inferable and there is no validation gap for a destructive operation.

4 / 5

Progressive Disclosure

The body is an overview of patterns and pitfalls, while flag-by-flag detail is appropriately split into five real, one-level-deep reference files, all verified to exist and clearly listed in the References section with descriptive titles ([Create flag compatibility matrix], [Framework adapter options], etc.). This matches the well-signaled, clearly-split anchor.

5 / 5

Total

18

/

20

Passed

Description

70%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 concrete, domain-specific, and clearly distinguishable, with strong flag-level detail. Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness at 3 and slightly weakens natural trigger coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating a new TanStack Start project, scaffolding an app with tanstack create, or choosing flags for a non-interactive scaffold."

Include one or two natural synonyms such as "new project" or "starter" to broaden trigger coverage beyond the flag names.

Briefly mention the flag-compatibility outcome users are steering toward (e.g., "so the command produces the intended scaffold rather than silently dropping integrations") to sharpen the 'what'.

DimensionReasoningScore

Specificity

Concrete phrasing like "Scaffold a TanStack app with tanstack create" plus an explicit flag list (--framework, --build-tool, --template, ...) names the domain and several specific capabilities ("flag compatibility, non-interactive defaults, and intent-preserving command construction"), with only minor gaps (e.g., no mention of build-tool rsbuild or --intent). Not 5 because the action set is essentially one scaffold action with coverage areas rather than multiple distinct concrete actions; not 3 because the flag enumeration goes well beyond 1-2 generic actions.

4 / 5

Completeness

The 'what' is clear (scaffold a TanStack app via tanstack create with the listed flags), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the 'what' half is concrete and specific rather than vague; not 4 because 'when' is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

"Scaffold", "TanStack app", "tanstack create", and the flag names are terms a user needing this skill would naturally say. Not 5 because common variations like "new project", "start/bootstrap a project", or "scaffold a TanStack Start app" are absent; not 3 because the domain-identifying phrases ("TanStack", "tanstack create", flag names) give good, specific trigger coverage rather than merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

"Scaffold a TanStack app with tanstack create" plus the specific flag list carves out a clear niche (the create command itself) with minimal overlap with adjacent skills like add-on/integration selection or docs lookup, which have distinct triggers. The third-person voice is correct ("Scaffold..."), so no specificity penalty applies.

5 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

TanStack/cli

Path

packages/cli/skills/create-app-scaffold/SKILL.md

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.