k8s-pivot

Kubernetes attack playbook — service-account token theft, RBAC abuse, pod escape, hostPath mount abuse, kube-api-server pivoting.

Quality

73%

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/k8s-pivot/SKILL.md

Quality

Content

80%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 playbook is highly actionable and token-efficient, with executable commands and a clear numbered sequence, but it is a monolithic single file with no progressive disclosure and no validation checkpoints for its destructive and batch operations. Splitting reference material into bundled files and adding verify-before-proceed steps would lift the two capped dimensions.

Suggestions

Add validation/verification checkpoints to destructive and batch steps, e.g. confirm the escape pod is Running before exec, verify a stolen token with `auth can-i` before escalation, and check `get secrets` output integrity before exfil.

Move the container-runtime-escape table, CVSS scoring, and defender-remediation sections into bundled reference files (e.g. escapes.md, scoring.md) referenced one level deep from SKILL.md.

Resolve the `$(cat .../namespace)` shorthand to its full path so the inventory commands are literally copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean command/comment prose with no explanation of concepts Claude already knows (what a pod or RBAC is); comments are terse and operational, so every token earns its place.	3 / 3
Actionability	Provides fully executable kubectl/jq commands and a copy-paste-ready escape-pod YAML manifest, plus tables mapping primitives to concrete techniques.	3 / 3
Workflow Clarity	The eight numbered sections give a clear sequence, but destructive/batch operations (secrets harvest, privileged pod creation, clusterrolebinding patching) lack any explicit validation or verification checkpoint, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Sections are well organized, but no bundle files exist and all content (RBAC tables, container escapes, OPSEC, CVSS, defender remediation) sits inline in a single ~150-line file rather than being split into one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

67%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 is specific and distinctive, naming five concrete Kubernetes attack actions, but it omits any explicit 'Use when...' trigger guidance and relies on technical jargon over the natural keyword variations a user would say. Moving the metadata.when_to_use terms into the description would lift both completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when pivoting through a compromised Kubernetes/k8s cluster, escaping pods, or abusing RBAC for lateral movement and cluster-admin escalation.'

Add natural keyword variations users actually say ('k8s', 'container escape', 'lateral movement', 'cluster compromise') rather than only technical terms like 'hostPath mount abuse'.

Fold the metadata.when_to_use terms into the description so the trigger guidance is visible where the rubric and skill-discovery expect it.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'service-account token theft, RBAC abuse, pod escape, hostPath mount abuse, kube-api-server pivoting' — matching the anchor for several specific concrete actions.	3 / 3
Completeness	The 'what' is clear (attack playbook with named actions), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description itself, which caps completeness at 2.	2 / 3
Trigger Term Quality	'Kubernetes' and 'pod escape' are natural, but 'hostPath mount abuse' and 'kube-api-server pivoting' lean technical, and common variations like 'k8s', 'container escape', and 'lateral movement' are absent (they live only in metadata.when_to_use, not the description).	2 / 3
Distinctiveness Conflict Risk	'Kubernetes attack playbook' carves a clear niche with k8s-specific triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	10 / 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/cloud/k8s-pivot/SKILL.md
Commit: e34afba

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