Name: amazon-ses
Rating: 55.2 (1 reviews)
Author: membranedev

amazon-ses

Amazon SES integration. Manage data, records, and automate workflows. Use when the user wants to interact with Amazon SES data.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/amazon-ses/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, mostly executable Membrane CLI integration guide with clear connection-state workflows and feedback loops. Its main weaknesses are a padded introductory paragraph explaining SES basics Claude already knows, an empty 'Popular actions' section, and broken step numbering ('Step 2' / '1b').

Suggestions

Delete or compress the opening marketing paragraph ('Amazon SES is a cloud-based email sending service designed to help...'); Claude already knows what SES is.

Fix the step numbering: label 'Step 1' and 'Step 2' explicitly (the '1b' / 'skip to Step 2' references currently point to nothing).

Populate 'Popular actions' with a few concrete SES action examples (e.g. sending email, verifying an identity) with real input, rather than only a discovery command.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Amazon SES is and who uses it ('cloud-based email sending service... used by businesses of all sizes') — concepts Claude already knows — plus filler like 'Use action names and parameters as needed', while the bulk is efficient commands; not a 4 because the padded intro is a noticeable over-explanation.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for the full flow (install, login, connection ensure, action list/run, request proxy) plus a flags table; not a 5 because placeholders like CONNECTION_ID/QUERY are never resolved with a concrete worked example and the 'Popular actions' section lists no actual SES actions.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state checkpoints and a feedback loop (poll -> CLIENT_ACTION_REQUIRED -> user acts -> poll again -> CONFIGURATION_ERROR check); not a 5 because it references 'Step 2' which is never labeled and the section numbering ('1b' with no '1a') is broken.	4 / 5
Progressive Disclosure	The body is organized into clear, navigable sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested-reference problem; not a 5 because all material — including the detailed connection state machine and proxy flag reference — is inlined in one 140-line file rather than split into a one-level-deep reference file.	4 / 5
	Total	15 / 20 Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit trigger clause and names a distinct AWS service, but its capability description is generic ('manage data, records, and automate workflows') rather than concrete SES actions, and it omits natural email-related trigger terms.

Suggestions

Replace generic verbs with concrete SES actions, e.g. 'Send transactional and marketing email, verify sender identities, manage templates and configuration sets.'

Add natural trigger terms users actually say: 'email', 'send email', 'transactional email', 'SES'.

Tighten the 'when' clause to reference email-sending intents, e.g. 'Use when the user wants to send or manage email via Amazon SES.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Amazon SES integration') but the actions 'Manage data, records, and automate workflows' are generic and not concrete SES-specific capabilities like sending email or verifying identities, matching the 'names the domain but actions are minimal or generic' anchor; not a 3 because no concrete SES action is enumerated.	2 / 5
Completeness	Both 'what' (Amazon SES integration, manage data/records/workflows) and 'when' ('Use when the user wants to interact with Amazon SES data') are present and explicit, satisfying the anchor for both present with the 'when' slightly generic; not a 5 because the 'what' is vague and the trigger phrases are not concrete.	4 / 5
Trigger Term Quality	It includes the natural product keyword 'Amazon SES' and an explicit trigger clause, but misses the most common user phrasings for an email service ('email', 'send email', 'transactional email'), so coverage is partial rather than comprehensive; not a 4 because several natural synonyms are absent.	3 / 5
Distinctiveness Conflict Risk	The explicit Amazon SES naming and SES-scoped trigger give it a clear, distinct niche with minimal conflict risk, but the generic verbs 'manage data, records, and automate workflows' create minor overlap risk with other data-integration skills; not a 5 because the generic action phrasing slightly blurs the niche.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/amazon-ses/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.