Skillv1.0.12

ClawScan security

Recipe Share Event Materials · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

BenignMar 31, 2026, 6:37 PM

Verdict: Benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requests and instructions are coherent with its stated purpose (sharing Drive files with Calendar event attendees); it is instruction-only, requires the gws CLI and related gws skills, and otherwise does not demand unexpected privileges.
Guidance: This recipe is internally consistent, but take these precautions before installing/using it: ensure the gws CLI and the gws-calendar and gws-drive skills are installed and properly authenticated to the Google account you intend to use; verify how those skills store credentials (OAuth tokens, files, etc.). When running the recipe, confirm EVENT_ID and FILE_ID are correct and review the attendee list before applying permissions — this action will share files with those emails and can expose sensitive data. The SKILL.md provides an example of granting a single 'reader' permission; make sure you intend that role and that you or the agent will iterate over all attendees. Also note a minor metadata mismatch (SKILL.md version 0.22.5 vs registry version 1.0.12) — this looks like a packaging/versioning inconsistency to check but does not affect functionality.

Purpose & Capability: okName/description match the actions in SKILL.md: the recipe uses the gws CLI to read a Calendar event's attendees and create Drive permissions for each attendee. Requiring the gws binary and the gws-calendar and gws-drive skills is proportionate for this functionality.
Instruction Scope: noteInstructions are narrowly scoped to running three gws commands (get event attendees, create a permission entry, list permissions). They do not reference unrelated files, environment variables, or external endpoints. Note: the SKILL.md shows example single-email substitution rather than an explicit loop; the recipe assumes the agent or user will iterate over attendees and supply EVENT_ID/FILE_ID.
Install Mechanism: okInstruction-only skill with no install spec and no code files — lowest install risk. It simply requires the gws binary to be present; nothing is downloaded or written by the skill itself.
Credentials: noteThe skill declares no required environment variables or credentials. In practice, the gws CLI (and the gws-calendar / gws-drive skills) will need authenticated access to the user's Google account; that auth is not declared here but is reasonably provided by the referenced gws skills. Users should confirm how those gws skills obtain/store Google credentials.
Persistence & Privilege: okalways is false and the skill is user-invocable. It does not request persistent system presence or attempt to modify other skills or global settings.