Name: brightpay-uk
Rating: 52.8 (1 reviews)
Author: membranedev

brightpay-uk

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

Quality

59%

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

Quality

Content

61%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 well-structured, actionable guide to the Membrane CLI integration with concrete commands throughout. Its main weaknesses are redundancy between action-listing sections, a non-substantive overview, and missing verification checkpoints around destructive action/proxy execution.

Suggestions

Add a verification step before destructive proxy/action calls (e.g. dry-run or confirm the connection/action id) and a post-run check on the `output`/error fields, to lift workflow clarity above the destructive-operation cap.

Merge the 'Searching for actions' and 'Popular actions' sections to remove the duplicated `action list --intent=QUERY` example, or replace 'Popular actions' with an actual curated list of common BrightPay actions.

Cut or repurpose the skeletal 'Overview' bullet tree and the introductory paragraph explaining what BrightPay is, since that context is either thin or already known.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes redundancy (the 'Searching for actions' and 'Popular actions' sections repeat the same `action list --intent=QUERY` example) and a thin 'Overview' bullet tree plus prose explaining what BrightPay is, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests with a thorough flags table, matching 'mostly executable guidance; concrete code or commands with minor gaps'; the gaps are the placeholder-driven 'Popular actions' section and the vague 'Use action names and parameters as needed'.	4 / 5
Workflow Clarity	The connection workflow has a clear sequence with state-based checkpoints (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but running actions and proxy requests (which support POST/PUT/DELETE) lack any validation/verification step before or after destructive calls, so the destructive/batch cap holds at 3.	3 / 5
Progressive Disclosure	The single file is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and only a one-level external docs link, but the redundant 'Popular actions' section and the skeletal 'Overview' bullets are minor organization gaps, fitting 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly uses third-person voice and includes an explicit 'Use when' trigger, giving it solid completeness and distinctiveness. It is weakened by generic action language and missing natural payroll-specific trigger terms (payroll, payslips, HMRC, deductions).

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete payroll verbs such as 'run payroll, manage employees and deductions, and submit reports to HMRC'.

Add natural trigger terms users would say, e.g. 'Use when the user wants to run UK payroll, generate payslips, handle PAYE/NI deductions, or submit RTI/EPS reports to HMRC'.

Mention .bpx/data file handling or BrightPay Connect if those are meaningful triggers, to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('BrightPay UK integration') but the actions 'Manage data, records, and automate workflows' are generic rather than concrete payroll actions (no payroll, deductions, taxes, or HMRC submission specifics), matching the 'names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what ('Manage data, records, and automate workflows') and an explicit when ('Use when the user wants to interact with BrightPay UK data'), but the 'when' is generic rather than concrete trigger phrases, matching 'has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	'BrightPay UK' is a relevant natural keyword, but the description relies on generic terms ('data', 'records', 'workflows') and omits common natural payroll phrases users would say (payroll, payslips, HMRC, deductions), fitting 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product 'BrightPay UK' gives a clear niche with minimal conflict risk, but the generic action language ('manage data, records, automate workflows') creates minor overlap risk with other integration skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 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/brightpay-uk/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.