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

Blog Docs Log in Get started

getemails

GetEmails integration. Manage Emails, Contacts, Labels. Use when the user wants to interact with GetEmails data.

Quality

68%

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

Quality

Content

75%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 guide to driving GetEmails through the Membrane CLI, with a clear connection workflow that includes polling and state-based validation. The main gaps are generic placeholders in action examples and a couple of over-explanatory sentences that could be trimmed.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands and tables, with only minor over-explanation such as "Membrane handles authentication... so you can focus on the integration logic rather than auth plumbing", fitting the 4 anchor of efficient content with trims available.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection, action listing/running, and proxying, but action-invocation examples use generic placeholders (CONNECTION_ID, '{"key": "value"}') without a fully worked real-input example, placing it just below the 5 anchor.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit validation checkpoints and feedback loops (poll with --wait, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), matching the 4 anchor; it stops short of a full error-recovery checklist for 5.	4 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), giving good structure; without any one-level-deep references it sits at 4 rather than the 5 reserved for well-signaled cross-file navigation.	4 / 5
	Total	16 / 20 Passed

Description

62%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 anchors on a distinct named app, but its action vocabulary is generic ("Manage") and the trigger clause is broad rather than rich with natural synonyms. Strengthening the verbs and trigger terms would lift specificity and trigger-term quality.

Suggestions

Replace the generic verb "Manage" with concrete actions (e.g., "Find, verify, and look up email and contact records, organize labels") to raise specificity.

Expand the "Use when" clause with natural user phrasings and synonyms, e.g. "Use when the user wants to find, verify, or look up email addresses, manage contacts, or organize labels in GetEmails."

Add file-format or entity synonyms (e.g. .csv exports, lead lists) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("GetEmails integration") and three entities ("Manage Emails, Contacts, Labels"), but the single generic verb "Manage" does not enumerate multiple concrete actions, so it sits between naming the domain (3) and listing several specific actions (4).	3 / 5
Completeness	Both a clear "what" ("Manage Emails, Contacts, Labels") and an explicit "when" ("Use when the user wants to interact with GetEmails data") are present, but the trigger clause is generic rather than concrete phrases, matching the 4 anchor with room for a more specific "when".	4 / 5
Trigger Term Quality	Natural terms like "Emails", "Contacts", and "Labels" appear, but coverage lacks common synonyms and file extensions, fitting "some relevant keywords but missing common variations" rather than the comprehensive anchor at 5.	3 / 5
Distinctiveness Conflict Risk	Naming the specific app "GetEmails" carves a clear niche with minimal conflict risk, though "Manage Emails, Contacts, Labels" could still overlap with generic email skills, matching "mostly distinct; minor overlap risk".	4 / 5
	Total	14 / 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/getemails/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.