SKILLEMALL.ai
GitHub ↗ RU Sign in

BD google-workspace

Google Workspace automation — Gmail, Calendar, Drive, and Sheets via service account or OAuth. Read, write, send, and manage your entire Google stack.

ClawHub Agent Skills author: fr3kstyle v1.0.0 MIT-0 3 files body ≈ 1 086 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

IntegrationGmailPersonal productivityInfrastructuretype 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
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
75
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Secrets in code secret-private-key SKILL.md:13
    Private key material (placeholder value)
    export GOOGLE_SERVICE_ACCOUNT_JSON='{"type":"service_account","project_id":"...","private_key_id":"...","private_key":"-----BEGIN PRIVATE KEY----- …
    placeholder

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 43/100

  • 0Result and completion. Does not say what the result is
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 4 mutating operations with no state check
  • 40Consistency. Frontmatter name (google-workspace) differs from the folder (fr3k-google-workspace)
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 75Steps. 3 steps
  • 100Execution cost. Instruction body is 1086 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)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 150: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 3 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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

External checks

ClawHub: suspicious
This skill appears to automate Google Workspace as advertised, but it grants broad access to email, Drive, Calendar, and Sheets with limited safety guardrails.
LLM: suspicious (high) · VirusTotal: · 29 May 2026