Tessl • The management layer for AI agent skills

SkillPublic

brightpay-uk

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

Quality

71%

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

68%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 delivers strong executable guidance — every Membrane command needed to connect, discover, run actions, and proxy raw requests is concrete and copy-paste ready, with a reasonable connection-state polling loop. Its weaknesses are padded filler sections (an empty "Overview", a "Popular actions" section with no actions, an app-description intro) and incoherent step references (a dangling "Step 2", a lone "1b" heading) that blur the workflow. Trimming the filler and fixing the step numbering would raise it substantially.

Suggestions

Remove or fill the hollow sections: give "## Popular actions" real action examples for common payroll tasks (list employees, run payroll, submit HMRC report), and either drop the "BrightPay UK Overview" bullet skeleton or replace it with actual entity/action mapping.

Fix the incoherent step references: rename "#### 1b" to a proper step sequence and define an explicit "Step 2" (discover and run actions) so "skip to Step 2" resolves.

Trim known-concept padding — the intro paragraph describing what BrightPay is and the "Agent Types : claude, openclaw, codex..." line add tokens without adding guidance Claude needs.

Dimension	Reasoning	Score
Conciseness	Several sections are unnecessary padding: the opening paragraph explains what BrightPay is, "## BrightPay UK Overview" holds only hollow bullets (Employer/Employee/Payroll/Schedule plus "Use action names and parameters as needed."), "## Popular actions" lists no actions, and the "Agent Types : claude, openclaw, codex..." line is filler — going beyond the minor instances the anchor-4 example allows.	3 / 5
Actionability	The body is built from complete, copy-paste-ready commands covering the common cases — npm install, membrane login (including headless completion), connection ensure/wait, action list/run with JSON input, proxy usage — plus a full flag table and an explanation of where results appear ("The result is in the `output` field"), matching the fully-executable anchor.	5 / 5
Workflow Clarity	A real sequence exists (install → login → connect → poll state → discover actions → run) with a state-driven feedback loop for CLIENT_ACTION_REQUIRED and error states, but it is undermined by incoherent references — "skip to Step 2" points to a Step 2 that doesn't exist, and the only numbered section is "1b" with no 1a/2 — leaving checkpoints implicit rather than explicit.	3 / 5
Progressive Disclosure	It is a single-file skill with well-organized section headers, no nested references and no dead pointers to bundle files, and the CLI-usage content is appropriately sized for one SKILL.md; the filler sections and inconsistent numbering keep it below the clear, well-signaled top anchor.	4 / 5
	Total	15 / 20 Passed

Description

61%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 has an explicit and appropriately scoped trigger tied to the named app, but the capability statement is generic buzzword-level ("manage data, records, and automate workflows") with no concrete payroll actions and no payroll-domain trigger terms like payroll, HMRC, payslips, or employees. It would reliably fire for the right skill but undersells and under-describes what the skill actually does.

Suggestions

Replace the generic action list with concrete BrightPay operations, e.g. "Manage employers and employees, run payrolls and calculate deductions, and submit RTI/HMRC reports."

Add payroll-domain trigger terms users would naturally say — payroll, payslips, HMRC submissions, employee records — to the "Use when" clause so it fires on domain language, not just the product name.

State what the skill operates on concretely (e.g. employee and employer records, pay schedules) instead of the vague "interact with BrightPay UK data".

Dimension	Reasoning	Score
Specificity	The description names the domain ("BrightPay UK integration") but the actions are generic — "Manage data, records, and automate workflows" contains no concrete payroll operations such as calculating pay, filing HMRC reports, or managing employees/payslips, matching the anchor for minimal or generic actions.	2 / 5
Completeness	It has an explicit when-clause ("Use when the user wants to interact with BrightPay UK data") so the missing-trigger cap doesn't apply, and both what and when are present; however the "what" ("Manage data, records, and automate workflows") is vague, placing it between the anchor for a clear what/missing when and the anchor for both being explicit and concrete.	4 / 5
Trigger Term Quality	It includes the strong specific keyword "BrightPay UK" plus "data" and "records", but misses the natural payroll vocabulary users would actually say — "payroll", "payslips", "HMRC", "employees", "wages" — so keyword coverage has relevant terms but lacks common variations.	3 / 5
Distinctiveness Conflict Risk	It names a specific niche product ("BrightPay UK") twice and triggers only on interaction with that app's data, giving a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 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/brightpay-uk/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

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.

brightpay-uk

Table of Contents

Is this your skill?