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

commercehq

CommerceHQ integration. Manage data, records, and automate workflows. Use when the user wants to interact with CommerceHQ 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/commercehq/SKILL.md

Quality

Content

65%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 CLI commands and a clear connection workflow, but loses points for an unnecessary explanatory intro, missing validation around destructive/batch operations, and inlined bulk reference content.

Suggestions

Add a validation checkpoint before destructive runs, e.g. 'Before delete-* actions, run a get-* to confirm the target ID and confirm with the user'.

Move the Popular actions table into a references file (e.g. ACTIONS.md) and link to it from a short inline summary to improve progressive disclosure.

Trim the introductory paragraph about CommerceHQ's market positioning and remove filler like 'Use action names and parameters as needed'.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the intro paragraph explaining what CommerceHQ is ('similar to Shopify... built-in marketing tools and dropshipping integrations') and filler like 'Use action names and parameters as needed' are unnecessary padding.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection, action search/run, and proxy requests, with flags and JSON examples covering the common cases.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based polling checkpoints, but destructive actions (delete-collection, delete-customer, delete-product) and batch list operations have no validation/verification step before execution, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Sections are clearly organized, but the large Popular actions table (bulk reference content) is inlined in SKILL.md with no external reference files to split it out, and no bundle files are used.	3 / 5
	Total	14 / 20 Passed

Description

66%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 identifies a specific platform and includes an explicit 'Use when' trigger, answering both what and when. Its main weakness is generic action language ('manage data, records, automate workflows') that lacks concrete, distinctive capabilities.

Suggestions

Replace generic verbs with concrete operations, e.g. 'Create and update products, manage orders and customers, list collections' so capabilities are specific.

Expand the trigger clause with natural variations users might say, e.g. 'Use when the user mentions CommerceHQ orders, products, customers, or store management'.

Tighten 'Manage data, records, and automate workflows' into named CRUD actions tied to CommerceHQ resources to lift specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (CommerceHQ) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic verbs rather than concrete operations, so coverage is not comprehensive.	3 / 5
Completeness	Provides both a 'what' (integration, managing data/records, automating workflows) and an explicit 'when' ('Use when the user wants to interact with CommerceHQ data'), though the 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the natural term 'CommerceHQ' and the phrase 'interact with CommerceHQ data', but lacks synonyms or common variations a user might say.	3 / 5
Distinctiveness Conflict Risk	Targets a specific named platform (CommerceHQ) with distinct triggers, making conflict with other skills unlikely.	5 / 5
	Total	15 / 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/commercehq/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.