AB webmail-email-monitor
Monitor Outlook and other common webmail inboxes in a persistent Edge profile, process new messages as a detached local background task, capture complete message screenshots, download attachments to the desktop, and write structured Excel rows with deterministic Python logic. Use when Codex needs to start, stop, verify, or modify a Windows email monitoring workflow.
As a process B 73/100 · Nearly there — weak spots: consistency
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:22Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- Start the monitor with `powershell -ExecutionPolicy Bypass -File scripts/webm…ps1 start`
quoted -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:26Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- Check `powershell -ExecutionPolicy Bypass -File scripts/webm…ps1 status`
quoted -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:27Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)or `powershell -ExecutionPolicy Bypass -File scripts/webm…ps1 logs`
quoted -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:54Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)1. Run `powershell -ExecutionPolicy Bypass -File scripts/webm…ps1 start`
quoted -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:55Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)2. Run `powershell -ExecutionPolicy Bypass -File scripts/webm…ps1 status`
quoted
Files scanned: 2. 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 73/100
- 40Consistency. Frontmatter name (webmail-email-monitor) differs from the folder (webmail-email-monitor-skill)
- 60Tools and files. Uses tools (bash, python) 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
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 79 steps, 2 vague phrases
- 100Failures and branches. 7 branches, has a failure section
- 100Execution cost. Instruction body is 2405 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 13 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 368: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 79 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.