Gws Events Subscribe Skill Security Audit

The Skill explicitly streams Workspace events as NDJSON and can write every event to a local directory; its example subscribes to chat-message creation events. If the user enables `--output-dir` or terminal output is logged, event payloads may remain in local files or logs. The source does not show the payload schema, so it does not prove message bodies are included. Users can ask for documented fields and retention behavior and restrict output to a protected temporary directory.

The `--no-ack` description indicates that pulled messages are acknowledged by default, and the command can use an existing subscription. Acknowledgment changes delivery state for that Pub/Sub subscription and may prevent other consumers sharing it from receiving those messages again; this does not establish an effect on separate subscriptions. Users can use a dedicated subscription or `--no-ack` and ask the author to document acknowledgment timing and failure handling.

The documentation says the command can set up Pub/Sub resources in a specified GCP project: by default they persist, while `--cleanup` deletes resources it created on exit. This can create ongoing cost or permission exposure, or cause loss of those created resources during cleanup; the word “created” does not show that pre-existing resources are deleted. Users should confirm the project, resource names, cost, and cleanup scope before execution; the Skill itself requires confirmation.

This Skill delegates authentication, global flags, and security rules to an adjacent Skill absent from the supplied source, and instructs running a generator if it is missing. Because neither the shared file nor generated output is included, users cannot verify the instructions, generated files, or credential handling from this evidence. This does not prove malicious behavior, but it is an unverified dependency that should be reviewed before execution; users can request a pinned shared file and the generator’s provenance.