CtrlK
BlogDocsLog inGet started
Tessl Logo

mercado-libre

Mercado Libre integration. Manage Recordses. Use when the user wants to interact with Mercado Libre data.

58

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mercado-libre/SKILL.md
SKILL.md
Quality
Evals
Security

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 commands and good validation feedback loops in the connection workflow. Its weaknesses are an unnecessary concept-explaining intro that hurts conciseness and a broken step-numbering scheme that slightly muddies workflow clarity.

Suggestions

Cut the Mercado Libre background paragraph ('largest online marketplace... similar to eBay or Amazon') — Claude already knows this; lead with the integration purpose instead.

Fix the step numbering: define explicit 'Step 1' / 'Step 2' headers (or remove the 'Step 2' and '1b' references) so the connect → search → run sequence is unambiguous.

Merge the overlapping 'Searching for actions' and 'Popular actions' sections to remove the duplicated `action list` guidance.

DimensionReasoningScore

Conciseness

The body is mostly command-driven and efficient, but it opens by explaining what Mercado Libre is ("the largest online marketplace in Latin America. It's similar to eBay or Amazon...") and narrates Membrane's behavior conceptually — concepts Claude already knows. Matches 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not a 4 because the intro paragraph and a few explanatory sentences are clearly trimmable padding.

3 / 5

Actionability

It provides copy-paste-ready commands for every common case — install (`npm install -g @membranehq/cli@latest`), login, `connection ensure`, action list/run with `--input` JSON, and a full proxy flag table. Matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases'.

5 / 5

Workflow Clarity

The connect flow has explicit validation checkpoints and a feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), which is strong, but the step numbering is broken: the text references 'Step 2' and a '#### 1b' header with no 1a or Step 2 header defined. Matches 'Clear sequence with most checkpoints present; minor validation gaps'; not a 5 because the inconsistent numbering leaves the overall sequence slightly ambiguous.

4 / 5

Progressive Disclosure

No bundle files exist, and the self-contained CLI usage is appropriately inline and organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Best practices). Matches 'Good structure; most content appropriately placed; minor organization gaps'; not a 5 because 'Popular actions' partly duplicates the 'Searching for actions' section and the structure could be tightened.

4 / 5

Total

16

/

20

Passed

Description

61%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 has a clear explicit trigger clause and a highly distinct niche, but its capability statement is thin and generic ('Manage Recordses'), which limits specificity and trigger-term breadth. It answers both what and when, just not comprehensively.

Suggestions

Replace 'Manage Recordses' with concrete enumerated actions (e.g., 'Create, read, update, delete, and list Records') so specificity and trigger coverage improve together.

Add natural trigger variations beyond the platform name (e.g., 'Use when the user wants to manage Mercado Libre listings, orders, or Records data').

Fix the apparent typo 'Recordses' → 'Records' to match the term used in the body.

DimensionReasoningScore

Specificity

It names the domain ("Mercado Libre integration") but the only action verb is "Manage Recordses" — a single minimal, generic action with no enumerated operations (the CRUD list lives in the body, not the description). This matches the anchor 'Names the domain but actions are minimal or generic', and is not a 3 because it does not list 1-2 concrete actions.

2 / 5

Completeness

It states a what ("Mercado Libre integration. Manage Recordses.") and an explicit when ("Use when the user wants to interact with Mercado Libre data"), and the 'Use when...' clause avoids the 3-cap. It fits 'Has both what and when; when could be more explicit or specific'; not a 5 because the what is vague ('Manage Recordses') and the when lacks concrete trigger phrases.

4 / 5

Trigger Term Quality

"Mercado Libre" is a strong distinctive keyword and "Use when the user wants to interact with Mercado Libre data" supplies a natural trigger, but coverage stops at one term with no synonyms or variations (no ML, marketplace, listings, orders). Matches 'Some relevant keywords but missing common variations or synonyms'; not a 4 because keyword breadth is thin.

3 / 5

Distinctiveness Conflict Risk

"Mercado Libre" is a single named external platform with distinct triggers, so conflict risk with other skills is minimal — matching 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 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.