container-cve

High-impact container-runtime CVE catalog — runC Leaky Vessels (CVE-2024-21626/-23651/-23652/-23653), CVE-2022-0185 (FUSE/legacy-fs), CVE-2019-5736 (runC binary replace), CRI-O Dirty COW analogs, Kubernetes API server CVE-2019-11247 (custom-resource RBAC bypass). Fingerprint → match → exploit.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/cloud/container/container-cve/SKILL.md

Quality

Content

57%

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

The body is well-structured and lean with several genuinely executable examples, but it loses points for time-sensitive version numbers outside a deprecated section, incomplete code for several CVE entries, and a missing validation feedback loop in the workflow.

Suggestions

Add an explicit validation/feedback step to the workflow, e.g. after a failed exploit, re-check the fingerprinted kernel/runtime version against the affected range before retrying.

Replace bare PoC GitHub links for CVE-2022-0185, CVE-2019-5736, and the CVE-2024-23651 family with at least a minimal executable snippet or a one-line reproduction command.

Consider isolating the affected-version tables in a dated 'Catalog' section or noting a maintenance date so time-sensitive version data does not penalize conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's knowledge (no preamble explaining runC or CVEs), but it is dense with time-sensitive version numbers (runC < 1.1.12, Docker < 25.0.3, etc.) that are not isolated in a deprecated/old-patterns section, which the rubric penalizes.	2 / 3
Actionability	The fingerprint commands, the Leaky Vessels Dockerfile, and the CRI-O pod YAML are concrete and executable, but several catalog entries (CVE-2022-0185, CVE-2019-5736, CVE-2024-23651 family) provide only a PoC link or a prose primitive rather than working code.	2 / 3
Workflow Clarity	A clear 4-step sequence exists with a 'try in a copy of the target environment first' checkpoint, but there is no explicit validate→fix→retry feedback loop for these destructive exploit operations, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files are present and the single self-contained file is organized into clear sections (Fingerprint, Catalog, Workflow, OPSEC, References) with one-level-deep external URL references and no nested indirection.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 is highly specific and distinctive, naming concrete CVEs and primitives, but it is missing an explicit 'when to use' trigger clause and leans on technical CVE identifiers over natural user phrasing.

Suggestions

Add a 'Use when...' clause stating when to invoke this skill, e.g. 'Use when fingerprinting a container runtime to find a matching escape/exploit CVE.'

Include natural trigger terms a user would actually say, such as 'container escape', 'container breakout', or 'runc privilege escalation', alongside the CVE identifiers.

Dimension	Reasoning	Score
Specificity	Names concrete CVEs (CVE-2024-21626, CVE-2022-0185, CVE-2019-5736) with specific primitives and the explicit action chain 'Fingerprint → match → exploit', matching the multiple-specific-actions anchor.	3 / 3
Completeness	Clearly states what the skill is (a CVE catalog with enumerated entries) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes relevant CVE numbers and product names (runC, Leaky Vessels, CRI-O) but leans on technical identifiers rather than natural phrases a user would say like 'container escape' or 'container breakout'; common variations are missing.	2 / 3
Distinctiveness Conflict Risk	The container-runtime CVE niche with specific CVE identifiers is sharply distinct and unlikely to trigger for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	10 / 12 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/container-cve/SKILL.md
Commit: e34afba

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