Name: mercado-pago
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mercado-pago

Mercado Pago integration. Manage Payments, Refunds. Use when the user wants to interact with Mercado Pago data.

Quality

74%

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/mercado-pago/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.

A well-structured, highly actionable integration skill whose concrete CLI commands and connection-state feedback loop are its strengths. The main drags are an unnecessary background intro paragraph, a duplicated action-discovery section, and a broken "Step 2" cross-reference.

Suggestions

Remove or shrink the opening "Mercado Pago is a popular Latin American online payments platform... similar to PayPal" paragraph; Claude does not need the product backstory.

Merge the "Searching for actions" and "Popular actions" sections, which both demonstrate `membrane action list --intent`, into one to eliminate redundancy.

Fix the broken "skip to Step 2" reference (there is no Step 2) and relabel "1b" with a matching "1a" or renumber the connection steps so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The intro paragraph ("similar to PayPal", "widely used by merchants and consumers in Latin America for e-commerce transactions") explains background Claude does not need, and the action-list guidance is duplicated across "Searching for actions" and "Popular actions", so it is mostly efficient but carries several padded sections rather than just minor trimmings.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure/get with --wait, action list, action run with JSON input, request with a full flags table), covering the workflow concretely and executably.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with an explicit polling feedback loop and per-state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the instruction to "skip to Step 2" references a non-existent step and the "1b" heading has no matching "1a", leaving minor structural gaps that keep it below 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is organized into clear, well-labeled sections with no content that needs splitting out, but at over 50 lines it carries minor organization gaps (the duplicated action-list sections and the broken Step 2 cross-reference) rather than the tight single-purpose structure that would score 5.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

A concise, third-person description that clearly scopes a single platform and provides an explicit Use-when trigger, answering both what and when. Its main weakness is the generic verb "Manage" and a when clause that could name payments/refunds as concrete triggers.

Dimension	Reasoning	Score
Specificity	"Manage Payments, Refunds." names the Mercado Pago domain and two concrete actions, but the verb "Manage" is generic and coverage is not comprehensive, matching the anchor for 1-2 concrete actions rather than the several required for a 4.	3 / 5
Completeness	It has both a "what" ("Mercado Pago integration. Manage Payments, Refunds.") and an explicit "when" ("Use when the user wants to interact with Mercado Pago data."), but the when clause is generic and lacks concrete payment/refund triggers, so it is not the fully explicit 5.	4 / 5
Trigger Term Quality	Natural terms "Mercado Pago", "Payments", "Refunds", and "interact with Mercado Pago data" give good keyword coverage a user would actually say, but synonyms/aliases (e.g. "MP", "checkout") are missing, so it does not reach comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	"Mercado Pago integration" targets a single, well-known platform with distinct triggers, giving it a clear niche with minimal risk of firing for an unrelated skill.	5 / 5
	Total	16 / 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/mercado-pago/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.