container-overview

Container / Kubernetes attack category — pod escape, RBAC abuse, runtime CVE exploitation, socket-mount escape. Routing skill: identify the surface (pod-internal RCE vs API-level vs build-pipeline), then load the matching sub-skill.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

86%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.

A tight, well-structured routing skill body that excels at conciseness and progressive disclosure, with clear routing logic; only minor gaps in directly executable attack commands and explicit feedback loops.

Dimension	Reasoning	Score
Conciseness	Lean ~35-line routing doc using tables and an ASCII decision tree; assumes Claude's competence and explains no concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	Provides concrete, copy-paste-ready load_skill(".../SKILL.md") paths and a named tooling table, but the actual executable attack commands are deferred to the sub-skills by design, leaving a minor gap.	4 / 5
Workflow Clarity	Clear identify-surface → route sequence with an explicit decision tree covering each branch; routing is not itself a destructive operation so the cap is not forced, though no explicit validate/feedback loop is present.	4 / 5
Progressive Disclosure	A clear overview that routes to one-level-deep sub-skill SKILL.md files via well-signaled load_skill paths in a structured table, with content appropriately split and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

75%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.

A specific, well-scoped routing description with strong trigger terms and clear distinctiveness, weakened only by the absence of an explicit "Use when..." trigger clause that caps completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the target is a container or Kubernetes cluster (pods, RBAC, mounted sockets, or vulnerable runtimes)."

Fold a few common synonyms (k8s, docker, podman) into the description itself rather than relying solely on metadata.when_to_use.

Dimension	Reasoning	Score
Specificity	Names the container/k8s attack domain and lists multiple concrete attack categories — "pod escape, RBAC abuse, runtime CVE exploitation, socket-mount escape" — plus three distinct routing surfaces, giving comprehensive coverage.	5 / 5
Completeness	The "what" is clear (attack category + routing mechanism), but there is no explicit "Use when..." trigger clause; per the judging guideline, a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Strong natural keyword coverage ("Container / Kubernetes", "pod escape", "RBAC", "CVE", "socket-mount", "RCE"), but common synonyms like "k8s", "docker", and "podman" appear only in metadata.when_to_use rather than the description itself.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear container/kubernetes attack niche with distinct, specific triggers and minimal overlap risk with other skill categories.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/cloud/container/SKILL.md
Commit: 0cf691e

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