AD agentmail-to-inbox-ops
Manage Agentmail.to inbox operations with deterministic Python scripts: list/read messages, download and analyze attachments, reply with sender filters, and set read/unread state. Use when handling inbox workflows for any Agentmail.to inbox.
As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
-
low Exfiltration
read-dotenvREADME.md:24Reads a .env filecp .env.example .env
Files scanned: 14. 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 45/100
- 0Result and completion. Does not say what the result is
- 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. 11 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 43 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 949 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (14 tags): a typed call is more reliable
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)
- +4Structure: 0 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -31 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 241: enough signal without eating the budget
- +3Step-by-step instructions: 43 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.