CtrlK
BlogDocsLog inGet started
Tessl Logo

cloud-overview

Cloud exploitation lane — AWS IAM privesc, S3 takeover, k8s RBAC abuse, Terraform state leaks, cloud metadata pivoting.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/cloud/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

A concise, well-structured routing catalog with executable commands and clear navigation to sub-skills, weakened by reliance on undefined audit helper functions and the absence of validation checkpoints in its sensitive workflows.

Suggestions

Define or ground the assumed audit helpers (`iam_policy_audit`, `tfstate_audit`, `k8s_audit`) and resolve the `<me>` placeholder so commands are copy-paste ready.

Add explicit validation/verification checkpoints to each workflow (e.g., confirm `get-caller-identity` output before enumerating policies, verify extracted credentials before pivoting) to lift workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a terse playbook table plus two numbered workflows with inline commands — and never explains concepts Claude already knows, matching the "every token earns its place" anchor.

3 / 3

Actionability

It gives concrete, runnable commands (e.g., `aws sts get-caller-identity`, `kubectl get pods -A -o json`, `metadata_endpoints("aws")`) but leans on undefined helper functions like `iam_policy_audit`, `tfstate_audit`, and `k8s_audit` and an unresolved `<me>` placeholder, so it is not fully copy-paste ready — matching the level-2 "some concrete guidance but incomplete" anchor.

2 / 3

Workflow Clarity

Both workflows are clearly sequenced, but they perform sensitive enumeration/privesc/credential-pivoting with no validation or verification checkpoints (e.g., confirm caller identity, verify extracted creds before pivoting), which the guidelines cap at 2; it is not level 1 because the sequence itself is explicit.

2 / 3

Progressive Disclosure

The body acts as an overview catalog that points to five well-signaled sub-skill SKILL.md paths via the Playbooks table, providing clear one-level-deep navigation appropriate to a routing skill; no bundle files exist locally to verify, so scoring is based on the references present in the body.

3 / 3

Total

10

/

12

Passed

Description

82%

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 tightly written, specific cloud-exploitation description with strong trigger terms and a clear niche, but it omits an explicit "Use when..." trigger clause, which caps its completeness at 2.

Suggestions

Append a 'Use when ...' clause to the description naming the situations that should trigger this skill (e.g., 'Use when assessing AWS/GCP/Azure cloud attack surface or pivoting from SSRF to cloud metadata').

Expand the trigger surface slightly to cover common phrasings like 'cloud privesc', 'IMDS', or 'SSRF to metadata' so users' natural queries match more reliably.

DimensionReasoningScore

Specificity

The description names five concrete exploitation primitives — "AWS IAM privesc, S3 takeover, k8s RBAC abuse, Terraform state leaks, cloud metadata pivoting" — matching the "Lists multiple specific concrete actions" anchor rather than the level-2 single-domain example.

3 / 3

Completeness

It strongly answers "what" but lacks any "Use when..." clause or equivalent explicit trigger guidance in the description itself, which the guidelines cap at 2; it is not level 1 because the what-side is concrete and comprehensive.

2 / 3

Trigger Term Quality

It surfaces the natural terms a user would say (cloud, aws, iam, s3, k8s, terraform, metadata) with good coverage of common variations; it is not level 2 because it goes beyond a single keyword to a spread of recognizable terms.

3 / 3

Distinctiveness Conflict Risk

The "Cloud exploitation lane" framing carves a clear niche with distinct cloud-specific triggers unlikely to fire for non-cloud skills, matching the "clear niche with distinct triggers" anchor.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.