SKILLEMALL.ai
GitHub ↗ RU Sign in

BB google-workspace

Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.

NousResearch/hermes-agent Hermes author: NousResearch MIT 7 files body ≈ 3 307 tokens Open the sourcegithub.com↗ analyzed 8 h ago

Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python.

As a process B 67/100 · Nearly there — weak spots: inputs and preconditions

IntegrationGmailGoogle CloudSoftware developmentData and analyticsPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Hermes Agent
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
71
Run on models
none yet
Process rating
B
67/100
Nearly there
Inputs and preconditions w 11
0
Tools and files w 18
60
Result and completion w 14
60
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: 7. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "required_credential_files"
  • note edit-residue the text marks something as outdated (lines 261): check that old rules are not kept next to new ones — the full check reads the text for contradictions

Process rating: all ten parameters 67/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Result and completion. Output format stated, no completion criterion
  • 60Consistency. The Hermes dialect needs category and tags
  • 70When it triggers. States when to use, but not when not to
  • 85Steps. 40 steps, 1 vague phrases
  • 100Failures and branches. 4 branches, has a failure section
  • 100Execution cost. Instruction body is 3307 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)
  • +3Description length 59: 120–800 characters recommended
  • -2localhost URLs: will not work for another user
  • -32 of 4 scripts are never mentioned in SKILL.md
  • +2Single-language instructions
  • +4Structure: 22 headings
  • +3Step-by-step instructions: 40 items
  • +3Output format is stated explicitly
  • +4Has examples (14 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +1License stated

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