CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commercehq

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

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/commercehq/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A strong, highly actionable CLI integration guide with executable commands throughout and a well-structured connection state machine, held back by missing validation guidance for the destructive operations it exposes and a broken internal "Step 2" reference.

Suggestions

Add validation before destructive actions, e.g. instruct to run get-collection/get-product/get-customer first and confirm with the user before any delete-* action.

Fix the dangling reference: "skip to Step 2" points to a heading that does not exist — either label the next section as Step 2 or reword to reference the actual section name ("Searching for actions").

Trim the low-value content: the bare Store/Products/Orders bullet overview and the filler line "Use action names and parameters as needed." add tokens without guidance.

DimensionReasoningScore

Conciseness

The body is mostly efficient command documentation, with only minor trimmable content: the bare Store/Dashboard/Products bullet overview, the filler line "Use action names and parameters as needed.", and the introductory paragraph explaining what CommerceHQ is.

4 / 5

Actionability

Copy-paste-ready bash commands cover the common cases end to end — install, login (including headless completion), connection ensure with polling, action search/run with --input JSON, and a proxy request flag table — each with exact syntax.

5 / 5

Workflow Clarity

The install → login → connect → poll → search → run sequence is clear with a state machine and re-poll loop, but the action catalog includes destructive operations (delete-collection, delete-product, delete-customer) with no validation or verification steps, which caps this at 3; the dangling "skip to Step 2" reference to a nonexistent heading adds a coherence gap.

3 / 5

Progressive Disclosure

A single-file skill with no bundle files and well-organized sections that are easy to navigate; the popular-actions catalog and proxy flag table are inline and could arguably live in a reference file, but placement is defensible at this size.

4 / 5

Total

16

/

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 correctly uses third-person voice and includes an explicit "Use when" trigger anchored to a distinct platform name, but it wastes the capability statement on generic filler ("Manage data, records, and automate workflows") instead of the concrete CRUD operations over products, orders, customers, and collections that the skill actually provides.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete actions, e.g. "Create, update, and delete products, orders, customers, and collections in a CommerceHQ store."

Broaden the trigger clause to include natural synonyms: "Use when the user mentions CommerceHQ or wants to manage their store's products, orders, customers, or collections."

DimensionReasoningScore

Specificity

"Manage data, records, and automate workflows" names the CommerceHQ domain but the actions are minimal and generic — no concrete capabilities like products, orders, customers, or collections management are mentioned.

2 / 5

Completeness

Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with CommerceHQ data") are present, though the "when" is narrow and the "what" is generic.

4 / 5

Trigger Term Quality

"CommerceHQ" and "data" are relevant keywords, but common natural variations users would say ("store", "products", "orders", "e-commerce", "shop") are missing.

3 / 5

Distinctiveness Conflict Risk

"CommerceHQ" is a distinctly named platform with clear triggers, giving it a clear niche and minimal risk of firing for the wrong skill.

5 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.