SKILLEMALL.ai
GitHub ↗ RU Sign in

CC google-loops

Set up and operate the Gmail/Calendar/Contacts connector and the open-loop engine: who is waiting on the user, what they promised, and the context needed to respond. Covers painless BYO OAuth setup (exactly two user interactions), the daily `gbrain waiting` digest, loop closing/muting, and troubleshooting via the typed error catalog.

garrytan/gbrain Agent Skills author: garrytan MIT 1 file body ≈ 2 262 tokens Open the sourcegithub.com↗ analyzed 4 d ago

Set up and operate the Gmail/Calendar/Contacts connector and the open-loop engine: who is waiting on the user, what they promised, and the context needed to…

As a process C 57/100 · Has gaps — References files that are not bundled: ../conventions/agent-operator-protocol.md

IntegrationGmailPersonal productivitySoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
57/100
Has gaps
References files that are not bundled: ../conventions/agent-operator-protocol.md
Tools and files w 18
0
Inputs and preconditions w 11
0
Failures and branches w 10
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: google-loops (garrytan/gbrain)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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: 1. 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")
  • warning missing-ref reference to a missing file: ../conventions/agent-operator-protocol.md
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "tools"
  • note frontmatter-key unknown frontmatter key "mutating"
  • note frontmatter-key unknown frontmatter key "writes_pages"
  • note edit-residue the text marks something as outdated (lines 152): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 57/100

Will not run. References files that are not bundled: ../conventions/agent-operator-protocol.md
  • 0Tools and files. 1 referenced file(s) missing: ../conventions/agent-operator-protocol.md
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 50Failures and branches. 0 branches, has a failure section
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2262 tokens
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress

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)
  • +1No license
  • +2Single-language instructions
  • +3Description length 335: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 23 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)

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