managing-container-registries

Execute use when you need to work with containerization. This skill provides container management and orchestration with comprehensive guidance and automation. Trigger with phrases like "containerize app", "manage containers", or "orchestrate deployment".

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/devops/container-registry-manager/skills/managing-container-registries/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The body is concise and well-structured with useful error-handling and examples sections, but it stops short of executable code and omits validation checkpoints for destructive registry operations, while failing to link the bundled helper scripts.

Suggestions

Add at least one copy-paste-ready example (e.g. a Terraform ECR block with scan-on-push and lifecycle policy, or an ECR lifecycle-policy JSON snippet).

Insert validation/dry-run checkpoints before destructive steps, e.g. 'preview lifecycle policy with aws ecr get-lifecycle-policy-preview before applying'.

Reference the bundled scripts from the body (e.g. 'Run scripts/create_registry.sh to provision ECR/GCR/Harbor') so the progressive-disclosure bundle is actually navigable.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned without explaining concepts Claude already knows; each section (Prerequisites, Instructions, Error Handling, Examples) earns its place.	3 / 3
Actionability	It names concrete tools and commands (e.g. 'docker-credential-ecr-login', 'gcloud auth configure-docker', 'ECR scan-on-push'), but provides no executable, copy-paste code blocks or example lifecycle-policy JSON/Terraform.	2 / 3
Workflow Clarity	The 9-step Instructions give a clear sequence, but destructive/batch operations (lifecycle auto-delete, cleanup) lack explicit validation or dry-run checkpoints, capping the score.	2 / 3
Progressive Disclosure	Sections are well organized, but the bundled scripts listed in scripts/README (create_registry.sh, cleanup_registry.sh, etc.) are never referenced or linked from the body, so the structure is underused.	2 / 3
	Total	9 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 includes explicit trigger phrasing and names a domain, but it is padded with buzzwords, describes container orchestration rather than registry management, and uses abstract action language that weakens specificity and distinctiveness.

Suggestions

Replace 'container management and orchestration with comprehensive guidance and automation' with concrete registry actions such as 'push, tag, replicate, scan, and retire images across ECR, Artifact Registry, ACR, Docker Hub, and self-hosted registries'.

Align trigger phrases with the skill's real purpose, e.g. add 'set up a container registry', 'configure ECR lifecycle policy', 'replicate registry images'.

Remove fluff ('comprehensive guidance and automation') and state the registry-management niche explicitly to reduce overlap with orchestration skills.

Dimension	Reasoning	Score
Specificity	Names the container domain and the actions 'management and orchestration', but these are abstract nouns padded with fluff like 'comprehensive guidance and automation' rather than concrete capabilities.	2 / 3
Completeness	It states a 'what' and an explicit 'Execute use when...' trigger clause, but the 'what' is vague ('container management and orchestration with comprehensive guidance and automation') and mischaracterizes the registry-focused skill.	2 / 3
Trigger Term Quality	Offers three natural phrases ('containerize app', 'manage containers', 'orchestrate deployment'), but coverage is thin and the terms target orchestration rather than the skill's actual registry-management focus.	2 / 3
Distinctiveness Conflict Risk	'Container management and orchestration' is a generic framing that overlaps heavily with Docker/Kubernetes/deployment skills, and the registry niche is not surfaced in the description.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/devops/container-registry-manager/skills/managing-container-registries/SKILL.md
Commit: bddba3c

Reviewed: 3 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.