CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aws-iam-enum

Enumerate AWS IAM policies, detect privilege escalation paths per Rhino Security Labs canonical 21 primitives.

Quality

74%

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/aws-iam-enum/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, well-sequenced enumeration runbook with genuinely useful canonical content (the 21 Rhino Security privesc primitives, concrete aws CLI commands, worked escalation chains). It is held back by undefined tool invocations (iam_policy_audit, kg_add_node) presented without context, unsubstituted placeholders, and a complete absence of validation/error-handling checkpoints for the multi-step workflow.

Suggestions

Explain or ground the iam_policy_audit() and kg_add_node()/kg_add_edge() calls — either name the tool/script they invoke (and bundle it in scripts/) or replace them with concrete, executable equivalents; currently they read as unexplained pseudocode.

Add validation checkpoints to the workflow: handle AccessDenied on get-policy-version gracefully, confirm policy JSON downloaded before auditing, and paginate/iterate explicitly over all attached policies rather than leaving ME/ARN/VID as unsubstituted placeholders.

Consider moving the 21-primitive canonical list to a references/ file (e.g., references/privesc-primitives.md) and keeping a short 'how to check' summary inline, to improve progressive disclosure and keep SKILL.md as an overview.

DimensionReasoningScore

Conciseness

The body is lean throughout: no padding, no explanation of AWS/IAM basics Claude already knows, and every section (identity check, policy retrieval, the 21-primitive list, graph promotion, common chains) carries non-obvious information that earns its place — matching anchor 5's "every token earns its place".

5 / 5

Actionability

The aws CLI commands are concrete but rely on unsubstituted placeholders (ME, ARN, VID), and the guidance mixes in non-executable calls with no explanation: "iam_policy_audit(open("/tmp/policy.json").read())" is an undefined function dropped into a bash flow, and "kg_add_node(... src=<vuln> ...)" is environment-specific pseudocode — matching anchor 3's "some concrete guidance but incomplete; pseudocode instead of executable code" rather than anchor 4's mostly-executable bar.

3 / 5

Workflow Clarity

The five sections form a coherent sequence (identify → gather policies → check primitives → promote to graph → note chains), but validation checkpoints are entirely absent: there is no handling of the extremely common AccessDenied errors on iam get-policy-version, no check that policy retrieval succeeded before auditing, and no verification step after graph promotion — matching anchor 3's "sequence present but checkpoints missing".

3 / 5

Progressive Disclosure

Sections are well-organized with clear headers and the skill is self-contained (no bundle files exist to reference), which per the rubric can approach 5; however, the 21-primitive enumeration (item 11 of the guidelines rewards reference material placed appropriately) is exactly the kind of stable reference data that could live in a references/ file, so organization is good but not optimal — anchor 4.

4 / 5

Total

15

/

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.

A tight, domain-specific description that clearly states what the skill does and cites a canonical methodology, with good natural keywords (AWS, IAM, privilege escalation). Its main weakness is the absence of any explicit "Use when..." trigger clause in the description field itself, which caps completeness at 3 despite the separate when_to_use metadata field.

Suggestions

Add an explicit "Use when..." clause to the description, e.g., "Use when auditing AWS IAM permissions, hunting privilege escalation paths, or reviewing IAM policies for over-privileged access" — this would lift completeness from 3 to 5.

Include common user phrasings like "privesc" and "permission audit" as trigger terms to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

The description names two concrete actions — "Enumerate AWS IAM policies" and "detect privilege escalation paths" — anchored to a specific methodology ("Rhino Security Labs canonical 21 primitives"), which is more specific than anchor 3's bare action list; however, it stays slightly below anchor 5 because it doesn't cover related enumeration surface (users, roles, groups) or what output the detection produces.

4 / 5

Completeness

The "what" is clear (enumerate AWS IAM policies, detect privilege escalation paths), but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; per anchor 3, a clear 'what' with 'when' missing or only weakly implied.

3 / 5

Trigger Term Quality

Natural phrases a user would say are present: "AWS", "IAM", "policies", "privilege escalation" — solid keyword coverage, though common variations users actually say like "privesc", "permission audit", or "IAM misconfiguration" are missing, keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The AWS IAM privilege-escalation niche is highly specific and unlikely to trigger for the wrong skill; the phrase "Rhino Security Labs canonical 21 primitives" pins it to a distinct, well-known methodology, matching anchor 5's clear niche with minimal conflict risk.

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/aws-iam-enum/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.