CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

s3-takeover

Detect and claim dangling S3 buckets referenced by subdomains (CNAME → s3 hostnames where bucket no longer exists).

Quality

71%

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/s3-takeover/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 strong, action-dense playbook: a numbered workflow with real verification steps, race-condition error handling, safe-PoC guardrails, and cleanup, plus a defender remediation section. Weaknesses are minor: undefined environment-specific helpers (s3_takeover_check, kg_* graph calls), unset shell variables in the verify snippet, and supplementary sections (CVSS, remediation, exemplars) inlined that could be split out.

DimensionReasoningScore

Conciseness

The body is command-driven and lean, with only minor trimmable content: the 2-sentence intro restates takeover mechanics Claude already knows, and the dated "Known exemplars" trivia is not operational. This fits 'efficient; minor instances of over-explanation' rather than the padding at 2 or the every-token-earns-its-place ideal at 5.

4 / 5

Actionability

Mostly executable copy-paste commands (subfinder/dig enumeration loop, curl NoSuchBucket checks, aws s3api create-bucket, remediation jq pipeline), but with minor gaps: s3_takeover_check() and kg_add_node/kg_add_edge reference environment-specific helpers not defined in the skill, and $SUBDOMAIN/$CNAME are used without being set. This matches 'mostly executable guidance; concrete code with minor gaps' at 4, not the fully-ready anchor at 5.

4 / 5

Workflow Clarity

A clearly numbered sequence (enumerate → verify dangling → claim → safe PoC → frame impact → promote) with explicit verification (step 2), error-recovery feedback for BucketAlreadyExists race conditions, a DO/DO-NOT checklist, and cleanup (aws s3 rb --force). The only minor gap is that post-claim verification is a comment ("# Now curl ... returns your content") rather than a runnable check, fitting anchor 4 rather than 5; validation is present, so the destructive-workflow cap at 3 does not apply.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-labeled sections, which is appropriate structure; the minor gap is that defender remediation, CVSS scoring, and known exemplars could be split into reference files to keep the core offensive workflow lean. This matches 'good structure; most content appropriately placed; minor organization gaps' at 4 rather than the ideal split at 5.

4 / 5

Total

16

/

20

Passed

Description

57%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 specific and highly distinctive for its niche, with accurate technical framing of the CNAME/dangling-bucket mechanism. Its main weaknesses are the absence of an explicit 'Use when...' clause in the description field and of the natural trigger phrase "subdomain takeover" that users would most likely say.

Suggestions

Append an explicit trigger clause to the description, e.g. "Use when checking for subdomain takeover, dangling DNS records, or unclaimed S3 buckets during recon."

Include the natural user phrase "subdomain takeover" (and the synonym "S3 takeover") in the description rather than only in metadata.when_to_use, so the description alone carries the trigger terms.

Consider adding a third concrete capability (e.g. verify, claim, or demonstrate impact) to lift the action coverage from 1-2 actions toward a comprehensive list.

DimensionReasoningScore

Specificity

"Detect and claim dangling S3 buckets referenced by subdomains (CNAME → s3 hostnames where bucket no longer exists)" names the domain and two concrete actions (detect, claim) with the CNAME mechanism, but does not list several actions — matching the 1-2-actions anchor rather than the 'several specific actions' anchor at 4.

3 / 5

Completeness

The 'what' is clear ("Detect and claim dangling S3 buckets referenced by subdomains"), but the description field contains no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guideline; the when_to_use metadata sits outside the description itself.

3 / 5

Trigger Term Quality

Relevant keywords are present ("dangling S3 buckets", "subdomains", "CNAME"), but the most natural user phrases — "subdomain takeover" and "S3 takeover" — are absent from the description field ("takeover" only appears in metadata.when_to_use, not the description), so common variations are missing per the anchor-3 example.

3 / 5

Distinctiveness Conflict Risk

The combination of "dangling S3 buckets", "CNAME → s3 hostnames", and "subdomains" defines a clear niche with distinct triggers and minimal overlap with other skills, matching the anchor-5 'clear niche with distinct triggers' example.

5 / 5

Total

14

/

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/s3-takeover/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.