AB email-writer-assistant
A professional email writing assistant. Based on the user's email purpose and content points, writes clear, concise, and polite emails covering subject, body, and attachment notes, adapted to different audiences and scenarios.
A professional email writing assistant.
As a process B 73/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 73/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 55Failures and branches. 1 branches
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 550 tokens
- 100Running it twice. No mutating operations
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 226: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.
External checks
ClawHub: clean
This is a simple email-writing skill that provides formatting and tone guidance without requesting access to files, credentials, tools, or external services.
LLM: benign (high) · VirusTotal: · 12 Jun 2026