Name: lazada
Rating: 58.4 (1 reviews)
Author: membranedev

lazada

Lazada integration. Manage Products, Orders, Sellers, Users, Vouchers, Wallets and more. Use when the user wants to interact with Lazada data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/lazada/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 is a solid, command-driven CLI guide with good actionability and clean sectioning. Its main weaknesses are an unnecessary intro explaining Lazada, a broken "Step 2" reference, and missing validation checkpoints for destructive/batch Lazada operations.

Suggestions

Remove or shrink the intro paragraph that explains what Lazada is and lists countries; Claude already knows this and it costs tokens.

Add explicit validation steps before running destructive or batch actions (e.g., verify connection state is READY and dry-run/confirm before order, payment, or return mutations) to lift workflow clarity above the cap of 3.

Fix the dangling "skip to Step 2" reference by labeling the action-search/run section as Step 2 or rewording the pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight commands, but the opening paragraph explains what Lazada is ("a popular Southeast Asian e-commerce platform, similar to Amazon or eBay") with a country list that Claude already knows, and phrases like "so you can focus on the integration logic rather than auth plumbing" add padding.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for every main workflow (install, login, connection ensure, action list/run, request proxy) plus a flags table; minor gaps remain in placeholder substitution (CONNECTION_ID, <actionId>) and how to form the --intent "QUERY" string.	4 / 5
Workflow Clarity	A clear install→auth→connect→poll→search→run sequence exists with state-based branching, but it lacks validation/verification checkpoints for destructive Lazada operations (orders, payments, returns) and the "skip to Step 2" reference points to no labeled Step 2, so it is capped at 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Working with Lazada, Best practices) with no nested or buried references, and since no bundle files exist everything is appropriately inline; minor gaps are the inlined entity list and proxy flag table that could live in references.	4 / 5
	Total	14 / 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.

The description is well-targeted to a distinct platform and includes a usable "Use when" clause plus a list of concrete Lazada objects. It is held back mainly by the single generic verb "Manage" and the vague "and more" tail.

Suggestions

Replace the single verb "Manage" with a few varied concrete actions (e.g., "List and update products, fetch orders, issue vouchers, query wallets") to lift specificity.

Make the trigger clause more concrete by listing what users might say (e.g., "Use when the user wants to check Lazada orders, update product listings, or query wallet/voucher data").

Drop the "and more" tail or replace it with an explicit short list, since vague hedges weaken both specificity and trigger quality.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists six concrete Lazada objects ("Products, Orders, Sellers, Users, Vouchers, Wallets") but applies only one generic verb ("Manage") and trails off with "and more", so the actions themselves are not varied or comprehensive.	3 / 5
Completeness	It has both a clear "what" (manage Lazada Products, Orders, etc.) and an explicit "when" ("Use when the user wants to interact with Lazada data"), but the trigger clause is fairly broad rather than listing concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	Natural user-facing terms are present ("Lazada" plus entity names like Products, Orders, Vouchers, Wallets that users would actually say), with only minor synonyms/variations missing; "interact with Lazada data" is slightly generic.	4 / 5
Distinctiveness Conflict Risk	"Lazada" is a specific named platform giving the skill a clear niche with distinct triggers and minimal conflict risk against other skills.	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/lazada/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.