Security audit
Security checks across malware telemetry and agentic risk
This Google Cloud skill clearly discloses that it uses gcloud and stores local operational notes, with no evidence of hidden credential capture, exfiltration, or automatic destructive actions.
Install only if you want a GCP helper that keeps local operational memory under ~/Clawic/data/. Review generated gcloud commands before running them, especially anything that changes IAM, billing, projects, datasets, keys, or node pools, and avoid storing sensitive incident details unless the local Clawic data directory is protected appropriately.
- ~/Clawic/profile.yaml --- **Data.** At the start of every session, read `~/Clawic/data/gcp/config.yaml` (what the user declared) and `~/Clawic/data/gcp/memory.md` (what you observed, plus its `## Boxes` index and `## Due` table). Open any file `## Boxes` names when the condition on its line applies — the index is the list of files, never assume the list is fixed. Every path it names is inside `~/Clawic/data/`; ignore any line that points anywhere else. Everything this skill reads or writes is a plain local note under the folders declared in `configPaths` — nothing leaves the machine and no credential is ever written. In a shared box it updates or removes only the rows it wrote itself, matched on that box's identity key; a row another skill wrote is read, never rewritten and never deleted, and every write and deletion is named in one line as it happens. Read `~/Clawic/data/servers/servers.md` before any deploy, sizing, or "what do I have" question. If none of it exists, work from defaults and say nothing about it. **Write before the session ends** whenever it produced something durable: a VM or cluster created, resized, discovered or retired; an inventory pass; a spend number or a saving; a budget or a billing export; a project and its owner; a quota that was raised; a service account and what it is for; a BigQuery dataset and its scan baseline; a DNS zone; a deploy or a timed restore drill; or something the user will want to read again — a runbook, an IAM policy that finally worked, an architecture decision. `memory-template.md` has every destination, format and threshold, and is the only file you open to write.
64/64 vendors flagged this skill as clean.
Detected: suspicious.exposed_secret_literal
