← Back to Skills Marketplace
132
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install howtoletmyagent-secure-gmail-access
Description
Teach an OpenClaw agent the recommended Gmail OAuth2 setup, scope choices, and safety guardrails from this guide.
README (SKILL.md)
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:
- Category: Gmail & Email
- Source article: https://howtoletmyagent.xyz/articles/how-to-let-my-openclaw-agent-get-secure-gmail-access
- Risk level: medium
- Tags: Gmail, OAuth2, Security, ClawHub, Google Workspace
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.
Usage Guidance
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.
Capability Analysis
Type: OpenClaw Skill
Name: howtoletmyagent-secure-gmail-access
Version: 0.1.0
The skill bundle contains only metadata and instructions (SKILL.md) designed to guide an AI agent through a Gmail OAuth2 setup process based on an external article (howtoletmyagent.xyz). It contains no executable code, and the instructions explicitly prioritize safety guardrails, risk disclosure, and user approval before making changes, with no evidence of malicious intent or data exfiltration.
Capability Assessment
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.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install howtoletmyagent-secure-gmail-access - After installation, invoke the skill by name or use
/howtoletmyagent-secure-gmail-access - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial companion skill release for secure Gmail access article
Metadata
Frequently Asked Questions
What is Howtoletmyagent Secure Gmail Access?
Teach an OpenClaw agent the recommended Gmail OAuth2 setup, scope choices, and safety guardrails from this guide. It is an AI Agent Skill for Claude Code / OpenClaw, with 132 downloads so far.
How do I install Howtoletmyagent Secure Gmail Access?
Run "/install howtoletmyagent-secure-gmail-access" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Howtoletmyagent Secure Gmail Access free?
Yes, Howtoletmyagent Secure Gmail Access is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Howtoletmyagent Secure Gmail Access support?
Howtoletmyagent Secure Gmail Access is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Howtoletmyagent Secure Gmail Access?
It is built and maintained by Bullkis1 (@bullkis1); the current version is v0.1.0.
More Skills