Name: prestashop
Rating: 59.2 (1 reviews)
Author: membranedev

prestashop

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

Quality

68%

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

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 highly actionable with executable commands and a sensible connection workflow including validation via state polling. Main weaknesses are minor padding, a wrong example URL, and an unlabeled 'Step 2' reference.

Suggestions

Fix the 'membrane connection ensure' example to use a PrestaShop URL instead of 'https://mixpanel.com/'.

Resolve the 'skip to Step 2' reference by either labeling Step 2 or rewording to 'skip to Running actions'.

Trim the introductory PrestaShop background paragraph and de-duplicate the action-list command to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with executable commands and a tidy flag table, though the opening 'open-source e-commerce platform... small to medium-sized businesses' paragraph and a duplicated action-list command add minor padding.	4 / 5
Actionability	Concrete, copy-paste-ready bash commands cover install, auth, connection, action discovery, running, and proxying; the placeholder 'CONNECTION_ID' and a stray 'mixpanel.com' example URL leave a small gap.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with state-based branching (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop; a referenced 'Step 2' is never labeled and the numbering drifts ('1b').	4 / 5
Progressive Disclosure	Sections are well-organized under clear headers in a single file with no nested references; the inlined 30-item entity list and full proxy-flag table are reference-like content that could be split out but are not severe.	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 follows good structure with third-person voice and an explicit 'Use when' trigger, but its action verbs are generic and it lacks synonym/extension coverage. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete PrestaShop operations, e.g. 'create and update products, manage orders and customers, sync inventory'.

Add natural trigger variations such as 'PrestaShop store', 'online shop', or 'PrestaShop API' to broaden keyword coverage.

Expand the 'Use when' clause with several concrete scenarios (e.g. managing catalogs, fulfilling orders, pulling sales reports).

Dimension	Reasoning	Score
Specificity	Names the domain ('Prestashop integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete PrestaShop operations like creating orders or syncing products.	3 / 5
Completeness	It states both what the skill does and an explicit 'Use when the user wants to interact with PrestaShop data' trigger, though the 'when' clause is a single phrase and could be more specific.	4 / 5
Trigger Term Quality	The keyword 'PrestaShop' appears but there are no common variations, synonyms, or natural phrases a user would say beyond 'interact with PrestaShop data'.	3 / 5
Distinctiveness Conflict Risk	'PrestaShop integration' carves out a clear niche with minimal overlap risk, but the generic action verbs ('manage data, records') slightly blunt the distinctiveness.	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/prestashop/SKILL.md
Commit: f484c82

Reviewed: 5 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.