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

shopline

Shopline integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with Shopline data.

Quality

72%

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

Quality

Content

82%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 highly actionable with executable commands and a clear, validated connection workflow, and is well-structured for a single-file skill. It loses a little on conciseness to marketing-style phrasing and on workflow clarity to a dangling "Step 2" reference and missing destructive-action confirmation.

Suggestions

Trim the marketing-style phrasing around auth plumbing and the awkward agent-types sentence so every line earns its tokens.

Fix the step numbering: either label the connection subsections "Step 1"/"Step 2" consistently or remove the dangling "skip to Step 2" references.

Add a brief confirmation/validation note before destructive actions (e.g., verify a product ID before delete-product) to close the workflow-clarity gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands, but a few lines could be trimmed (the "focus on the integration logic rather than auth plumbing" phrasing, the awkward "adjust tooling to be used best with your harness", and the thin "Shopline Overview" stub).	4 / 5
Actionability	Copy-paste-ready bash commands cover install, login (including headless completion), connection ensure, polling, action search/run with JSON input, and proxy requests, with output fields explained and concrete action keys listed.	5 / 5
Workflow Clarity	The install→login→connect→poll→search→run sequence is clear with an explicit state-machine feedback loop (re-poll after CLIENT_ACTION_REQUIRED), but the dangling "Step 2" reference and the absence of any confirmation checkpoint for destructive actions like delete-product are minor gaps.	4 / 5
Progressive Disclosure	With no bundle files present, the single-file body is organized into clear, well-labeled sections with no nested references; the borderline-separable "Popular actions" table and the redundant overview stub are minor organization gaps rather than structural problems.	4 / 5
	Total	17 / 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 clearly identifies the Shopline niche and includes an explicit "Use when" trigger, but relies on one generic verb ("Manage") and lacks synonym coverage, leaving it solid but not exemplary. Voice is correctly third person.

Suggestions

Replace the single verb "Manage" with several distinct concrete actions (e.g., create, update, search, and retrieve records) to lift specificity.

Expand the trigger clause with natural synonyms users would say, such as "Shopline store, orders, customers, or e-commerce data".

Drop "and more" or replace it with the next concrete capability so coverage reads as comprehensive rather than open-ended.

Dimension	Reasoning	Score
Specificity	It names the domain and several concrete entities ("Persons, Organizations, Deals, Leads, Activities, Notes"), but the single generic verb "Manage" plus "and more" leaves the distinct actions thin rather than a comprehensive set of specific verbs.	3 / 5
Completeness	It answers both "what" ("Shopline integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more") and "when" ("Use when the user wants to interact with Shopline data"), with the "when" clause present but fairly generic.	4 / 5
Trigger Term Quality	The platform name "Shopline" and the phrase "interact with Shopline data" are relevant natural terms, but common variations and synonyms (store, orders, customers, e-commerce) are absent from the description.	3 / 5
Distinctiveness Conflict Risk	The named platform "Shopline" gives it a clear niche with a distinct trigger, with only minor overlap risk against generic e-commerce skills.	4 / 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/shopline/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.