CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tanstack-start

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per project.

Quality

86%

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

77%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 high-quality scaffold skill: nearly everything is executable, the workflow is explicitly sequenced with checklists at both local and deploy stages, and it concentrates on Cloudflare/D1/better-auth gotchas rather than concepts Claude already knows. Its main weaknesses are the absence of any progressive disclosure (everything inlined in one long file, including boilerplate and version pins that could be references) and minor gaps in the code shown for core files like schema.ts and __root.tsx.

Suggestions

Split heavy inline content into one-level-deep references (e.g., references/dependencies.md for the pinned version tables, references/troubleshooting.md for the Common Issues table, references/ui-components.md for theme/sidebar/root-route details) and keep SKILL.md as the workflow overview with clear 'See X' pointers.

Trim boilerplate Claude can reproduce unaided (full tsconfig.json listing, router registration snippet, auth.client.ts) to just the non-obvious settings, keeping the token budget for the Cloudflare-specific gotchas.

Add a minimal executable skeleton for src/db/schema.ts (the four better-auth tables with correct column types) since it is a CRITICAL prerequisite for auth to work and currently only the table names are listed.

DimensionReasoningScore

Conciseness

The body is dense with stack-specific gotchas Claude genuinely needs ("Use `import { env } from "cloudflare:workers"` — NOT `process.env`", "nodejs_compat (NOT node_compat)", "Auth MUST use an API route... NOT a server function"), with almost no conceptual padding. However, full boilerplate listings Claude could reproduce (complete tsconfig.json, createRouter registration, auth.client.ts) and pinned time-sensitive version numbers in Dependencies could be trimmed or split out, matching anchor 4 (minor instances that could be trimmed) rather than 5.

4 / 5

Actionability

Most guidance is copy-paste ready: complete vite.config.ts, wrangler.jsonc, drizzle client factory, better-auth server config, API catch-all route, validated server functions, shell commands, and secret-setting commands. It falls short of anchor 5 because several core files are described rather than shown (schema.ts table definitions, __root.tsx HTML shell, app.css variables, all UI components), which are gaps beyond the anchor-5 'covers the common cases' bar — fitting anchor 4 (concrete code with minor gaps).

4 / 5

Workflow Clarity

A clearly sequenced 9-step workflow (gather info → init → schema → auth → server functions → shell → CRUD → local verify → deploy) with explicit validation checkpoints: a local verification checklist ("Register a new account", "Create, list, edit, delete items"), a pre-deploy checklist, post-deploy verification, and a symptom→cause→fix Common Issues table providing error-recovery feedback loops. This matches the anchor-5 pattern of clear sequence plus explicit validation and feedback loops.

5 / 5

Progressive Disclosure

The body is a well-sectioned ~525-line monolith with zero bundle files and zero reference pointers — dependencies/version listings, full config boilerplate, per-step code, and the troubleshooting table are all inlined when several could live in one-level-deep reference files. It has genuine structure (file tree, headed steps), so it is above anchor 2, but with no external split at this size it fits anchor 3 (content that should be separate is inline) better than anchor 4 (references mostly clear).

3 / 5

Total

16

/

20

Passed

Description

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

A strong description: it states concrete capabilities via the full stack enumeration, has explicit and well-varied 'Use when...' triggers including the unnamed-tool case, and is written in third person without fluff. The only weaknesses are the single 'build' verb limiting action specificity and mildly over-broad SSR/React phrasing that slightly raises conflict risk with other full-stack frameworks.

DimensionReasoningScore

Specificity

"Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui" names the domain and a comprehensive stack of concrete capabilities, but the verbs are limited to a single 'build' action (deploy, migrations, scaffolding details are left to the body). This sits between anchor 3 (1-2 concrete actions) and anchor 5 (multiple specific actions, fully comprehensive), so 4 is the best fit.

4 / 5

Completeness

It clearly answers 'what' ("Build a full-stack TanStack Start app on Cloudflare Workers... SSR, file-based routing, server functions, D1+Drizzle, better-auth") and 'when' with an explicit 'Use whenever...' clause listing concrete trigger phrases, exactly matching the anchor-5 example pattern. Neither the what nor the when is vague or only implied.

5 / 5

Trigger Term Quality

"Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically" covers natural phrasings users would actually say, including synonym variations (scaffold a Cloudflare app / SSR dashboard / React 19 + Workers app) and the unnamed-tool case. This matches the anchor-5 comprehensive coverage with synonyms; nothing significant is missing for this niche.

5 / 5

Distinctiveness Conflict Risk

The TanStack Start + Cloudflare Workers niche is highly distinct with clear triggers, but phrases like "wants an SSR dashboard" and "even if they don't name TanStack Start specifically" broaden it to users who may actually want Next.js or another SSR framework, creating minor overlap risk with closely related full-stack React skills. Mostly distinct with minor conflict risk matches anchor 4 rather than 5.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (526 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

jezweb/claude-skills

Path

archive/plugins/cloudflare/skills/tanstack-start/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.