Name: easysendy
Rating: 62.4 (1 reviews)
Author: membranedev

easysendy

EasySendy integration. Manage Users, Organizations, Goals, Filters. Use when the user wants to interact with EasySendy data.

Quality

73%

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/easysendy/SKILL.md

Quality

Content

76%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 body is highly actionable with copy-paste commands and a clear connection workflow, but it lacks validation/verification steps for the destructive and batch operations it prominently features, and carries minor marketing fluff. Splitting reference material into a bundled file would improve progressive disclosure.

Suggestions

Add a validation/verification step before destructive and batch actions — e.g. 'Before delete-subscriber or delete-list, confirm the target ID with the user; after add-multiple-subscribers, run get-subscriber-status to verify a sample was added.'

Remove the marketing filler in the opening paragraph ('focuses on affordability and ease of use, especially for users in developing markets') since it does not aid execution.

Move the popular-actions table and proxy flag reference into a bundled references/ file linked from SKILL.md to keep the overview lean and one level deep.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, tables, and flag references; the only padding is the opening marketing paragraph ('focuses on affordability and ease of use, especially for users in developing markets') which could be trimmed, fitting 'efficient; minor instances of over-explanation'.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for every stage (install, login, connection ensure/get, action list, action run with --input JSON, request proxy) plus a flags table and a popular-actions table — covering the common cases completely.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but the skill features destructive and batch actions (Delete Subscriber, Delete List, Add Multiple Subscribers) with no validation or verification guidance before running them, capping workflow clarity at 3 per the destructive/batch rule.	3 / 5
Progressive Disclosure	Single well-organized file with clear sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices) and no nested references; not a 5 because at ~180 lines some content (e.g. the full action catalog / proxy reference) could be split into a one-level reference file.	4 / 5
	Total	16 / 20 Passed

Description

71%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 answers both what and when and is clearly niche-specific to EasySendy, but its trigger vocabulary is thin and the 'when' clause is generic. Naming the actual EasySendy concepts (campaigns, subscribers, lists) would materially improve it.

Suggestions

Expand the trigger phrase to name concrete EasySendy concepts users actually say, e.g. 'Use when the user wants to manage EasySendy email campaigns, subscribers, lists, or sequences.'

Replace the single generic verb 'Manage' with distinct concrete actions (e.g. 'Create and send email campaigns, manage subscribers and lists, view reports').

Align the description's entity list (Users, Organizations, Goals, Filters) with the skill body's actual domain (campaigns, lists, subscribers, sequences) to avoid misleading triggers.

Dimension	Reasoning	Score
Specificity	Lists several specific actions via 'Manage Users, Organizations, Goals, Filters' — four named entity areas, matching the 'several specific actions' anchor; not a 5 because all share one generic verb ('Manage') rather than distinct concrete verbs.	4 / 5
Completeness	Has both a 'what' ('EasySendy integration. Manage Users, Organizations, Goals, Filters.') and a 'when' ('Use when the user wants to interact with EasySendy data.'), but the 'when' is generic and could name concrete triggers, so it is not a 5.	4 / 5
Trigger Term Quality	The only natural trigger term is 'EasySendy' / 'EasySendy data'; common variations users would say (email campaigns, subscribers, lists) are absent, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tied to a specific named product ('EasySendy') with a distinct trigger ('interact with EasySendy data'), giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 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/easysendy/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.