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.
65
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-tanstack-start/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent trigger terms and clear distinctiveness for a niche technology stack. The main weakness is that it describes the domain and when to use it but doesn't articulate specific actions the skill performs (e.g., 'diagnoses build errors', 'configures server functions', 'sets up routing'). Adding concrete verbs describing what the skill does would elevate the specificity.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Diagnoses and resolves SSR, build, and preset errors in TanStack Start projects' or 'Configures TanStack Router, server functions, and vinxi settings.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TanStack Start, full-stack React framework, Bun runtime) and mentions some specific concepts (TanStack Router, server functions, vinxi, SSR, build, preset errors), but doesn't list concrete actions the skill performs—it's more about what it covers than what it does. | 2 / 3 |
Completeness | Answers both 'what' (TanStack Start full-stack React framework with Bun runtime) and 'when' ('Use for TanStack Router, server functions, vinxi, or encountering SSR, build, preset errors') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would actually say: 'TanStack Start', 'TanStack Router', 'server functions', 'vinxi', 'SSR', 'build errors', 'preset errors', and 'Bun runtime'. These cover the key terms a developer would use when encountering issues in this stack. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive—TanStack Start, vinxi, and the combination of TanStack Router with Bun runtime create a very specific niche that is unlikely to conflict with generic React or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable skill with excellent executable code examples covering the full TanStack Start workflow with Bun. Its main weaknesses are verbosity (many similar patterns repeated at length that could be condensed or split into reference files) and lack of validation checkpoints in workflows. The progressive disclosure structure is partially implemented but the inline content is too heavy for a SKILL.md overview.
Suggestions
Move detailed examples (server functions with context, search params, Docker deployment) into separate reference files and link to them from the main SKILL.md to reduce token footprint
Add validation checkpoints to workflows, e.g., after `bun run build` verify `.output/` directory exists, after `bun run dev` verify server responds at localhost:3000
Consolidate repetitive patterns — the Database open/close/query pattern appears 3 times; show it once and reference it
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long with many code examples that are somewhat repetitive (e.g., multiple variations of fetching users, repeated Database open/close patterns). The 'Secure Installation' section adds useful but somewhat verbose content. The server functions section could be tightened. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready with correct imports, proper TypeScript types, and realistic patterns. The quick start commands, project setup files, route components, server functions, API routes, Docker deployment, and error table all provide concrete, specific guidance. | 3 / 3 |
Workflow Clarity | The Quick Start section provides a clear sequence for project creation, and the Deployment section has clear build steps. However, there are no validation checkpoints — no steps to verify the dev server is running, no build validation, no guidance on what to do if build fails. The common errors table partially compensates but lacks feedback loops. | 2 / 3 |
Progressive Disclosure | The skill references `references/router-api.md` and `references/forms.md` at the end with clear trigger conditions, and mentions the `dependency-upgrade` skill. However, no bundle files are provided, so these references may be broken. The main content is quite long (~300 lines) with sections like the full Docker setup and extensive route examples that could be split into reference files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- secondsky/claude-skills
- Commit
5e92b71
- 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.