container-orchestration

Docker and Kubernetes patterns. Triggers on: Dockerfile, docker-compose, kubernetes, k8s, helm, pod, deployment, service, ingress, container, image.

1.25x

Quality

70%

Does it follow best practices?

Impact

100%

1.25x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xdarkmatter/claude-mods/container-orchestration/SKILL.md

Quality

Content

72%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 content is highly actionable and token-efficient, packed with executable examples. Its main weaknesses are the absence of any validation-gated workflow for the build/push operation and the fact that all referenced bundle files are missing.

Suggestions

Create the referenced bundle files (references/dockerfile-patterns.md, references/k8s-manifests.md, references/helm-patterns.md, scripts/build-push.sh, and the two asset templates) or remove the dead references.

Add a short build-and-push workflow with an explicit validation checkpoint (e.g. verify image runs locally before pushing) so the batch/outward operation has a feedback loop.

Trim the redundant intro line and the DO/DON'T entries that restate the annotated Dockerfile to push conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, code-driven reference material that does not over-explain concepts Claude already knows. Minor redundancy (intro restates the description; the DO/DON'T list partly reiterates the Dockerfile) keeps it just below 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready artifacts: a complete multi-stage Dockerfile, docker-compose.yml, Kubernetes Deployment/Service/Ingress manifests, and a kubectl command table covering common cases.	5 / 5
Workflow Clarity	This is a reference catalog, not a sequenced workflow, and the referenced build-push.sh implies a batch/outward operation (build and push image) without any validation or verification steps. Per the destructive/batch cap, workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	In-body structure is well organized with one-level-deep reference pointers, but every referenced bundle file (./references/.md, ./scripts/build-push.sh, ./assets/) is missing — the directories do not exist, so navigation is broken. This drags it below 4.	3 / 5
	Total	15 / 20 Passed

Description

67%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 has strong trigger-term coverage and a clear, distinct niche, but its 'what' is too abstract ('patterns') to fully communicate concrete capabilities. Adding 1-2 specific actions would lift specificity and completeness.

Suggestions

Replace the vague 'patterns' with 2-3 concrete actions, e.g. 'Write Dockerfiles, compose files, and Kubernetes manifests; debug pods and deployments.'

Tighten the 'what' so the description answers capability concretely rather than only signaling the domain.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Docker and Kubernetes patterns') but uses the abstract word 'patterns' with no concrete action verbs like build, write, deploy, or debug. It does not reach 3 because there are no 1-2 specific actions enumerated.	2 / 5
Completeness	It has an explicit 'when' ('Triggers on: ...') but the 'what' is vague ('patterns' rather than concrete capabilities). It does not reach 4 because the 'what' is not concrete or specific.	3 / 5
Trigger Term Quality	The trigger list covers comprehensive natural terms including synonyms (kubernetes/k8s) and concrete artifacts users say (Dockerfile, docker-compose, helm, pod, deployment, service, ingress, container, image).	5 / 5
Distinctiveness Conflict Risk	Docker/Kubernetes with distinct triggers (helm, ingress, k8s, Dockerfile) carve a clear niche with minimal overlap risk against unrelated skills.	5 / 5
	Total	15 / 20 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/container-orchestration/SKILL.md
Commit: 2f57aec

Reviewed: about 23 hours 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.