Name: emelia
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

emelia

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

Quality

61%

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

Quality

Content

61%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 highly actionable with concrete Membrane CLI commands and a well-structured connection workflow including state checkpoints. Its weaknesses are a marketing-fluff intro, missing validation for destructive campaign operations, and the absence of any reference-file split for the action/flag tables.

Suggestions

Cut the marketing intro ("Marketers and small business owners use it to engage with their audience...") and other padded phrasing; keep only the one-line statement of what Emelia is.

Add an explicit validation/confirmation checkpoint before destructive or batch campaign actions (e.g., verify the campaign/contact with a get-* action before remove/pause, and confirm the result from the `output` field).

Provide one fully worked end-to-end example (e.g., search for an action, run it with a realistic `--input` value, and read the `output` field) so the run flow is copy-paste complete.

Dimension	Reasoning	Score
Conciseness	The body is dominated by tight, operational CLI content, but it opens with unnecessary marketing fluff ("Marketers and small business owners use it to engage with their audience and promote their products or services") and a few padded phrases ("so you can focus on the integration logic rather than auth plumbing") that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a popular-actions table and proxy flag table, but examples rely on placeholders (CONNECTION_ID, <actionId>) and an abstract JSON input ("key": "value") with no fully worked end-to-end example.	4 / 5
Workflow Clarity	The connection-setup flow has good state-based checkpoints and a re-poll feedback loop (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but destructive and batch campaign operations ("Remove Contact from Email Campaign", "Pause/Start Email Campaign") have no validation or verification steps, which caps this dimension at 3.	3 / 5
Progressive Disclosure	The single-file body is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Popular actions, Running actions, Proxy) with an external docs link, though all reference material is inlined since no bundle/reference files are provided.	4 / 5
	Total	14 / 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 successfully states both what the skill does and when to use it, anchored by the distinct "Emelia" brand name. Its main weakness is relying on one generic verb ("Manage") and a broad trigger phrase rather than concrete actions and specific trigger terms.

Suggestions

Replace the single generic verb "Manage" with distinct concrete actions per entity (e.g., "Create and pause email campaigns, add or remove contacts, fetch the current user").

Tighten the "Use when" clause with concrete trigger phrases users would actually say (e.g., "Use when the user wants to send or pause an Emelia email campaign, manage contacts, or query Emelia data").

Add a couple of natural synonyms/variants (e.g., "email campaigns", "contacts", "Emelia API") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("Emelia integration") and lists concrete entities ("Organizations, Users, Goals, Filters"), but relies on a single generic verb ("Manage") rather than distinct concrete actions, so coverage is not comprehensive.	3 / 5
Completeness	Both a clear "what" ("Manage Organizations, Users, Goals, Filters") and an explicit "Use when..." clause are present, but the "when" ("interact with Emelia data") is somewhat generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The main natural keyword is the brand name "Emelia" plus the entity nouns, but the trigger phrasing "interact with Emelia data" is generic and lacks common variations or synonyms, leaving keyword coverage incomplete.	3 / 5
Distinctiveness Conflict Risk	The unique brand name "Emelia" anchors a clear niche with low conflict risk, though the generic entity list (Organizations, Users, Goals, Filters) and broad "interact with Emelia data" trigger leave minor overlap with related CRM/marketing skills.	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/emelia/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.