AC email-ops
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC. Use when the user wants to organize email, draft or send through the real mail surface, or prove what landed in Sent.
Promises mailbox triage, draft composition, delivery verification, and safe follow-up for multiple platforms. Single file, 1028 tokens, no broken links or critical issues. Quality scores 87/100, but process efficiency sits at 58—there's friction in the workflow. No model runs or sandbox testing.
Works as a template across Claude, Cursor, and a dozen other agents. Won't give you a plug-and-play mail handler. Will give you a framework to build on. Install if you're ready to adapt; skip if you need something that runs out of the box.
Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, failures and branches, 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 · 0
✓ No critical or high findings
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 58/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
- 30Running it twice. 18 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 47 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1028 tokens
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 224: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 47 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.