Name: flexmail
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

flexmail

Flexmail integration. Manage Contacts, Campaigns, Templates. Use when the user wants to interact with Flexmail data.

Quality

69%

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

Quality

Content

65%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 concrete commands and a clear connection workflow, but it is padded with marketing prose and a noisy action table, lacks verification steps around destructive actions, and is a monolithic single file with no external references.

Suggestions

Add a validation/verification checkpoint before destructive actions (e.g. list-then-confirm before delete-webhook or unsubscribe-contact) to lift the workflow clarity cap.

Move the 'Popular actions' catalog and proxy flag reference into a separate references file and link to it from SKILL.md, improving progressive disclosure.

Trim the introductory marketing paragraph and 'auth plumbing' commentary, and replace 'No description' rows with real one-line descriptions or remove them.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but the opening marketing paragraph about what Flexmail is, the 'rather than auth plumbing' commentary, and a 20-row 'Popular actions' table repeating 'No description' add unnecessary padding.	3 / 5
Actionability	Concrete, copy-paste-ready commands cover the full common workflow (login, connection ensure, action list/run, request/proxy) plus a complete proxy-flags table, matching the 'fully executable, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checkpoints and polling, but the skill exposes destructive actions (delete-webhook, unsubscribe-contact) and the 'Running actions' section has no validation/verification step, so the destructive-operations cap applies.	3 / 5
Progressive Disclosure	No bundle files exist and the document is a single 165-line file; although it has clear section headers, the 20-row action catalog is reference content inlined that would be better separated, matching the 'content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

73%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 names the target product and core entities and includes an explicit 'Use when' trigger, but the action verb is generic and trigger coverage lacks common synonyms. It is distinct and clearly scoped to Flexmail.

Suggestions

Replace the generic verb 'Manage' with concrete actions, e.g. 'Create, update, and list contacts, campaigns, and templates'.

Expand the 'Use when' clause with concrete triggers, e.g. 'Use when the user mentions Flexmail contacts, email campaigns, newsletters, or subscriber lists'.

Add commonly used synonyms (email marketing, newsletters, subscribers) so the description matches natural user phrasing.

Dimension	Reasoning	Score
Specificity	Names three concrete domain objects ("Contacts, Campaigns, Templates") but relies on a single generic verb ("Manage") rather than enumerating distinct concrete actions, matching the 'names domain + 1-2 actions' anchor and falling short of the multiple-specific-actions anchor.	3 / 5
Completeness	It states both the what ("Manage Contacts, Campaigns, Templates") and an explicit when ("Use when the user wants to interact with Flexmail data"), but the trigger is a single generic clause rather than varied concrete trigger phrases, so it sits at anchor 4 rather than 5.	4 / 5
Trigger Term Quality	"Contacts, Campaigns, Templates, Flexmail" are natural terms users would say, but common synonyms such as email marketing, newsletters, subscribers, or lists are missing, fitting the 'good keyword coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	"Flexmail" is a specific named SaaS product, giving the skill a clear niche with distinct triggers and minimal risk of firing for unrelated skills, matching the top anchor.	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/flexmail/SKILL.md
Commit: f484c82

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