CtrlK
BlogDocsLog inGet started
Tessl Logo

shoprocket

Shoprocket integration. Manage Organizations. Use when the user wants to interact with Shoprocket data.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

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 content is well-structured and action-oriented, giving executable commands and a clearly sequenced connection workflow with validation checkpoints. Main gaps are minor verbosity in the intro and placeholder-only examples rather than a worked end-to-end run.

DimensionReasoningScore

Conciseness

The body is mostly lean command examples and a flags table with only minor over-explanation (the intro paragraph describing what Shoprocket is for small businesses), sitting just below the fully lean 5 anchor.

4 / 5

Actionability

Concrete, copy-paste-ready commands appear throughout (login, connection ensure, action run, request proxy with flag table); it falls short of 5 because most examples rely on placeholders (CONNECTION_ID, actionId) with no fully worked end-to-end example.

4 / 5

Workflow Clarity

The connection flow is explicitly sequenced with state-based branching and polling checkpoints (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but it lacks an explicit error-recovery loop for action-run failures, keeping it below 5.

4 / 5

Progressive Disclosure

A single, well-sectioned SKILL.md with clear headers and no nested or broken references; with no bundle files present this is good structure, though the proxy/action sections run long enough inline to keep it just under 5.

4 / 5

Total

16

/

20

Passed

Description

62%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 includes an explicit 'Use when' trigger and names a specific platform, satisfying both what and when. It is held back by thin, slightly inaccurate capability listing ("Manage Organizations" only) and generic trigger phrasing.

Suggestions

Replace "Manage Organizations" with the full concrete action set the skill supports (e.g. manage Products, Orders, Customers, Discounts, Shipping) to lift specificity.

Tighten the trigger with natural user phrases, e.g. "Use when the user wants to list or manage Shoprocket orders, products, or customers".

Ensure the description's claimed capabilities match the body's actual entity list to avoid under-coverage.

DimensionReasoningScore

Specificity

"Manage Organizations" names the domain plus one concrete action, matching the 'names domain and 1-2 concrete actions' anchor; it is not a 4 because coverage is thin and the action understates what the body actually supports.

3 / 5

Completeness

It states both what ("Shoprocket integration. Manage Organizations.") and an explicit when ("Use when the user wants to interact with Shoprocket data"), but the when is generic so it does not reach the fully concrete 5 anchor.

4 / 5

Trigger Term Quality

Terms like "Shoprocket" and "interact with Shoprocket data" are relevant but few and not the natural phrases a user would say (e.g. "list my orders"), missing common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

Naming the specific Shoprocket platform gives a clear niche with low conflict risk, but the broad trigger "interact with Shoprocket data" leaves minor overlap risk versus a hypothetical 5.

4 / 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.

Validation15 / 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
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.