SKILLEMALL.ai
GitHub ↗ RU Sign in

CC cloud-iam-deep

Cloud IAM red-team attack chain across AWS, Azure, GCP

sickn33/agentic-awesome-skills Agent Skills author: sickn33 MIT 2 files body ≈ 4 717 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Cloud IAM red-team attack chain across AWS, Azure, GCP

As a process C 61/100 · Has gaps — weak spots: result and completion, failures and branches, running it twice

IntegrationKubernetesAWSGoogle CloudAzureSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
87
Quality 40%
87
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

The same skill appears in 2 more places: agentic-awesome-skills, agentic-awesome-skills

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 13

    ✓ No critical or high findings

    Medium and low: 13
    • low Risky intent intent-offensive-security references/details.md:95
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      4. **HackTricks Cloud — `aws-cognito-unauthenticated-enum`** — canonical playbook covering Steps 1-5. [cloud.hacktricks.wiki](https://cloud.hacktricks.wiki/en/pentesting-cloud/aws-security/aws-unauthe
    • low Secrets in code secret-private-key SKILL.md:76
      Private key material (placeholder value)
      "private_key": "-----BEGIN PRIVATE KEY----- …
      placeholder
    • low Risky intent intent-offensive-security SKILL.md:97
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      # 2. WHAT can I do? (the privesc question)
    • low Risky intent intent-offensive-security SKILL.md:123
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## AWS privesc patterns (24+ documented — `iam_privesc` techniques)
    • low Secrets in code secret-high-entropy-token SKILL.md:194
      High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
      curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aw…ds: 21600"
      quoted
    • low Exfiltration net-credential-use SKILL.md:196
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -H "X-aw…en: $TOKEN" http://169.254.169.254/latest/meta-data/iam/security-credentials/
      security skill
    • low Exfiltration net-credential-use SKILL.md:242
      Credential used in a network call (verify the destination is the intended service) (destination is a well-known publishing service; documentation of a security skill; the skill's own vendor host)
      curl -H "Authorization: Bearer $TOKEN" "https://management.azure.com/subscriptions?api-version=…"
      known servicesecurity skillvendor-host
    • low Risky intent intent-offensive-security SKILL.md:256
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## Azure privesc patterns
    • low Risky intent intent-offensive-security SKILL.md:299
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ## GCP privesc patterns
    • low Exfiltration net-credential-use SKILL.md:327
      Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)
      curl -H "Authorization: Bearer $TOKEN" \
      security skill
    • low Risky intent intent-offensive-security SKILL.md:350
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      ### K8s privesc patterns

    A further 2 matches are quotations in this security skill's documentation and are not counted as findings.

    Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "risk"
    • note frontmatter-key unknown frontmatter key "source"
    • note frontmatter-key unknown frontmatter key "source_repo"
    • note frontmatter-key unknown frontmatter key "source_type"
    • note frontmatter-key unknown frontmatter key "date_added"
    • note frontmatter-key unknown frontmatter key "license_source"
    • note frontmatter-key unknown frontmatter key "sources"
    • note frontmatter-key unknown frontmatter key "report_count"
    • note edit-residue the text marks something as outdated (lines 168): check that old rules are not kept next to new ones — the full check reads the text for contradictions

    Process rating: all ten parameters 61/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 30Running it twice. 25 mutating operations with no state check
    • 60Tools and files. Uses tools (web, node) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4717 tokens
    • 100Steps. 29 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Progress reporting. Reports progress
    • low 21 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +3Description length 54: 120–800 characters recommended
    • +3Output format is not stated: the model decides each time
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +4Structure: 23 headings
    • +3Step-by-step instructions: 29 items
    • +4Has examples (10 code blocks)
    • +4Reference files are cited in the instructions (1 of 1)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.