SKILLEMALL.ai

CC enumerating-cloud-with-cloudfox

Run CloudFox's read-only Describe/List/Get enumeration (all-checks, role-trusts, secrets, endpoints, and permissions commands) to map AWS and Azure attack paths and surface exploitable misconfigurations. Use immediately after obtaining a cloud credential to build situational awareness, find exposed resources and secrets, or map sts:AssumeRole trust relationships for lateral-movement/privilege-escalation planning.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 5 files · 1 script body ≈ 2 258 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Run CloudFox's read-only Describe/List/Get enumeration (all-checks, role-trusts, secrets, endpoints, and permissions commands) to map AWS and Azure attack…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

AnalyzerAWSAzureGitHubSecuritytype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
95
Quality 40%
81
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

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 · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Risky intent intent-offensive-security SKILL.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - cloud-pentest
    • low Risky intent intent-offensive-security SKILL.md:29
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      > **Legal Notice:** This skill is for authorized cloud penetration testing and assessment only. CloudFox makes read/describe API calls against the cloud account whose credentials you supply. Run it ON
    • low Risky intent intent-offensive-security SKILL.md:43
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      - Mapping `sts:AssumeRole` trust relationships to plan lateral movement / privesc
    • low Risky intent intent-offensive-security SKILL.md:182
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      2. Open `role-trusts` first — it reveals the assume-role graph for lateral movement.
    • low Risky intent intent-offensive-security SKILL.md:185
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      5. Feed confirmed assume-role / privesc candidates into Pacu for active exploitation.

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

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "nist_csf"
    • note frontmatter-key unknown frontmatter key "mitre_attack"

    Process rating: all ten parameters 51/100

    • 0Result and completion. Does not say what the result is
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 1 mutating operations with no state check
    • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Steps. 33 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2258 tokens
    • low 11 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
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -42 reference files, but SKILL.md never points to them: the model will not open them
    • +2Single-language instructions
    • +3Description length 416: enough signal without eating the budget
    • +4Structure: 21 headings
    • +3Step-by-step instructions: 33 items
    • +4Has examples (11 code blocks)
    • +3All 1 scripts are documented
    • +1License stated

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