Name: eden-ai
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

eden-ai

Eden AI integration. Manage Recordses. Use when the user wants to interact with Eden AI 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/eden-ai/SKILL.md

Quality

Content

81%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 a strong, executable integration guide with a well-sequenced, validated connection workflow and concrete CLI commands. Its main weaknesses are mild verbosity in the intro and a large inline actions table that would benefit from being split into a reference file.

Suggestions

Trim the Eden AI overview paragraph and 'auth plumbing' commentary to assume Claude's familiarity and save tokens.

Move the full Popular actions table into a references/ file (e.g. ACTIONS.md) and keep only 3-4 representative examples inline.

Consider extracting the proxy request options table to a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph explaining what Eden AI is and prose like 'so you can focus on the integration logic rather than auth plumbing' add explanation Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than lean.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action run/list, request) with --json flags and a concrete input example, covering the common cases the 'fully executable' anchor calls for.	5 / 5
Workflow Clarity	The connection flow is a clearly sequenced state machine (install → auth → ensure → poll until READY) with explicit validation via the --wait poll loop and branching on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, matching the anchor for clear sequence with explicit checkpoints and error-recovery feedback.	5 / 5
Progressive Disclosure	Sections are well-organized and self-contained with no nested references, but the 20-row Popular actions table and proxy options table are sizable reference material inlined in SKILL.md that could live in a separate file, fitting 'good structure, most content appropriately placed, minor organization gaps' rather than an ideally split layout.	4 / 5
	Total	17 / 20 Passed

Description

57%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 correctly names the Eden AI platform and includes an explicit 'Use when' clause, but it is thin on concrete capabilities and natural trigger phrases, leaning on the oddly generic 'Manage Recordses'. It is adequate for routing but undersells the skill's actual actions.

Suggestions

Replace 'Manage Recordses' with concrete Eden AI actions, e.g. 'Analyze sentiment, translate text, detect objects in images, and extract text via OCR'.

Expand the 'Use when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants sentiment analysis, translation, OCR, image recognition, or other Eden AI model tasks'.

Add file-format or endpoint synonyms (e.g. text, images, audio, video) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ("Eden AI integration") but the only stated action is the oddly generic "Manage Recordses", with "interact with Eden AI data" adding no concrete capability — matching the anchor that names the domain with minimal/generic actions rather than listing concrete actions.	2 / 5
Completeness	It states both what ("Eden AI integration. Manage Recordses.") and when ("Use when the user wants to interact with Eden AI data."), satisfying the anchor for having both with a 'when' that could be more specific; it is not a 5 because the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	The proper noun "Eden AI" is a relevant keyword a user would naturally say, but the description offers no common task phrases or synonyms (e.g. sentiment, translation, OCR), so it sits at the 'some relevant keywords but missing variations' anchor rather than full coverage.	3 / 5
Distinctiveness Conflict Risk	"Eden AI" is a named platform giving a clear niche with minimal conflict risk, but the generic "interact with Eden AI data" trigger leaves minor overlap risk with broad data skills, placing it at 'mostly distinct' rather than fully distinct.	4 / 5
	Total	13 / 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/eden-ai/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.