Name: brightpearl
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

brightpearl

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

Quality

66%

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

Quality

Content

67%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 a strong, actionable CLI guide with a clear connection workflow and built-in state-handling checkpoints. Main weaknesses are an unnecessary marketing intro and a redundant 'Popular actions' section that adds little.

Suggestions

Remove the opening marketing paragraph about what Brightpearl is; keep only operationally relevant context.

Either populate 'Popular actions' with named, commonly-used actions or delete the section, since it currently just repeats the discovery command.

Tighten verbose phrasing like 'so you can focus on the integration logic rather than auth plumbing' to save tokens.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but opens with marketing-style context Claude doesn't need ('Brightpearl is a retail management system... streamline operations and improve efficiency') and a few padded phrasings.	3 / 5
Actionability	Provides concrete, executable CLI commands with real flags (install, login, connection ensure, action list/run, request proxy), with only minor gaps such as unresolved placeholders and a redundant 'Popular actions' section.	4 / 5
Workflow Clarity	Clear sequence from install → login → connect → search → run, with a polling feedback loop and state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR) that functions as validation checkpoints.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested or buried references; no bundle files exist, and the inline entity list is compact enough to stay in SKILL.md, leaving only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

66%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 target platform and includes an explicit 'Use when' trigger, making it distinct and reasonably complete. Weaknesses are the generic action verbs and limited natural-language trigger variation.

Suggestions

Replace generic verbs with concrete Brightpearl actions, e.g. 'create and update sales orders, sync inventory, manage contacts and products'.

Add natural trigger phrases users would say, such as 'Brightpearl orders, inventory, products, or accounting data'.

Tighten the 'when' clause to enumerate specific Brightpearl objects (orders, stock, customers) rather than only 'Brightpearl data'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Brightpearl integration') and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete (e.g. no 'create sales orders', 'sync inventory').	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Brightpearl data') are present and explicit, though the 'what' is somewhat generic and the 'when' could name specific triggers.	4 / 5
Trigger Term Quality	'Brightpearl' and 'Brightpearl data' are the primary natural triggers, but coverage lacks common synonyms or related phrases a user might say (e.g. 'orders', 'inventory', 'retail').	3 / 5
Distinctiveness Conflict Risk	'Brightpearl' is a specific named retail platform, giving the skill a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/brightpearl/SKILL.md
Commit: f484c82

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