CtrlK
BlogDocsLog inGet started
Tessl Logo

edrone

Edrone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Edrone data.

61

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/edrone/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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, executable Membrane CLI commands and a well-structured connection workflow with state-based branching. Its main weaknesses are an undefined 'Step 2' reference that breaks navigation, a 'Popular actions' section that points to discovery rather than naming actions, and minor verbosity in motivational framing.

Suggestions

Define or remove the 'Step 2' reference — it is referenced ('skip to Step 2', 'Skip to Step 2') but never labeled as a section.

Replace or supplement the 'Popular actions' placeholder with a few named high-value Edrone actions instead of only pointing back to the discovery command.

Show the polling loop explicitly (e.g. a `while state == BUILDING` example) so the validate-then-proceed workflow has an explicit feedback checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly efficient — direct CLI commands and brief explanations — but includes a few mildly over-explanatory passages like 'Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing'.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (login, connection ensure, action list/run, request) with concrete flags and JSON output examples covering the common cases.

5 / 5

Workflow Clarity

The connection setup has a clear sequence with state-handling branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but polling is described rather than shown as an explicit validate-then-proceed loop, and the 'Step 2' reference is never defined.

4 / 5

Progressive Disclosure

Content is well organized into clear sections (install, auth, connecting, actions, proxy, best practices) with no bundle files to offload to; minor gaps are the inline 'Popular actions' placeholder and an undefined 'Step 2' navigation reference.

4 / 5

Total

17

/

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 names a distinct brand and includes both a 'what' and an explicit 'Use when...' clause, satisfying completeness. Weaknesses are in specificity and trigger terms: the actions listed are generic and it omits the concrete Edrone capabilities (newsletters, funnels, reports, segmentation) and natural synonyms a user would say.

Suggestions

List concrete Edrone capabilities in the description, e.g. 'manage newsletter campaigns, funnels, customer segmentation, and reports'.

Add natural user-facing trigger phrases beyond 'interact with Edrone data', such as 'e-commerce CRM', 'marketing automation', or 'newsletter campaigns'.

Tighten 'Manage data, records, and automate workflows' into the specific Edrone actions so specificity reaches the comprehensive anchor.

DimensionReasoningScore

Specificity

Names the Edrone domain and a few concrete actions ('Manage data, records, and automate workflows'), but the actions are generic and not comprehensive — no mention of segmentation, newsletters, funnels, or reports shown in the body.

3 / 5

Completeness

It has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Edrone data'); the 'when' is present but could be more specific.

4 / 5

Trigger Term Quality

'Edrone' is a specific keyword and 'interact with Edrone data' is a reasonable phrase, but it lacks synonyms or natural variations a user might say (e.g. 'e-commerce CRM', 'newsletter', 'automation').

3 / 5

Distinctiveness Conflict Risk

The Edrone brand name gives it a clear niche unlikely to conflict with other skills, though the generic 'data'/'records'/'workflows' phrasing leaves minor overlap risk with broad CRM skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.