CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

terraform-state-leak

Exploit exposed Terraform state files — secrets, cloud creds, RDS passwords, IAM keys, and infrastructure topology in plain JSON.

Quality

76%

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/terraform-state-leak/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a dense, highly actionable runbook: real discovery, parsing, validation, and pivoting commands organized in a clear numbered workflow with an embedded credential-validation checkpoint. Weaknesses are minor — unexplained internal tooling calls (tfstate_audit, kg_add_node), undefined shell variables in the RDS pivot, and reference-worthy sections (remediation, exemplars) inlined in the main file.

Suggestions

Replace or annotate the environment-specific calls (tfstate_audit, kg_add_node/kg_add_edge) with a note on what tool provides them or standard equivalents, since they are not executable as written.

Define how $USER/$PASSWORD/$AKID/$SK are populated in sections 4-5 (e.g. sourcing from /tmp/tf-secrets.txt) to make the pivot commands fully copy-paste ready.

Move "Defender remediation" and "Known exemplars" into a references/ file and link them from the body to keep SKILL.md a leaner overview.

DimensionReasoningScore

Conciseness

The body is dominated by lean, copy-paste command blocks and terse lists with almost no padding. It is not 5 because the opening explanation of what a tfstate file contains, the misconfiguration list, and the "Known exemplars"/"Defender remediation" sections carry background Claude largely knows or could infer, adding tokens beyond what is strictly needed.

4 / 5

Actionability

Nearly every section gives concrete executable commands (curl path loop, feroxbuster, aws s3 ls, jq extraction filters, sts get-caller-identity, mysql/psql connect, terraform backend config, BFG). It is not 5 because "tfstate_audit(...)" and "kg_add_node(...)" invoke unexplained external tooling, and section 5 uses undefined $USER/$PASSWORD placeholders; it is well above 3 because the commands are real and complete rather than pseudocode.

4 / 5

Workflow Clarity

A clear numbered sequence 1-6 (discover → parse → topology → validate creds → pivot → promote) with an explicit validation checkpoint in step 4 (sts get-caller-identity "confirmed live cred" if the ARN returns). It is not 5 because there are no explicit validate-and-retry loops or checks that a downloaded state file is valid before parsing, and not 3 because the sequence and one key credential-validation checkpoint are present.

4 / 5

Progressive Disclosure

This is a single-file skill (no references/, scripts/, or assets/ exist) with clear, well-ordered section headers and a one-level-deep cross-skill pointer (aws-iam-enum/SKILL.md). It is not 5 because at ~175 lines, content such as "Defender remediation" and "Known exemplars" could be split into separate reference files to keep SKILL.md a leaner overview.

4 / 5

Total

16

/

20

Passed

Description

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

The description is concrete, specific, and highly distinctive, clearly conveying what the skill does and what it yields. Its main weakness is the absence of an explicit "Use when…" trigger clause, which both caps completeness and leaves a few natural trigger synonyms (tfstate, leaked state) out of the description text itself.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when a Terraform state file (.tfstate / tfstate.backup) is found exposed in a bucket, web root, or Git history."

Include the natural synonym "tfstate" and file extensions (.tfstate, tfstate.backup) in the description text itself, not only in the when_to_use metadata.

Name one or two concrete actions beyond the single verb "Exploit" (e.g. "extract and validate IAM keys and RDS passwords") to sharpen the what-clause.

DimensionReasoningScore

Specificity

"Exploit exposed Terraform state files — secrets, cloud creds, RDS passwords, IAM keys, and infrastructure topology in plain JSON" names the domain and enumerates several concrete capabilities (secret/credential extraction, topology disclosure). It falls between anchor 3 (1-2 concrete actions) and anchor 5 (comprehensive multi-action coverage) because a single verb "Exploit" covers the enumerated objects, with minor gaps in action coverage.

4 / 5

Completeness

The "what" is explicit (exploit exposed Terraform state files for secrets and topology), but the description contains no "Use when…" clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" is fully clear, and not 4 because the "when" is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

"Terraform state files", "secrets", "cloud creds", "RDS passwords", "IAM keys" are natural terms a user would say. A few natural variations ("tfstate", ".tfstate", "leaked state") are missing from the description itself — they appear only in the separate when_to_use metadata field — so it matches anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Terraform state files" with IAM keys and RDS passwords defines a clear niche with distinct triggers and minimal conflict risk with other skills, matching the anchor-5 example of a clear niche.

5 / 5

Total

16

/

20

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.

Validation — 14 / 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

Path

packages/decepticon/decepticon/skills/standard/cloud/terraform-state-leak/SKILL.md

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.