AC agentmail
Use when an agent needs AgentMail CLI email inboxes.
AgentMail gives an agent its own email inbox for sending mail, receiving replies, completing email OTP flows, and running inbound email loops.
As a process C 59/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-requests-env-secretSKILL.md:1Skill asks the runtime to inject credential env vars into its sandbox: AGENTMAIL_API_KEY — verify each one is needed for the stated purposerequired_environment_variables: AGENTMAIL_API_KEY
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "prerequisites" - note
frontmatter-keyunknown frontmatter key "required_environment_variables"
Process rating: all ten parameters 59/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 608 tokens
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 52: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 8 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.