CtrlK
BlogDocsLog inGet started
Tessl Logo

docker-app-deployer

Deploys Docker and Docker Compose applications to homelab hosts with configuration management and health verification.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/docker-app-deployer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is a concise, well-structured workflow with mostly executable steps and good safety/companion-skill integration. The main weakness is the vague health-check step, which lacks concrete commands and an explicit retry loop.

Suggestions

Make the health-check step concrete with commands (e.g., 'docker ps --filter name=<app>', 'docker compose logs --tail=50 <service>') and an explicit validate->fix->retry loop.

Add a verification step that confirms the service responds (e.g., curl the health endpoint) before logging the deployment as successful.

Trim the restated opening line and per-tool invocation boilerplate to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with no padding or explanation of concepts Claude already knows; the only minor trim is the opening line restating the description and the per-tool invocation lines, so it sits at 4 rather than a perfect 5.

4 / 5

Actionability

Most steps give concrete executable commands ('docker pull', 'docker compose pull', 'docker compose up -d') and reference real companion skills/files, but the health-check step ('Verify container is running; check logs for errors') lacks specific commands, leaving minor gaps.

4 / 5

Workflow Clarity

An 8-step numbered sequence with a pre-flight safety check and a health-check step is clear, and the Safety section adds a backup-before-replacing checkpoint; however the health check is vague with no explicit validate->fix->retry loop, so it stops at 4.

4 / 5

Progressive Disclosure

The skill is under 50 lines, well-organized into clear sections (Invocation, Workflow, Safety, Companion Skills, References), and its references are one-level external URLs with no nested or buried references, so for a simple skill this scores 5.

5 / 5

Total

17

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 clearly states what the skill does and targets a distinct homelab deployment niche, but it omits an explicit 'when to use' trigger clause and its action list is only modestly specific. Adding a 'Use when...' clause and more concrete deploy-time actions would raise the score.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when deploying containers or compose stacks to homelab hosts').

Replace the broad 'configuration management' with specific concrete actions such as 'inject environment variables, map volumes, attach networks'.

Include common synonyms users say (containers, compose files, stacks) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (Docker/Docker Compose deployment to homelab hosts) with two concrete actions ('configuration management', 'health verification'), but 'configuration management' is broad and coverage is not comprehensive, matching the anchor for 1-2 concrete actions rather than several.

3 / 5

Completeness

It gives a clear 'what' (deploys Docker/Compose apps with configuration management and health verification) but lacks any 'Use when...' trigger clause, so per the guideline a missing explicit when caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ('Docker', 'Docker Compose', 'homelab hosts') with good keyword coverage, though some common synonyms ('deploy containers', 'compose files', 'stack') are missing, placing it just above the midpoint between anchors 3 and 4.

4 / 5

Distinctiveness Conflict Risk

The homelab-host deployment niche with Docker/Compose is mostly distinct with minimal conflict risk, though it could slightly overlap with generic container-management skills, so it sits at 4 rather than 5.

4 / 5

Total

14

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
pvnkmnk/AgenticSelfHostSkills
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.