CC performing-gcp-penetration-testing-with-gcpbucketbrute
Performs authorized GCP security testing using GCPBucketBrute to enumerate publicly accessible storage buckets, combined with gcloud CLI IAM enumeration to find privilege escalation paths and audit service account permissions. Use when penetration testing a GCP project for exposed buckets, overly permissive IAM bindings, or service account key exposure.
Performs authorized GCP security testing using GCPBucketBrute to enumerate publicly accessible storage buckets, combined with gcloud CLI IAM enumeration to…
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# GCP Penetration Testing API Reference
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:60Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## Privilege Escalation Permissions
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:62Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Dangerous IAM permissions that enable privilege escalation:
detector -
low Risky intent
intent-offensive-securitySKILL.md:5Offensive-security / dual-use content (legitimate for authorised testing; review intended use)find privilege escalation paths and audit service account permissions. Use when
-
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)penetration testing a GCP project for exposed buckets, overly permissive IAM bindings,
-
low Risky intent
intent-offensive-securitySKILL.md:12Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- cloud-pentesting
-
low Risky intent
intent-offensive-securitySKILL.md:41Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# Performing GCP Penetration Testing with GCPBucketBrute
-
low Risky intent
intent-offensive-securitySKILL.md:45Offensive-security / dual-use content (legitimate for authorised testing; review intended use)This skill covers Google Cloud Platform security testing using GCPBucketBrute for storage bucket enumeration and access permission testing, combined with gcloud CLI IAM enumeration to identify privile
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_ai_rmf" - note
frontmatter-keyunknown frontmatter key "atlas_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 54/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
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 497 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 355: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 19 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.