Name: sellercloud
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

sellercloud

Sellercloud integration. Manage data, records, and automate workflows. Use when the user wants to interact with Sellercloud data.

Quality

66%

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

Quality

Content

71%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 a clear connection workflow including state-based checkpoints. It loses points on an unnecessary introductory paragraph and on a lack of progressive disclosure structure.

Suggestions

Trim the opening 'Sellercloud is an e-commerce management platform...' paragraph and the marketing-style auth-plumbing aside to respect token budget.

Move the detailed clientAction state-machine reference and proxy flag table into reference files (e.g. CONNECTION_STATES.md, PROXY.md) and link to them from the body.

Add an explicit post-run validation step (e.g. inspect the `output` field / error handling) to round out the workflow's feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and a compact flags table, but the opening paragraph explaining what Sellercloud is ('e-commerce management platform... Amazon, eBay, and Walmart') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add unnecessary explanation.	3 / 5
Actionability	Provides fully executable, copy-paste ready commands for every stage (install, login, connection ensure/get --wait, action list/run, request) plus a flag table covering the common proxy cases.	5 / 5
Workflow Clarity	The connect -> poll -> branch-on-state sequence has explicit checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a retry loop, but lacks an explicit validation step after running an action.	4 / 5
Progressive Disclosure	The file is well-sectioned but monolithic (~120 lines) with no bundle references; content such as the detailed clientAction state machine or the proxy flag table could live in separate referenced files.	3 / 5
	Total	15 / 20 Passed

Description

62%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 concise, third person, and answers both 'what' and 'when', which is solid. Its main weakness is generic action vocabulary ('Manage data, records') and limited trigger-term breadth.

Suggestions

Replace generic verbs with concrete Sellercloud capabilities, e.g. 'Manage orders, inventory, products, and companies; automate order workflows.'

Expand the 'Use when' clause with natural trigger phrases users would say, e.g. 'Use when the user wants to query or update Sellercloud orders, products, or inventory.'

Tie trigger terms to the marketplace/accounting domain language (orders, shipments, catalog) to boost distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the Sellercloud domain plus a few actions ('Manage data, records, and automate workflows'), but these actions are fairly generic and not a comprehensive enumeration of capabilities.	3 / 5
Completeness	States both the 'what' (Sellercloud integration: manage data/records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Sellercloud data'), though the 'when' could name more concrete triggers.	4 / 5
Trigger Term Quality	Includes relevant keywords ('Sellercloud', 'interact with Sellercloud data') but misses common natural variations or synonyms a user might say (e.g. orders, inventory, Amazon/eBay marketplaces).	3 / 5
Distinctiveness Conflict Risk	The proper noun 'Sellercloud' carves a clear niche with distinct triggers and low overlap risk; the only softness is the generic 'data, records' phrasing that could bleed into other data skills.	4 / 5
	Total	14 / 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/sellercloud/SKILL.md
Commit: f484c82

Reviewed: 4 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.