Name: jumpseller
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jumpseller

Jumpseller integration. Manage Stores. Use when the user wants to interact with Jumpseller data.

Quality

65%

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/jumpseller/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 highly actionable, with executable CLI commands and a clear connection workflow, and is well-structured for navigation. Its main weaknesses are an unnecessary introductory explanation of Jumpseller and the absence of validation checkpoints for the destructive CRUD actions it exposes.

Suggestions

Trim the opening paragraph that explains what Jumpseller is; Claude already knows this, so lead directly with the integration workflow.

Add a validation/verification step before destructive actions (e.g. list-then-confirm before delete-product/delete-customer) to lift the workflow-clarity cap.

Move the 20-row popular actions table into a references file and link to it from SKILL.md to deepen progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens by explaining what Jumpseller is ("an e-commerce platform that allows users to create and manage online stores... primarily used by small to medium-sized businesses") and includes padded phrasing like "so you can focus on the integration logic rather than auth plumbing", fitting the anchor for mostly-efficient content with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands across the common cases (login, connection ensure, action list, action run with JSON input, request proxy) plus a flag reference table, matching the anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connect-and-poll sequence has clear states and checkpoints, but the skill exposes destructive and batch operations (delete-product, delete-customer, delete-category) with no validation or verification guidance before running them, so per the rubric cap workflow clarity cannot exceed 3.	3 / 5
Progressive Disclosure	No bundle files exist and the body is well-organized into clear sections (install, auth, connect, search, popular actions, proxy, best practices) with appropriately placed inline tables; structure is good with only minor organization gaps, fitting the "good structure; most content appropriately placed" anchor.	4 / 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 successfully states both the skill's purpose and an explicit use trigger, anchored on a distinctive platform name. It is let down by thin action specificity and limited trigger-term coverage that omit the concrete entities (products, orders, customers) users would mention.

Suggestions

Expand "Manage Stores" into concrete capabilities, e.g. "Manage products, orders, customers, and categories in Jumpseller stores."

Broaden the trigger clause to name what users say: "Use when the user wants to manage Jumpseller products, orders, customers, or categories."

Keep the description in third person and avoid first/second person to preserve specificity.

Dimension	Reasoning	Score
Specificity	The description names the Jumpseller domain and one concrete-ish action ("Manage Stores"), but offers only that single generic action rather than several specific ones, matching the anchor for naming a domain with 1-2 actions that are not comprehensive.	3 / 5
Completeness	Both "what" ("Jumpseller integration. Manage Stores.") and an explicit "when" ("Use when the user wants to interact with Jumpseller data.") are present, but the trigger clause is fairly generic rather than concrete, fitting the anchor where both exist yet "when" could be more specific.	4 / 5
Trigger Term Quality	It includes the key natural keyword "Jumpseller" (what a user would actually say), but lacks common variations or synonyms such as products, orders, customers, or e-commerce, so it fits the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The named platform "Jumpseller" carves a clear niche with low conflict risk, but the thin set of distinct triggers leaves minor overlap with general e-commerce skills, matching the "mostly distinct; minor overlap risk" anchor rather than the comprehensive-trigger 5.	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/jumpseller/SKILL.md
Commit: f484c82

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