bun-docker

Use for Docker with Bun, Dockerfiles, oven/bun image, containerization, and deployments.

Quality

47%

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-docker/SKILL.md

Quality

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.

This description is essentially a list of trigger keywords without any explanation of what the skill actually does. It lacks concrete actions (e.g., creating Dockerfiles, optimizing Bun container builds, configuring multi-stage builds) and reads more like a tag list than a functional description. The narrow technology pairing of Docker+Bun provides some distinctiveness, but the absence of capability details severely limits its usefulness for skill selection.

Suggestions

Add concrete actions describing what the skill does, e.g., 'Creates and optimizes Dockerfiles for Bun applications, configures multi-stage builds using the oven/bun image, and sets up container-based deployments.'

Expand the 'Use when' clause with more natural trigger phrases, e.g., 'Use when the user needs to containerize a Bun project, create a Dockerfile for Bun, deploy a Bun app with Docker, or configure the oven/bun base image.'

Separate the 'what it does' from the 'when to use it' to clearly answer both questions, ensuring completeness.

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 the skill's capabilities or actions. The description only answers 'when' (partially) but not '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 say. However, it misses variations like 'container', 'docker-compose', 'bun runtime', or '.dockerfile'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'Docker' and 'Bun' together with 'oven/bun image' provides some distinctiveness, but 'containerization' and 'deployments' are broad terms that could overlap with general Docker or deployment skills.	2 / 3
	Total	6 / 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 strong, highly actionable reference skill for Docker with Bun, providing comprehensive, executable Dockerfile examples across many common scenarios. Its main weaknesses are the lack of validation/verification steps in workflows and some redundancy across similar Dockerfile patterns. The progressive disclosure and reference structure are well done.

Suggestions

Add validation checkpoints to multi-step workflows, e.g., 'docker build -t myapp . && docker run --rm myapp bun --version' to verify the image works before deploying.

Consolidate overlapping sections (distroless image and compiled binary) to reduce redundancy and improve conciseness.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete examples, but includes some variants that could be consolidated (e.g., the compiled binary section overlaps significantly with the distroless section). The image variant comments with sizes are helpful but the overall document is quite long with many similar Dockerfile patterns.	2 / 3
Actionability	Every section provides fully executable, copy-paste ready Dockerfiles, docker-compose files, and bash commands. The code examples are complete and specific, covering a wide range of real deployment scenarios.	3 / 3
Workflow Clarity	Multi-stage builds are clearly sequenced, but there are no explicit validation checkpoints (e.g., 'verify the image builds successfully', 'test the container starts'). For Docker operations which can fail silently or produce broken images, validation steps like testing the built image or verifying health checks work would improve reliability.	2 / 3
Progressive Disclosure	The skill is well-organized with clear section headers progressing from basic to advanced topics. It appropriately references external files (references/optimization.md, references/kubernetes.md) with clear trigger conditions, keeping the main file focused on core Docker patterns.	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.