ClawHub

Howtoletmyagent Secure Gmail Access

v0.1.0

Teach an OpenClaw agent the recommended Gmail OAuth2 setup, scope choices, and safety guardrails from this guide.

⭐ 0· 128·0 current·0 all-time
by@bullkis1

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bullkis1/howtoletmyagent-secure-gmail-access.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Howtoletmyagent Secure Gmail Access" (bullkis1/howtoletmyagent-secure-gmail-access) from ClawHub.
Skill page: https://clawhub.ai/bullkis1/howtoletmyagent-secure-gmail-access
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install howtoletmyagent-secure-gmail-access

ClawHub CLI

Package manager switcher

npx clawhub@latest install howtoletmyagent-secure-gmail-access
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the SKILL.md: the skill is a companion guide that references a specific article and explains Gmail OAuth2 setup, scope choices, and guardrails. It does not request unrelated binaries, config paths, or credentials.
ℹ
Instruction Scope
The instructions are aligned to the referenced article and correctly emphasize calling out risks and approvals. However the guidance includes open-ended phrases like "inspect first and adapt carefully" and "perform the workflow end-to-end if the user asks," which give the agent broad discretion. The SKILL.md does not explicitly instruct reading local files or exfiltrating secrets, but the vagueness could lead the agent to ask for or attempt to use sensitive credentials if the user requests full automation.
✓
Install Mechanism
No install spec and no code files — instruction-only. This is the lowest-risk install model and consistent with a documentation/guide skill.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. That is proportionate for a guidance-only skill. Note: performing real OAuth operations would require client credentials in practice, but the skill itself does not request them.
✓
Persistence & Privilege
always:false and user-invocable:true (default) — appropriate for a teaching/guide skill. The skill does not request permanent presence or modify other skills or system-wide agent settings.
Assessment
This skill is a text-only guide on how to set up Gmail OAuth2 and is coherent with that purpose. Before installing or asking the agent to perform changes: (1) verify the source article yourself; (2) do not paste client_secret, private keys, or admin credentials into chat — instead follow step-by-step instructions locally or provide the agent with only the minimum, short-lived tokens if absolutely necessary; (3) prefer least-privilege OAuth scopes and internal/verified consent where possible; (4) if you want the agent to perform actions in your cloud/GCP project, expect it to request credentials — consider doing those steps yourself or creating a scoped, revocable credential for the task; (5) audit and rotate any credentials created. If you want a stricter assessment, provide the referenced article or examples of prompts where the agent would be asked to act autonomously so I can check for additional risky guidance.

Like a lobster shell, security has layers — review code before you run it.

latestvk978b304mnts04tx0zny2a9jp583gzhs
128downloads
0stars
1versions
Updated 1mo ago
v0.1.0
MIT-0
@bullkis1
latest
Download

How to let my OpenClaw agent get secure Gmail access (2026) Companion Skill

Use this skill when the user wants help with the workflow covered by this article:

Primary behavior:

  • Treat the article above as the canonical source for this workflow.
  • Follow the recommended approach from the article instead of inventing alternate setups.
  • Call out risk, credentials, destructive actions, and approval points before making changes.
  • If the user's environment differs from the article, inspect first and adapt carefully.

When this skill should trigger:

  • The user asks for this exact workflow.
  • The user references this article or asks to "use the Howtoletmyagent method".
  • The user needs a safe, article-aligned setup rather than a generic answer.

Suggested quick prompt:

  • "Use the Howtoletmyagent secure Gmail access skill when I ask you to set up Gmail for OpenClaw."

Important sections in the source article:

  • Prerequisites
  • Which Gmail access method should you use?
  • The best and safest method for most users
  • Step 1: Decide how much inbox power you actually want to give
  • Step 2: Create a Google Cloud project
  • Step 3: Enable the Gmail API
  • Step 4: Configure the OAuth consent screen
  • Step 5: Add scopes carefully

If the user asks you to perform the workflow end-to-end, use the source article as the baseline procedure and keep the user informed about any deviations or missing prerequisites.

Comments

Loading comments...