Name: emailoctopus
Rating: 58.4 (1 reviews)
Author: membranedev

emailoctopus

Emailoctopus integration. Manage Lists, Campaigns, Templates. Use when the user wants to interact with Emailoctopus data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/emailoctopus/SKILL.md

Quality

Content

68%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 skill is highly actionable with executable commands and a clear connection workflow, but it lacks validation checkpoints before destructive/batch operations and carries some trimmable prose plus a large inline reference table.

Suggestions

Add an explicit verification step before destructive actions, e.g. 'Before delete-contact/delete-list, run get-contact/get-list to confirm the target, then confirm with the user before re-running with the delete action'.

Move the 'Popular actions' table into a bundled references file (e.g. references/actions.md) and link to it from SKILL.md to keep the overview lean.

Trim background prose (the Amazon SES intro, 'This is the fastest way to get a connection') to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational and command-driven, but includes some unnecessary prose such as the opening background on Amazon SES and phrases like 'This is the fastest way to get a connection' that could be trimmed without losing clarity.	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every stage (install, login, connection ensure/get, action list/run, request proxy) plus a flag table and a parameter-passing example, covering the common cases concretely.	5 / 5
Workflow Clarity	The connection workflow is well sequenced with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling, but the skill exposes destructive and batch operations (delete-contact, delete-list, list-all) with no verification step before running them, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references, but the large inline 'Popular actions' reference table could live in a separate bundled file rather than the main SKILL.md, leaving a minor organization gap.	4 / 5
	Total	15 / 20 Passed

Description

66%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 cleanly identifies a specific niche and includes both a 'what' and a 'when' clause, but the action verb is generic ('Manage') and the trigger phrasing is broad rather than listing concrete user-facing triggers.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create and update Lists, send and report on Campaigns, and manage Templates and Contacts'.

Sharpen the 'Use when...' trigger with natural user phrases, e.g. 'Use when the user wants to send email campaigns, manage subscriber lists, or check campaign reports in EmailOctopus'.

Dimension	Reasoning	Score
Specificity	It names the domain (Emailoctopus) and three concrete resource types ("Lists, Campaigns, Templates"), but the only action verb is the generic "Manage", so coverage of actual actions is minimal rather than comprehensive.	3 / 5
Completeness	It states both what ("Manage Lists, Campaigns, Templates") and when ("Use when the user wants to interact with Emailoctopus data"), but the 'when' clause is somewhat generic and could be more explicit, matching the 4 anchor rather than the fully concrete 5 anchor.	4 / 5
Trigger Term Quality	It includes relevant domain keywords ("Emailoctopus", "Lists", "Campaigns", "Templates") but the trigger phrase "interact with Emailoctopus data" is generic and misses common natural variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	"Emailoctopus integration" names a specific external product, giving it a clear niche with distinct triggers and minimal risk of conflicting with other skills.	5 / 5
	Total	15 / 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/emailoctopus/SKILL.md
Commit: f484c82

Reviewed: 4 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.