CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-tanstack-start

TanStack Start full-stack React framework with Bun runtime. Use for TanStack Router, server functions, vinxi, or encountering SSR, build, preset errors.

64

Quality

76%

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 ./plugins/bun/skills/bun-tanstack-start/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 copy-paste-ready code and a clear progression from scaffolding to deployment, and is mostly concise. Its main weakness is progressive disclosure: the referenced reference files are absent from the bundle and some content that could live in separate files is inlined.

Suggestions

Create the referenced bundle files (references/router-api.md, references/forms.md) so the 'When to Load References' navigation points to real, loadable content.

Move the larger inlined code patterns (e.g., full server-function and search-params examples) into the reference files, keeping only concise representative snippets in SKILL.md.

Add an explicit validation/retry feedback loop to the server-function mutation example (validate input, retry on failure) to lift workflow clarity for the destructive POST path.

DimensionReasoningScore

Conciseness

The body is largely lean — section headers with executable code blocks and minimal prose — with only minor over-explanation (the 'Secure Installation' preamble and 'Load the dependency-upgrade skill' aside), fitting 'efficient; minor instances of over-explanation that could be trimmed' rather than the fully lean 5 anchor.

4 / 5

Actionability

Provides copy-paste-ready, complete code examples for the common cases (scaffolding commands, package.json, app.config.ts, route components, server functions, API routes, Dockerfile) — matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

Sequenced sections (Quick Start → Project Setup → routing → server functions → deployment) give a clear progression with mostly concrete checkpoints; the destructive/server-function mutation example lacks an explicit validate-then-retry feedback loop, capping it below 5 at 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Structure is reasonable and a 'When to Load References' section signals references, but the referenced files (references/router-api.md, references/forms.md) do not exist in the bundle, and substantial API-style content is inlined — matching 'some structure but could be better organized; references present but not clearly signaled / content that should be separate is inline'.

3 / 5

Total

16

/

20

Passed

Description

73%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 concise, third-person, and clearly answers both what the skill does and when to use it with domain-specific trigger terms. It is distinct and low-conflict, though the 'what' could enumerate more concrete actions to reach full specificity.

Suggestions

Expand the 'what' clause with a couple of concrete actions (e.g., scaffolding, building, and deploying TanStack Start apps on Bun) to lift specificity toward 5.

Broaden trigger coverage with a few synonyms users might say (e.g., 'TanStack Start on Bun', 'Nitro/Bun preset', 'file-based routes').

DimensionReasoningScore

Specificity

Names the domain ('TanStack Start full-stack React framework with Bun runtime') and a few concrete subsystems (TanStack Router, server functions, vinxi) but does not enumerate specific concrete actions like scaffolding, building, or deploying — matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor.

3 / 5

Completeness

Provides a clear 'what' (the framework/runtime combo) and an explicit 'when' via 'Use for TanStack Router, server functions, vinxi, or encountering SSR, build, preset errors', matching 'has both what and when; when could be more explicit or specific' rather than the fully concrete 5 anchor.

4 / 5

Trigger Term Quality

Natural trigger phrases include 'TanStack Router', 'server functions', 'vinxi', 'SSR, build, preset errors' — good keyword coverage of terms users would actually say, with only minor synonyms missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

The combination of 'TanStack Start', 'Bun runtime', 'vinxi', and 'preset errors' carves a clear niche with distinct triggers and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
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.