Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Google Suite Skill
v1.0.0Provides unified access to Gmail, Google Calendar, and Drive APIs for managing emails, calendar events, and files with OAuth2 authentication.
⭐ 0· 424·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's declared registry metadata lists no required environment variables or primary credential, yet SKILL.md and the code require OAuth credentials (GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, GOOGLE_OAUTH_REDIRECT_URI). The top-level registry also described the package as instruction-only, but the bundle contains Python code and requirements — these metadata mismatches are incoherent and worth flagging. The requested credentials themselves are appropriate for a Google Suite integration, but the metadata omission is suspicious and reduces trust (source/homepage unknown).
Instruction Scope
SKILL.md instructions and the code stay within the stated scope (Gmail/Calendar/Drive operations) and describe an OAuth flow (local server + user consent). However SKILL.md asserts 'tokens are stored securely and never logged' while the implementation writes tokens to a plain JSON file (google_suite_tokens.json) in the skill folder — not encrypted. That storage behavior should be considered when trusting the skill.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the bundle includes requirements.txt and explicit pip install instructions in SKILL.md for google-api-python-client and related libs. This is expected for a Python skill, but the absence of a declared install mechanism in the metadata is inconsistent with the provided code and requirements.
Credentials
The environment variables the skill uses (OAuth client ID, client secret, redirect URI) are appropriate and proportionate to its functionality. The scopes requested are broad (read/send/modify Gmail, calendar, full Drive) but justified by the feature set. Note: these are sensitive values; the skill stores resulting tokens as a local JSON file which should be protected (file permissions, isolated environment).
Persistence & Privilege
The skill persists OAuth tokens to google_suite_tokens.json in the skill directory so it can reuse credentials across runs. always:false and no cross-skill configuration changes are present, so privilege level is reasonable. Still, token persistence to disk is a lasting capability — ensure the file's location and permissions are acceptable for your security posture.
What to consider before installing
This skill appears to implement the advertised Gmail/Calendar/Drive features, but there are a few red flags you should consider before installing:
- Metadata mismatch: The registry claims no required env vars and no install steps, but SKILL.md and the code require GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, and GOOGLE_OAUTH_REDIRECT_URI and instruct you to pip install Google API libs. Treat the missing metadata as a packaging/quality issue and ask the publisher for clarification.
- Sensitive credentials: You must provide an OAuth client ID and secret. Only supply these if you trust the publisher. The skill will launch a local OAuth flow and store tokens in google_suite_tokens.json in the skill folder (plain JSON). Ensure that file is stored in a secure/isolated environment and that file permissions prevent unauthorized access.
- Broad scopes: The scopes include full Drive and Gmail modify/send access. If you only need read-only actions, consider narrowing scopes or using a different, less-privileged skill.
- Source provenance: The skill has no homepage and an unknown source owner — prefer skills with a verifiable homepage or known publisher. If you plan to use it, review the included Python files yourself (they are present and readable) and consider running the skill in an isolated environment (VM/container) until you are comfortable.
- Practical steps: (1) Verify the code matches SKILL.md (it does, but check token path and any changes), (2) run in an isolated account/VM, (3) set restrictive file permissions on google_suite_tokens.json, and (4) ask the publisher to fix metadata and provide a source/homepage for accountability.
If you want, I can produce a checklist of exact commands to inspect the files, run the skill in a container, or help you narrow OAuth scopes for safer use.Like a lobster shell, security has layers — review code before you run it.
apivk97drb2src39qcz0735r8fqryn81rqg0automationvk97drb2src39qcz0735r8fqryn81rqg0calendarvk97drb2src39qcz0735r8fqryn81rqg0drivevk97drb2src39qcz0735r8fqryn81rqg0gmailvk97drb2src39qcz0735r8fqryn81rqg0googlevk97drb2src39qcz0735r8fqryn81rqg0latestvk97drb2src39qcz0735r8fqryn81rqg0productivityvk97drb2src39qcz0735r8fqryn81rqg0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.