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.
50
54%
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-nextjs/SKILL.mdQuality
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 essentially a trigger-term list with no capability description. While it excels at specifying when to use the skill and occupies a clear niche (Next.js + Bun), it completely fails to describe what the skill actually does — whether it helps with project setup, configuration, deployment, debugging, or something else entirely. A user or Claude selecting this skill would have no idea what actions it enables.
Suggestions
Add concrete capability descriptions at the beginning, e.g., 'Scaffolds, configures, and runs Next.js applications using Bun as the JavaScript runtime and package manager. Covers project setup with create-next-app, dependency management, dev server configuration, and build optimization.'
Restructure to lead with 'what it does' followed by 'Use when...' — currently the entire description is a 'when' clause with zero 'what' content.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions or capabilities. It only describes when to use the skill ('when the user asks about...') 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' explicitly 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' is a very specific niche that is unlikely to conflict with a general Next.js skill or a general Bun skill. The trigger terms clearly delineate this intersection. | 3 / 3 |
Total | 8 / 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 solid, actionable skill with excellent executable code examples covering the full spectrum of Bun + Next.js development. Its main weaknesses are verbosity — several sections cover standard Next.js patterns that aren't Bun-specific — and the lack of validation checkpoints in workflows. The referenced files don't exist in the bundle, and the monolithic structure would benefit from splitting non-essential sections into reference files.
Suggestions
Remove or significantly trim sections that cover standard Next.js patterns with no Bun-specific content (middleware, environment variables) to improve conciseness.
Add validation checkpoints to workflows — e.g., after `bun run build`, verify the `.next` directory was created; after Docker build, verify the container starts correctly.
Move detailed code examples (server actions, file operations, API routes) into a reference file like `references/bun-apis.md` and keep only the most essential example inline.
Avoid pinning specific version numbers (e.g., `next: ^16.1.1`, `react: ^19.2.3`) in the package.json example, as these become stale quickly — or note them as examples only.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some sections that are overly verbose or cover patterns Claude already knows well (middleware auth checks, environment variables, basic Docker setup). The middleware and env vars sections add little Bun-specific value. The numerous full code examples could be trimmed since many follow standard Next.js patterns. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code throughout — from project creation commands, to complete server component examples, API routes, Docker configurations, and deployment steps. The common errors table is also highly actionable with specific fixes. | 3 / 3 |
Workflow Clarity | The Quick Start provides a clear sequence for project creation and running. However, there are no validation checkpoints — no steps to verify the project was created correctly, no build validation, and the Docker workflow lacks health checks or verification. The deployment section lists commands without confirming success. | 2 / 3 |
Progressive Disclosure | The skill references `references/app-router.md`, `references/caching.md`, and a `dependency-upgrade` skill, which is good. However, no bundle files are provided, so these references are unverifiable. The main file itself is quite long (~250 lines) with substantial inline content (middleware, env vars, server actions) that could be split into reference files for better organization. | 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.