bun-docker
Use for Docker with Bun, Dockerfiles, oven/bun image, containerization, and deployments.
44
43%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-docker/SKILL.mdQuality
Discovery
22%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 functions primarily as a keyword list rather than a proper skill description. It completely lacks any explanation of what the skill does (e.g., creating Dockerfiles, optimizing Bun container images, configuring deployments), making it impossible for Claude to understand the skill's capabilities. The trigger terms are reasonable but the absence of concrete actions severely limits its usefulness.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates and optimizes Dockerfiles for Bun applications, configures multi-stage builds using the oven/bun image, and sets up containerized deployments.'
Restructure to clearly separate 'what' from 'when', e.g., 'Creates Dockerfiles and container configurations for Bun-based applications using the oven/bun image. Use when the user needs to containerize a Bun project, write a Dockerfile for Bun, or deploy Bun apps with Docker.'
Add more trigger term variations such as 'container', 'docker-compose', 'bun runtime image', or 'production Docker setup' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not list any concrete actions—it only says 'Use for Docker with Bun' without specifying what the skill actually does (e.g., generate Dockerfiles, optimize images, configure multi-stage builds). | 1 / 3 |
Completeness | While it has a 'Use when' clause listing trigger terms, the 'what does this do' part is entirely missing—there is no description of what actions or capabilities the skill provides. The description only addresses 'when' without 'what'. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Docker', 'Bun', 'Dockerfiles', 'oven/bun image', 'containerization', and 'deployments', which are natural terms users might use. However, it misses variations like 'container', 'docker-compose', 'bun runtime', or '.dockerfile'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Docker' and 'Bun' together is somewhat distinctive, but terms like 'containerization' and 'deployments' are broad and could overlap with general Docker or deployment skills. | 2 / 3 |
Total | 6 / 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, highly actionable reference skill for Docker with Bun that provides comprehensive, executable examples across many common scenarios. Its main weaknesses are moderate verbosity from overlapping patterns and the lack of explicit validation/verification steps in the deployment workflow. The progressive disclosure structure is reasonable but the referenced files don't exist in the bundle.
Suggestions
Add explicit validation checkpoints to the workflow, e.g., 'docker build . && docker run --rm myapp bun --version' to verify the image works before deploying to production.
Consolidate overlapping Dockerfile patterns (distroless and compiled binary sections are very similar) to reduce redundancy and improve conciseness.
Include the referenced bundle files (references/optimization.md, references/kubernetes.md) or remove the references if they don't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete examples, but includes some redundancy (e.g., multiple similar Dockerfile patterns that overlap significantly, and the compiled binary section partially duplicates the distroless section). The image variant comments with sizes are helpful but the overall document could be tightened. | 2 / 3 |
Actionability | Every section provides fully executable, copy-paste ready Dockerfiles, docker-compose files, and shell commands. The code examples are complete and specific, covering a wide range of real deployment scenarios with concrete configurations. | 3 / 3 |
Workflow Clarity | Multi-stage builds are clearly sequenced within individual Dockerfiles, and the common errors table helps with troubleshooting. However, there are no explicit validation checkpoints (e.g., 'verify the image builds successfully', 'test the container starts correctly') or feedback loops for the overall deployment workflow, which involves potentially destructive/production operations. | 2 / 3 |
Progressive Disclosure | The document references `references/optimization.md` and `references/kubernetes.md` with clear loading criteria, and mentions the `dependency-upgrade` skill. However, no bundle files are provided, so these references are unverifiable. The main document itself is quite long and some sections (like the compiled binary vs distroless patterns) 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.