AC brevo
Brevo (formerly Sendinblue) email marketing API for managing contacts, lists, sending transactional emails, and campaigns. Use when importing contacts, sending emails, managing subscriptions, or working with email automation.
Brevo (formerly Sendinblue) email marketing API for managing contacts, lists, sending transactional emails, and campaigns.
As a process C 61/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
net-credential-useSKILL.md:260Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl "https://api.brevo.com/v3/contacts/lists/10" -H "api-key: $BREVO_KEY" | jq '.totalSubscribers'
vendor-host -
low Exfiltration
net-credential-useSKILL.md:263Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl "https://api.brevo.com/v3/contacts?limit=10&sort=desc" -H "api-key: $BREVO_KEY"
vendor-host -
low Exfiltration
net-credential-useSKILL.md:266Credential used in a network call (verify the destination is the intended service) (security demo / example; the skill's own vendor host)curl "https://api.brevo.com/v3/contacts/us…@….com" -H "api-key: $BREVO_KEY"
demovendor-host -
low Exfiltration
net-credential-useSKILL.md:269Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)curl "https://api.brevo.com/v3/account" -H "api-key: $BREVO_KEY"
vendor-host
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 15 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1659 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
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 225: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 10 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.