SKILLEMALL.ai
RU Sign in

BB howtoletmyagent_secure_gmail_access

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

ClawHub Agent Skills author: Bullkis1 v0.1.0 MIT-0 2 files body ≈ 410 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process B 66/100 · Nearly there — weak spots: result and completion, consistency, running it twice

IntegrationGmailAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
B
66/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 66/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (howtoletmyagent_secure_gmail_access) differs from the folder (howtoletmyagent-secure-gmail-access)
  • 60Failures and branches. 2 branches
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 20 steps
  • 100Execution cost. Instruction body is 410 tokens

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 113: 120–800 characters recommended
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Step-by-step instructions: 20 items

Quality base 70; lint remarks subtract, signals add up to 100. Result: 56.

External checks

ClawHub: clean
This is a markdown-only companion skill that openly guides Gmail OAuth setup and warns users to approve sensitive account changes carefully.
LLM: benign (medium) · VirusTotal: · 29 May 2026