Back to skill
Skillv1.0.1
ClawScan security
Google Sheets Reporting · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignMar 3, 2026, 5:53 PM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill's requirements and runtime instructions are consistent with its stated purpose (reading Google Sheets, computing simple aggregates, and sending email reports/alerts); nothing in the package attempts to access unrelated systems or exfiltrate data to unknown endpoints.
- Guidance
- This skill appears to be what it says: it reads Google Sheets and emails formatted reports/alerts. Before installing: 1) Confirm the REPORT_EMAIL recipient is correct and safe (alerts may include snippets of row data). 2) Use minimal-permission Google credentials (restrict to the specific Sheet) and an SMTP account dedicated to automated reports. 3) Review and set ALERT_THRESHOLDS to avoid noisy alerts and to ensure numeric column names match your sheet. 4) Inspect the workflows in your n8n instance and test on a non-production sheet to verify no sensitive fields are included in alert emails. 5) Note minor metadata inconsistencies (owner/version fields differ across files); this is not a security issue by itself but worth verifying the source if you require provenance.
Review Dimensions
- Purpose & Capability
- okName/description (Google Sheets reporting) align with what the workflows do: read sheets via Google OAuth2, compute aggregates/threshold checks in n8n Code nodes, and send email via SMTP. Required credentials (Google Sheets OAuth2, SMTP) and env vars (REPORT_EMAIL, ALERT_THRESHOLDS) are appropriate for this purpose.
- Instruction Scope
- noteInstructions and workflow code stay within scope (read sheet rows, compute stats, build HTML, email results). Note: the workflows include entire row content in alert row identifiers (JSON.stringify(row).slice(0,50)), so alert emails may contain portions of row data (possibly sensitive). Review which sheet columns are monitored and who receives REPORT_EMAIL.
- Install Mechanism
- okNo install spec or external downloads — instruction-only skill and three n8n workflow JSONs. Nothing is written or fetched at install time.
- Credentials
- okOnly two env vars are requested: REPORT_EMAIL (recipient) and ALERT_THRESHOLDS (threshold JSON). The workflows also require n8n credentials for Google Sheets and SMTP, which are reasonable. No unrelated secrets or system paths are requested.
- Persistence & Privilege
- okSkill is not always-enabled and does not request elevated platform privileges. It schedules recurring runs within n8n (the workflows are cron/schedule-based), which is expected behavior.
