Name: bigcommerce
Rating: 61.6 (1 reviews)
Author: membranedev

bigcommerce

BigCommerce integration. Manage Products, Customers, Orders, Carts, Coupons, GiftCertificates and more. Use when the user wants to interact with BigCommerce data.

Quality

73%

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

Quality

Content

75%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 copy-paste commands and a well-sequenced, state-aware connection workflow. It is held back by some boilerplate explanation of concepts Claude already knows and by a large inline action table that would benefit from being split into a reference file.

Suggestions

Trim the marketecture paragraph and the 'so you can focus on the integration logic' rationale to improve token efficiency.

Move the full 'Popular actions' table into a references/ file and link to it, keeping only the top few inline, to strengthen progressive disclosure.

Add an explicit validation checkpoint after running actions (e.g. check the `output` field / error handling) to nudge workflow clarity toward 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and a compact action table, but it pads concepts Claude already knows (the BigCommerce marketecture paragraph, 'This skill uses the Membrane CLI to interact... so you can focus on the integration logic') that could be trimmed.	3 / 5
Actionability	Fully executable copy-paste-ready commands for install, login, connection ensure, polling, action list/run, and proxy, with a clear options table and JSON-input examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state-handling branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry loop; minor gap is the lack of an explicit validation/verification checkpoint after running actions, though the destructive-op cap is not triggered since actions themselves are gated.	4 / 5
Progressive Disclosure	Well-organized sections with a 'Popular actions' table inlining the most-needed items and clear navigation; no external bundle files exist so there are no buried references, but the 20-row action table is borderline inline content that could live in a separate reference, leaving it just below the 5 anchor.	4 / 5
	Total	16 / 20 Passed

Description

71%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 states what the skill manages and gives an explicit 'Use when' trigger, anchored firmly to the distinct BigCommerce niche. It loses points mainly for trigger term breadth and slightly generic 'Manage' actions rather than enumerating concrete operations.

Suggestions

Expand the trigger clause with natural user phrasings, e.g. 'Use when the user wants to manage BigCommerce products, orders, customers, or store data'.

Replace the generic 'Manage ... and more' with a few concrete verbs (list, create, update, delete) to lift specificity toward the comprehensive anchor.

Consider adding the file/resource synonyms users actually say (e.g. 'catalog', 'store', 'e-commerce data') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names concrete entities ('Products, Customers, Orders, Carts, Coupons, GiftCertificates') plus the verb 'Manage', but actions are generic CRUD-ish rather than a list of specific actions, leaving minor coverage gaps relative to the comprehensive anchor.	4 / 5
Completeness	Answers 'what' clearly ('Manage Products, Customers, Orders...') and provides an explicit 'Use when the user wants to interact with BigCommerce data' trigger; the 'when' could be more specific with concrete trigger phrases, so it sits just below the explicit-concrete anchor of 5.	4 / 5
Trigger Term Quality	Includes 'BigCommerce' and 'interact with BigCommerce data' as triggers, but misses the natural phrasings and synonyms users say ('products', 'orders', 'store', 'catalog') beyond the bare entity list, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	BigCommerce is a clearly named, distinct e-commerce niche with 'BigCommerce' appearing throughout, giving it a clear niche and minimal conflict risk with 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/bigcommerce/SKILL.md
Commit: f484c82

Reviewed: ~3 hours 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.