bun-nextjs

This skill should be used when the user asks about "Next.js with Bun", "Bun and Next", "running Next.js on Bun", "Next.js development with Bun", "create-next-app with Bun", or building Next.js applications using Bun as the runtime.

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/bun/skills/bun-nextjs/SKILL.md

Quality

Discovery

44%

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 description is heavily lopsided: it provides excellent trigger terms and clear 'when to use' guidance, but completely omits what the skill actually does. A user or Claude selecting this skill would know when to pick it but have no idea what capabilities it offers (e.g., scaffolding projects, configuring Bun runtime, resolving compatibility issues). The description needs concrete action verbs describing the skill's capabilities.

Suggestions

Add a 'what it does' clause listing specific actions, e.g., 'Scaffolds Next.js projects using Bun, configures bun runtime settings, resolves Bun/Next.js compatibility issues, and optimizes build performance.'

Restructure to lead with capabilities first, then trigger conditions: 'Configures and builds Next.js applications using Bun as the runtime. Use when the user asks about...'

Remove some redundant trigger phrases (e.g., 'Bun and Next' vs 'Next.js with Bun') and use the freed space to describe concrete skill capabilities.

Dimension	Reasoning	Score
Specificity	The description contains no concrete actions or capabilities. It only describes when to use the skill ('should be used when...') but never states what the skill actually does. There are no verbs describing actions like 'configures', 'scaffolds', 'optimizes', etc.	1 / 3
Completeness	The description answers 'when' extensively but completely fails to answer 'what does this do'. There is no indication of what capabilities or actions the skill provides, only trigger conditions. The 'what' is entirely missing.	1 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'Next.js with Bun', 'Bun and Next', 'running Next.js on Bun', 'Next.js development with Bun', 'create-next-app with Bun'. These are realistic phrases users would naturally use.	3 / 3
Distinctiveness Conflict Risk	The combination of 'Next.js' AND 'Bun' creates a very specific niche that is unlikely to conflict with a general Next.js skill or a general Bun skill. The trigger terms are narrowly scoped to this specific technology pairing.	3 / 3
	Total	8 / 12 Passed

Implementation

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, actionable skill with excellent code examples covering the full spectrum of Bun + Next.js development. Its main weaknesses are some verbosity in sections that aren't Bun-specific (middleware, env vars) and repetitive patterns (Database open/close), plus a lack of validation checkpoints in the workflow. The progressive disclosure and reference structure are well done.

Suggestions

Remove or significantly trim sections that aren't Bun-specific (middleware, environment variables) — Claude already knows standard Next.js patterns.

Add a validation step after setup, e.g., 'Verify Bun runtime: `bun --version` and check that `bun --bun next dev` starts without errors before proceeding.'

Extract the repeated Database open/close pattern into a single utility example and reference it, rather than duplicating it across 4 code blocks.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good code examples, but includes some sections Claude already knows well (middleware patterns, environment variables, basic Next.js concepts). The middleware and env vars sections add little Bun-specific value. Some code examples are repetitive (Database open/close pattern repeated 4+ times).	2 / 3
Actionability	Provides fully executable, copy-paste ready code throughout — from project creation commands to complete API routes, server actions, Docker deployment, and configuration files. Every section has concrete, runnable examples.	3 / 3
Workflow Clarity	The Quick Start provides a clear sequence for project setup, and the common errors table is helpful. However, there are no validation checkpoints — for example, no step to verify Bun is actually being used as the runtime after setup, no verification that bun:sqlite is accessible before building, and no feedback loops for error recovery during build/deploy.	2 / 3
Progressive Disclosure	Well-structured with clear sections progressing from quick start to advanced topics. References to external files (app-router.md, caching.md) are clearly signaled at the end with specific trigger conditions. Content is appropriately organized without being monolithic.	3 / 3
	Total	10 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 88da5ff

Reviewed: 17 days 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.