Name: quickmailio
Rating: 64.8 (1 reviews)
Author: membranedev

quickmailio

QuickMail.io integration. Manage Users, Organizations, Files, Notes, Activities. Use when the user wants to interact with QuickMail.io data.

Quality

77%

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

Quality

Content

83%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 executable Membrane CLI commands and a clear connect-to-run workflow including a polling feedback loop. It is slightly padded by an introductory platform description and a duplicated action-discovery section.

Suggestions

Trim the opening overview paragraph that explains what QuickMail.io is and its audience; Claude can infer this and it consumes tokens.

Consolidate the duplicated action-discovery instructions ('Searching for actions' vs 'Popular actions') into one section to remove redundancy.

Add an explicit validation/retry checkpoint after 'membrane action run' for batch or destructive operations (e.g. verify the output field before proceeding).

Dimension	Reasoning	Score
Conciseness	Largely efficient with copy-paste commands and tables, but the opening overview paragraph explaining what QuickMail.io is and who uses it pads slightly with context Claude could infer, fitting the 'efficient; minor over-explanation to trim' anchor.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection, polling, action search/run, and proxy requests, covering common cases with concrete flags and examples.	5 / 5
Workflow Clarity	A clear sequence from install through connect to running actions, with an explicit state-polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED) for the connection step; minor gaps include a slightly redundant 'Popular actions' section repeating the search command.	4 / 5
Progressive Disclosure	No bundle files exist, so content is a single well-sectioned SKILL.md with clear headings (Overview, Working with..., Best practices); structure is good and easy to navigate, with only minor organization redundancy.	4 / 5
	Total	17 / 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 clearly names the QuickMail.io niche and provides an explicit 'Use when' trigger alongside concrete managed entities, scoring well on completeness and distinctiveness. Its main weakness is generic 'Manage' verbs and limited trigger-term variation.

Suggestions

Replace the generic 'Manage' with distinct concrete verbs (e.g., 'Create, list, update, and delete Users, Organizations, Files, Notes, and Activities') to raise specificity.

Add natural trigger synonyms such as 'QuickMail contacts', 'outreach campaigns', or 'prospects' so users' varied phrasings match the skill.

Tighten the 'when' clause with concrete scenarios, e.g. 'Use when the user wants to query or update QuickMail.io users, organizations, or activities.'

Dimension	Reasoning	Score
Specificity	Names the domain plus five concrete managed entities ('Users, Organizations, Files, Notes, Activities'), though 'Manage' is a generic verb rather than several distinct actions, fitting just below the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ('Manage Users, Organizations, Files, Notes, Activities') and when ('Use when the user wants to interact with QuickMail.io data'), but the trigger could be more specific to edge cases, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	Includes the natural phrase 'Use when the user wants to interact with QuickMail.io data' but offers few synonyms or variations beyond the product name, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	A named niche product with a specific entity list gives clear triggers and minimal overlap risk with 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/quickmailio/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.