AD Google Workspace
Manage Google Calendar, Google Drive, and Google Sheets through MyBrandMetrics-connected Google data sources and the local Google Workspace CLI. Use it to list, create, update, and delete Calendar events; read, append, update, and batch update Google Sheets; and search, create, move, copy, share, upload, export, and delete Google Drive files and folders. No Google Cloud project setup and no MCP server are required: sign in to MyBrandMetrics with Google, connect the needed Google data sources, get a MyBrandMetrics API key, and start using the skill.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens)
Process rating: all ten parameters 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Consistency. Frontmatter name (Google Workspace) differs from the folder (clawbus-google-workspace)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 100Steps. 20 steps
- 100Execution cost. Instruction body is 1374 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 554: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 20 items
- +4Has examples (13 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.