Skip to content
TrustedSkillsbeta
Back to all skills

Gcp Logs Monitoring

Checked
bcrema·vlatest·cloud

Helps with Google Cloud, monitoring as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bcrema/runwarapp --skill gcp-logs-monitoring -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bcrema

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 bcrema/runwarapp at 70660dcaf1.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
70660dcaf1
Manifest
.agents/skills/gcp-logs-monitoring/SKILL.md
Scanned
5 files, 325 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to monitor Google Cloud Platform (GCP) logs. It can query and analyze log data, providing insights into application behavior and system health. Specifically, the agent can retrieve log entries based on various criteria and present them in a structured format for analysis.

When to use it

  • Troubleshooting application errors by querying specific error messages within GCP logs.
  • Monitoring resource utilization (CPU, memory) of deployed applications using relevant log metrics.
  • Identifying security threats by analyzing audit logs for suspicious activity.
  • Generating reports on system performance based on aggregated log data.

Key capabilities

  • Querying GCP Logs
  • Analyzing Log Data
  • Retrieving Log Entries
  • Structured Presentation of Log Information

Example prompts

  • "Show me all error logs from the last hour for my web application."
  • "What is the average latency reported in the application logs?"
  • "Find any log entries containing 'failed authentication'."

Tips & gotchas

  • Requires appropriate GCP permissions to access and query logs.
  • Log queries can be resource-intensive; optimize queries for efficiency.