AC zoho
Interact with Zoho CRM, Projects, and Meeting APIs. Use when managing deals, contacts, leads, tasks, projects, milestones, meeting recordings, or any Zoho workspace data. Triggers on mentions of Zoho, CRM, deals, pipeline, projects, tasks, milestones, meetings, recordings, standups.
Interact with Zoho CRM, Projects, and Meeting APIs.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Exfiltration
exfil-secret-in-urlscripts/standup-summarizer.sh:157Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"https://generativelanguage.googleapis.com/upload/v1beta/files?key=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlscripts/standup-summarizer.sh:203Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"https://generativelanguage.googleapis.com/v1beta/models/gemi…ent?key=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlscripts/standup-summarizer.sh:217Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"https://generativelanguage.googleapis.com/v1beta/models/gemi…ent?key=…" \
placeholder
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "repository"
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 85Steps. 32 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2644 tokens
- 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)
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 283: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.