Name: meesho
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

meesho

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

Quality

68%

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/meesho/SKILL.md

Quality

Content

68%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 actionable and well-structured with strong command examples and a solid connection-state feedback loop, but the data-operation workflow omits validation for destructive Records operations and a couple of sections are redundant. Adding verification checkpoints would notably improve workflow clarity.

Suggestions

Add a validation/verification step after running destructive actions (e.g. re-query or check the `output`/error fields and confirm success before proceeding), so the CRUD workflow is not capped at 3.

Merge or differentiate the "Searching for actions" and "Popular actions" sections, which both restate the `action list` command, to remove redundancy.

Trim soft prose like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, built from executable commands, a flag table, and brief prose, with only minor padding such as "so you can focus on the integration logic rather than auth plumbing"; it is noticeably above the midpoint but not fully lean, so 4 rather than 5.	4 / 5
Actionability	It provides concrete, copy-pasteable commands (e.g. `membrane connection ensure "https://www.meesho.com/" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --json`) with a flag table, but uses unsubstituted placeholders (CONNECTION_ID, actionId, QUERY) that keep it just below fully copy-paste-ready.	4 / 5
Workflow Clarity	There is a clear sequence (install → auth → connect → poll → search → run → proxy) with a good feedback loop for connection state, but the core Records CRUD workflow (create/update/delete) lacks validation or verification checkpoints; per the destructive/batch cap this holds it at 3 rather than 4.	3 / 5
Progressive Disclosure	The single-file body is well-organized into clear headed sections with no nested references, but the "Popular actions" section largely duplicates the "Searching for actions" command and adds minor organization gaps, keeping it just below 5.	4 / 5
	Total	15 / 20 Passed

Description

68%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 successfully pairs a what and a when around a distinctive named platform, but the capability statement is thin and generic ("Manage Recordses"). Tightening the action list and adding concrete trigger phrases would lift specificity and completeness.

Suggestions

Replace the generic "Manage Recordses" with concrete operations, e.g. "Create, read, update, delete, and list Records in Meesho".

Expand the trigger clause with natural user phrasings, e.g. "Use when the user wants to query, create, or update Meesho Records or Meesho data."

Fix the garbled token "Recordses" which reads as a templating artifact and weakens clarity.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Meesho integration") and a single generic action ("Manage Recordses"), which reads as minimal/generic rather than a list of concrete operations; it is below the 3-anchor which expects 1-2 concrete actions.	2 / 5
Completeness	It states a "what" ("Meesho integration. Manage Recordses.") and an explicit "when" ("Use when the user wants to interact with Meesho data"), but the "when" could be more specific with concrete trigger phrases, keeping it just below 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Meesho data" provides good keyword coverage built around the natural product name "Meesho", though it lacks synonyms or file-extension variants that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	"Meesho" is a named external platform giving the skill a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 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/meesho/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.