Name: elopage
Rating: 60 (1 reviews)
Author: membranedev

elopage

Elopage integration. Manage Deals, Persons, Organizations, Leads, Projects, Activities and more. Use when the user wants to interact with Elopage data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/elopage/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 body is highly actionable with executable CLI commands and a well-structured connection workflow including validation checkpoints, weakened only by mild explanatory padding and an inline reference table that could be split out.

Suggestions

Trim the introductory "Elopage is an e-commerce platform..." paragraph and "Use action names and parameters as needed" filler to assume Claude's domain knowledge.

Label the post-connection phase explicitly (e.g., a "## Step 2: Search and run actions" header) so the "skip to Step 2" reference resolves.

Move the 20-row popular-actions table into a references file and keep only a few high-value examples inline to reduce token cost.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient commands and tables, but the opening paragraph explaining what Elopage is and filler like "Use action names and parameters as needed" pad content Claude could infer.	3 / 5
Actionability	It provides copy-paste ready commands (membrane connection ensure, action run, request) with flags, JSON input examples, and a populated popular-actions table covering common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-checking validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-after-action feedback loop, but "skip to Step 2" references a step that is not explicitly labeled as a section.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections with no nested references, though the large inline popular-actions and proxy-option tables are reference material that could live in a separate file.	4 / 5
	Total	16 / 20 Passed

Description

66%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 covers a clear niche and includes an explicit Use-when clause, but relies on a single generic verb ("Manage") and a broad trigger phrase rather than enumerating concrete actions and natural trigger terms.

Suggestions

Replace the generic "Manage" with 2-3 concrete verbs (e.g., "List, create, and update Deals, Persons, Organizations") to raise specificity.

Expand the trigger with natural phrases users would say, such as "Use when the user wants to query Elopage orders, customers, payouts, or webhook endpoints."

Drop "and more" in favor of naming the highest-value entities to avoid vague over-claims.

Dimension	Reasoning	Score
Specificity	"Manage Deals, Persons, Organizations, Leads, Projects, Activities and more" names many entities but applies only one generic verb ("Manage"), so concrete actions are minimal rather than comprehensive.	3 / 5
Completeness	It states both what ("Manage Deals, Persons, Organizations...") and when ("Use when the user wants to interact with Elopage data"), but the when-clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the app name "Elopage" plus several entity keywords, but the natural trigger phrase is limited to "interact with Elopage data", missing common variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	"Elopage" is a uniquely named niche platform, and the trigger is scoped to Elopage data, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/elopage/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.