Gcp Audit Logs
CheckedHelps with Google Cloud, auditing as part of deploying and managing cloud infrastructure workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add bagelhole/devops-security-agent-skills --skill gcp-audit-logs -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
bagelhole
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bagelhole/devops-security-agent-skills at 0365f57a07.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 0365f57a07
- Scanned
- 1 file, 459 lines
About this skill
What it does
This skill allows AI agents to query and interpret Google Cloud Platform (GCP) Audit Logs. It can extract information about resource modifications, user actions, and system events within a GCP environment. The agent can then summarize findings or trigger alerts based on these audit log entries.
When to use it
- Security Incident Investigation: Quickly identify the root cause of a security incident by analyzing audit logs for suspicious activity.
- Compliance Auditing: Generate reports demonstrating adherence to regulatory requirements by extracting relevant data from GCP Audit Logs.
- Resource Change Tracking: Monitor changes made to critical resources and identify potential configuration drift.
- User Activity Monitoring: Track user actions within the GCP environment to ensure proper access controls and identify unauthorized behavior.
Key capabilities
- Querying GCP Audit Logs
- Filtering logs by resource type, user, time range, and event category
- Summarizing audit log data
- Identifying specific events (e.g., IAM policy changes)
Example prompts
- "Show me all API calls made to my Cloud Storage bucket in the last 24 hours."
- "What IAM role assignments were changed yesterday?"
- "List all instances where a user named 'john.doe' modified a Compute Engine instance."
Tips & gotchas
- Ensure your AI agent has appropriate permissions (roles) to access GCP Audit Logs within the project you are querying.
- Audit logs can be verbose; use specific filters to narrow down results and improve performance.