Name: sage-payroll
Rating: 55.2 (1 reviews)
Author: membranedev

sage-payroll

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

Quality

63%

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/sage-payroll/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 content is highly actionable with concrete, copy-paste-ready CLI commands and a well-structured connection flow. It is held back by an unnecessary product-intro paragraph, missing validation around destructive proxy/action calls, and a redundant actions section.

Suggestions

Remove or trim the opening paragraph that explains what Sage Payroll is and who uses it; Claude can infer product context and it pads the token budget.

Add validation/verification guidance before destructive proxy or action calls (e.g., GET-before-write or a dry-run check for POST/PUT/DELETE) — destructive operations without validation cap workflow clarity at 3.

Merge the redundant 'Popular actions' section into 'Searching for actions' to remove the duplicated `action list` command.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI reference, but the opening paragraph explaining what Sage Payroll is and who uses it ('cloud-based payroll management software... primarily used by small to medium-sized businesses') is concept padding Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every common operation — install, login, connection ensure/get, action list/run, and request — with clearly marked placeholders, matching the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The connection flow has good state-based branching and polling feedback loops, but the proxy and action-run sections permit destructive methods (POST/PUT/DELETE) with no validation or verification guidance, and the rubric caps workflow clarity at 3 for destructive/batch operations lacking validation.	3 / 5
Progressive Disclosure	No bundle files exist and the single file is well-organized into clear section headers with no nested references, but the redundant 'Popular actions' section and the inlined proxy-flags reference table leave minor organization gaps short of the 5 anchor.	4 / 5
	Total	15 / 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 includes an explicit 'Use when' trigger and is clearly anchored to a specific product, giving it solid completeness and distinctiveness. Its main weakness is generic action language and a narrow set of trigger terms that lean entirely on the product name.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions users perform, e.g. 'run pay runs, pull employee records, generate payroll reports'.

Add natural payroll-domain trigger terms users would actually say — 'payroll', 'pay runs', 'payslips', 'employees' — instead of relying solely on the product name 'Sage Payroll'.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Sage Payroll integration') but its actions are generic verbs — 'Manage data, records, and automate workflows' — rather than concrete operations like running payruns or pulling employee records, matching the 'actions are minimal or generic' anchor.	2 / 5
Completeness	It answers both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Sage Payroll data'), but the when is a single generic phrase rather than multiple concrete trigger phrases, so it falls short of the 5 anchor.	4 / 5
Trigger Term Quality	The only natural keyword is the product name 'Sage Payroll', repeated in 'interact with Sage Payroll data'; it misses common payroll-domain variations users would actually say (payroll, pay runs, payslips, employees), fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific named product 'Sage Payroll' gives it a clear niche with minimal conflict risk, though the generic action wording leaves minor overlap with other accounting/payroll integrations, placing it just below the 5 anchor.	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/sage-payroll/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.