CC aws-ses
Amazon SES playbook. Scripts: check account/sandbox status, create a domain identity and print DKIM/SPF records, verify DNS, derive an SMTP password locally, send a test email, report bounce/complaint stats. Production-access requests and Sendy setup are written guidance only — no script automates them.
Amazon SES playbook. Scripts: check account/sandbox status, create a domain identity and print DKIM/SPF records, verify DNS, derive an SMTP password locally…
As a process C 58/100 · Has gaps — weak spots: when it triggers, consistency, execution cost
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 304 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
body-longSKILL.md body ≈ 10419 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "author_x" - note
frontmatter-keyunknown frontmatter key "dependencies" - note
edit-residuethe text marks something as outdated (lines 438): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 58/100
- 0Consistency. Frontmatter name (aws-ses) differs from the folder (aws-ses-skill)
- 20When it triggers. No condition that starts the skill
- 40Execution cost. Instruction body is 10419 tokens: crowds the task out of the window
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 122 steps
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 17 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (5 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)
- +2Single-language instructions
- +3Description length 304: enough signal without eating the budget
- +4Structure: 65 headings
- +3Step-by-step instructions: 122 items
- +3Output format is stated explicitly
- +4Has examples (36 code blocks)
- +3All 6 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.