tanstack-start

Build JSON-defined TanStack Start applications with @json-render/tanstack-start. Use for Start route specs, splat routing, SSR loaders, head metadata, layouts, and client navigation. Do not use for generic TanStack Router apps that do not use json-render.

Quality

88%

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

Quality

Content

90%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 a tight, code-first integration guide with fully executable examples and no padding, scoring top marks on conciseness and actionability. Workflow clarity and progressive disclosure sit at 4: the build sequence is logical but lacks explicit checkpoints, and all detail is inlined in a single file rather than split across one-level-deep references.

Suggestions

Add a short numbered build sequence at the top (1. Install 2. Define catalog + spec 3. Wire server helpers 4. Add route + root provider) to make the workflow order explicit.

Consider moving the full StartAppSpec object shape and server-helper options into a referenced reference file, keeping SKILL.md as a concise overview with one-level-deep links.

Add a brief verification step (e.g. run the dev server / check that getHead resolves metadata) so the workflow has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean and dense: leads each section with executable code and tight prose, assumes Claude knows React/TanStack, and avoids explaining basic concepts or what libraries are.	5 / 5
Actionability	Fully executable, copy-paste-ready TypeScript covering the common cases: catalog definition, a complete StartAppSpec object, createStartApp server helpers, route wiring, and the root provider.	5 / 5
Workflow Clarity	Sections follow a clear logical build sequence (Install, Application Spec, Server Helpers, Route Wiring, Root Provider) but lack explicit numbered checkpoints or validation steps; no destructive/batch operations so the workflow-clarity cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections, but it is a ~195-line monolithic SKILL.md with no one-level-deep references to separate files for the spec/server-helpers detail, so it does not reach the clear-overview-with-references anchor 5.	4 / 5
	Total	18 / 20 Passed

Description

87%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 strong: it states a concrete purpose, enumerates specific capabilities, provides explicit 'Use for' triggers, and includes a clear exclusion boundary against generic TanStack Router apps. Minor gaps in trigger-term synonyms keep specificity and trigger quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('route specs, splat routing, SSR loaders, head metadata, layouts, and client navigation') but they are capability areas rather than many discrete actions, so it sits at anchor 4 rather than 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Build JSON-defined TanStack Start applications with @json-render/tanstack-start') and 'when' ('Use for Start route specs...') with concrete trigger phrases, plus a negative boundary clause.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('TanStack Start', 'splat routing', 'SSR loaders', 'head metadata', 'client navigation') matching what a user would say, but misses a few common synonyms (e.g. 'server-side rendering' spelled out).	4 / 5
Distinctiveness Conflict Risk	Clear niche scoped to @json-render/tanstack-start with explicit disambiguation ('Do not use for generic TanStack Router apps that do not use json-render'), minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/json-render
Path: skills/tanstack-start/SKILL.md
Commit: c2600d7

Reviewed: 1 day 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.