CtrlK
BlogDocsLog inGet started
Tessl Logo

shopee

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

52

Quality

59%

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/shopee/SKILL.md
SKILL.md
Quality
Evals
Security

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 highly actionable with concrete, copy-paste commands and a well-structured connection state machine, but it carries some redundant prose, an incoherent 'Step 2' reference, and no validation guidance for the destructive Record operations the skill exists to perform.

Suggestions

Add a short Records CRUD workflow with a verification step (e.g. re-fetch or list the record after create/update/delete) to satisfy the destructive-operations validation requirement.

Fix the broken cross-reference: replace 'skip to Step 2' with a concrete anchor like 'skip to Searching for actions', and label the section sequence consistently (e.g. Step 1 / 1b / Step 2).

Remove the duplicated `membrane action list` command in 'Popular actions' and the Shopee background paragraph that Claude does not need.

DimensionReasoningScore

Conciseness

The body is mostly executable commands, but the opening 'Shopee is a mobile-first e-commerce platform…' background prose and the duplicated `membrane action list` command (shown in both 'Searching for actions' and 'Popular actions') are unnecessary padding that could be tightened.

3 / 5

Actionability

Provides copy-paste-ready bash commands for every stage (install, login, connection ensure, poll, action list/run, request) plus a full proxy flag table; minor gap is the lack of a concrete filled example with a real Shopee action id rather than <actionId> placeholders.

4 / 5

Workflow Clarity

The connection flow has a real poll-until-READY feedback loop, but 'skip to Step 2' references a Step 2 that is never labeled, and the skill's core destructive CRUD on Records has no validation checkpoint, so per the destructive-ops cap it cannot exceed 3.

3 / 5

Progressive Disclosure

A single well-sectioned CLI reference file with clear headers and no need for external bundle files; it exceeds 50 lines so the simple-skill 5 exception does not apply, leaving minor organization gaps that hold it at 4.

4 / 5

Total

14

/

20

Passed

Description

57%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 correctly answers both what and when with an explicit 'Use when' trigger and is distinct via the Shopee proper noun, but its capability language is generic ('Manage Recordses') and lacks concrete operations or keyword variations.

Suggestions

Replace the generic 'Manage Recordses' with concrete operations, e.g. 'Create, read, update, delete, and list Shopee Records'.

Expand trigger terms with natural synonyms users might say, such as 'Shopee orders, products, shop data, or Shopee API'.

Fix the apparent typo 'Recordses' to 'Records' for clarity.

DimensionReasoningScore

Specificity

Names the domain ('Shopee integration') but the only action is the generic verb 'Manage Recordses' with no concrete operations like create/read/update/delete; matches the 'names domain but actions minimal/generic' anchor and is clearly below the 1-2 concrete actions needed for a 3.

2 / 5

Completeness

Both a 'what' ('Shopee integration. Manage Recordses.') and an explicit 'when' ('Use when the user wants to interact with Shopee data.') are present; it is not a 5 because the 'what' is vague rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

'Shopee' and 'interact with Shopee data' are relevant natural keywords, but common variations or synonyms are absent, fitting the 'some relevant keywords but missing variations' anchor rather than the fuller coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The proper noun 'Shopee' gives a clear niche with low conflict risk, but the templated 'Manage X / interact with X data' phrasing overlaps sibling Membrane integration skills, keeping it just below the minimal-risk 5.

4 / 5

Total

13

/

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.