Name: thrivecart
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

thrivecart

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

Quality

64%

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

Quality

Content

67%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 delivers concrete, executable Membrane CLI guidance with a clear connection workflow and good sectioning. The main weakness is the padded introductory paragraph that explains concepts Claude already knows.

Suggestions

Trim the opening paragraph to a single line; drop the audience description ('Entrepreneurs, small business owners...') since Claude does not need it to act.

Replace placeholder CONNECTION_ID / actionId with a brief note on where to obtain them, or a worked end-to-end example.

Consider moving the proxy flag table into a short reference example to reduce surface area for the common action-run path.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening paragraph explaining what ThriveCart is and who uses it adds padding Claude largely already knows, fitting the 'mostly efficient but could be tightened' anchor.	3 / 5
Actionability	Concrete, executable `membrane` commands with real flags and examples cover install, auth, connection, action search/run, and proxy; minor gaps (placeholder ids) keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling feedback loop; a few validation gaps keep it at level 4.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections within a single file with no nested references and no bundle files to navigate, which is good structure with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

61%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 clearly targets a distinct niche and includes an explicit trigger clause, but its capability phrasing is generic. Tightening 'manage data, records, and automate workflows' into concrete actions would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and manage products, customers, transactions, subscriptions, and coupons in Thrivecart.'

Add natural trigger variations users might say, such as 'checkout pages', 'shopping cart', or 'ThriveCart orders'.

Keep the explicit 'Use when...' clause but pair it with the more specific actions to push completeness from 4 to 5.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Thrivecart integration') but the stated actions — 'Manage data, records, and automate workflows' — are generic rather than concrete, matching the 'names the domain but actions are minimal or generic' anchor better than level 3.	2 / 5
Completeness	Both 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Thrivecart data') are present; the 'what' could be more concrete, which fits the level-4 anchor.	4 / 5
Trigger Term Quality	'Thrivecart' and 'Thrivecart data' are relevant natural keywords, but there are few variations or synonyms, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	'Thrivecart integration' is a clear, specific niche with distinct triggers and minimal risk of conflicting with other skills.	5 / 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/thrivecart/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.