AF mermail-cli
Install and use the official Mermail CLI for deterministic shell automation across workspaces, mailboxes, email, folders, labels, agents, task triage, and Agent Wallet via MCP OAuth. Use when a user asks for terminal commands, scripts, CI automation, or stable JSON output. Prefer direct Mermail MCP skills when no shell composition is needed.
Install and use the official Mermail CLI for deterministic shell automation across workspaces, mailboxes, email, folders, labels, agents, task triage, and…
As a process F 55/100 · Will not run — References files that are not bundled: references/tools.md, references/workflows.md, references/security.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/tools.md - warning
missing-refreference to a missing file: references/workflows.md - warning
missing-refreference to a missing file: references/security.md
Process rating: all ten parameters 55/100
- 0Tools and files. 3 referenced file(s) missing: references/tools.md, references/workflows.md, references/security.md
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1650 tokens
- 100Progress reporting. Reports progress
- 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 343: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 38 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.