Name: shoprocket-co
Rating: 56.8 (1 reviews)
Author: membranedev

shoprocket-co

Shoprocket integration. Manage data, records, and automate workflows. Use when the user wants to interact with Shoprocket 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/shoprocket-co/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 body is highly actionable with copy-paste Membrane commands and a clear connection workflow, but it opens with marketing fluff and lacks validation/error-recovery checkpoints around running actions. Trimming the intro and adding verification steps would raise its weakest dimensions.

Suggestions

Cut the opening marketing paragraph about what Shoprocket is and who it is for; keep only the one-line official-docs pointer and jump straight to working with the CLI.

Add a validation checkpoint after connecting (e.g. confirm the connection via `membrane connection list --json` and verify the new connectionId appears) and a verify/dry-run note before running mutating actions.

Add brief error-recovery guidance for `membrane action run` and `membrane request` failures (e.g. re-check connectionId, inspect the JSON error, retry) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening marketing paragraph ('Shoprocket is an e-commerce platform that allows users to easily add a shopping cart... designed for small businesses, creators, and developers') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary explanation Claude does not need.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common case (install, login, connect, list actions, run actions, proxy) plus a thorough proxy-flags table and a concrete output-parsing hint ('output.items[0].element?.id').	5 / 5
Workflow Clarity	A clear sequence exists (install -> login -> connect -> discover -> run/proxy) with one checkpoint (checking existing connections before creating), but there are no validation or verification steps after connecting or before/after running actions, and no error-recovery guidance.	3 / 5
Progressive Disclosure	No bundle files exist and the content is appropriately self-contained with well-organized section headers and easy navigation; minor redundancy between 'Searching for actions' and 'Popular actions' keeps it just below a 5, and the over-50-line simple-skill exception does not apply.	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 has an explicit trigger clause and a highly distinctive platform name, but its capability verbs are generic ('Manage data, records, and automate workflows') rather than concrete. Strengthening the action list would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Shoprocket actions, e.g. 'Manage products, orders, and customers; search and run Shoprocket actions; proxy custom API requests.'

Add natural trigger variations users might say, e.g. 'Use when the user mentions Shoprocket, wants to manage Shoprocket products/orders, or needs Shoprocket checkout data.'

Tighten 'Manage data, records, and automate workflows' into specific nouns that map to Shoprocket entities (products, orders, customers).

Dimension	Reasoning	Score
Specificity	The description names the domain (Shoprocket) but its actions are generic and abstract ('Manage data, records, and automate workflows') with no concrete verbs like extract, create, or sync, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It explicitly states both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Shoprocket data'), so it clears anchor 3; the 'what' is vague, keeping it just below a 5.	4 / 5
Trigger Term Quality	'Shoprocket' and 'interact with Shoprocket data' provide one strong natural keyword a user would say, but there are no synonyms, product-type variations, or file extensions, matching the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	'Shoprocket' is a specific named platform with a distinct trigger phrase ('interact with Shoprocket data'), giving it a clear niche and minimal conflict risk 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/shoprocket-co/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.