Name: melo
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

melo

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

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/melo/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 body provides concrete, executable CLI guidance and a reasonable connect-to-run workflow, but suffers from broken step numbering, missing validation checkpoints, and some padded prose. It is well structured for a single-file skill.

Suggestions

Fix the step numbering: label "Step 1" and "Step 2" explicitly and add the missing "1a" so the "skip to Step 2" references resolve.

Add a validation/verification step after `membrane action run` (check the `output` field, handle errors) to satisfy the feedback-loop requirement for batch operations.

Standardize the CLI invocation — pick either `membrane` or `npx @membranehq/cli@latest` and use it consistently across all examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable command snippets but includes padded prose ("burn less tokens", the agent-types list, repeated auth explanation) that could be tightened; matches the mostly-efficient-with-some-unnecessary-explanation anchor rather than a 4 because several sections over-explain.	3 / 5
Actionability	Concrete executable commands appear throughout ("membrane connection ensure", "membrane action run ... --input '{\"key\": \"value\"}'", a proxy options table), covering common cases copy-paste ready; not a 5 because the membrane vs npx @membranehq/cli invocation is inconsistent and a few examples omit full parameter detail.	4 / 5
Workflow Clarity	A connect→wait→search→run sequence exists with state-branch handling, but step numbering is broken ("skip to Step 2" with no Step 1/2 labels, a "1b" with no "1a"), and there is no validation/verification after running actions or for batch operations; per the rubric, missing validation in batch/destructive contexts caps this at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to mismanage; not a 5 because some inlineable-heavy content (popular actions, proxy option table) has no one-level-deep references to split it out.	4 / 5
	Total	14 / 20 Passed

Description

67%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 states concrete capabilities and includes an explicit Use-when trigger, satisfying both what and when. It is mostly distinct and specific, though the trigger phrasing is generic and lacks natural synonyms.

Suggestions

Tighten the trigger clause with concrete natural phrases, e.g. "Use when the user wants to manage Melo organizations, pipelines, users, goals, or filters".

Reconcile the described entities (Organizations/Pipelines/Users/Goals/Filters) with the body's entities (Project/Task/Member/Time Entry) so the description matches what the skill actually exposes.

Add file-format or synonym terms where applicable to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Quotes "Manage Organizations, Pipelines, Users, Goals, Filters" — several specific concrete actions named, matching the anchor for listing several specific actions with minor gaps; not a 5 because coverage is a flat list rather than a comprehensive set of distinct operations.	4 / 5
Completeness	Both a clear "what" ("Manage Organizations, Pipelines, Users, Goals, Filters") and an explicit "when" ("Use when the user wants to interact with Melo data") are present, matching the anchor where both exist but the when could be more specific; not a 5 because the when clause is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	Trigger guidance "Use when the user wants to interact with Melo data" plus entity names give some relevant keywords, but the phrasing is generic and lacks synonyms or natural variations a user would actually say; not a 4 because common natural terms are missing.	3 / 5
Distinctiveness Conflict Risk	The skill is anchored to the named niche "Melo" with distinct entity triggers, making it mostly distinct with only minor overlap risk against closely related data-management skills; not a 5 because the generic "interact with Melo data" trigger leaves some ambiguity.	4 / 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/melo/SKILL.md
Commit: f484c82

Reviewed: 6 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.