BC gws-shared
gws CLI: Shared patterns for authentication, global flags, and output formatting.
gws CLI: Shared patterns for authentication, global flags, and output formatting.
As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
IntegrationData and analyticsSoftware developmenttype and topics are labelled automatically from the skill text
This is a copy of a skill from another catalog; the rating counts the canonical one: gws-shared (ClawHub)
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 609 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 81: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.
External checks
ClawHub: clean
This skill is a small reference guide for using the gws Google Workspace CLI and its sensitive behaviors are disclosed and purpose-aligned.
LLM: benign (high) · VirusTotal: · 2 Aug 2026