Name: sage-people
Rating: 53.6 (1 reviews)
Author: membranedev

sage-people

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

Quality

60%

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

Quality

Content

57%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 action-oriented with concrete Membrane CLI commands and a well-handled connection-polling workflow. Weaknesses are verbosity in the intro, a dangling step reference, missing validation for destructive operations, and no progressive file disclosure.

Suggestions

Remove the introductory "Sage People is a cloud-based HR..." paragraph and the empty "Popular actions" section, or fold popular actions into the search section.

Add an explicit validation/verification checkpoint before destructive proxy calls (e.g. "For DELETE/PUT/PATCH, confirm the target id with the user before running") and resolve the dangling "Step 2" reference.

Move the detailed clientAction state reference and proxy flag table into a separate reference file linked from the relevant section to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly actionable commands, but the product-intro paragraph ("cloud-based HR... from recruitment to retirement") and the redundant "Popular actions" section that merely repeats the discovery command add padding that could be trimmed, fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, auth, connect, search, run, and proxy, plus a flag table, with only minor gaps such as no example of an actual action run with a real actionId, matching mostly-executable guidance with minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear polling/validation loop for BUILDING and CLIENT_ACTION_REQUIRED states, but a dangling "Step 2" reference and the absence of validation/verification for destructive proxy methods (DELETE/PUT/PATCH) and action runs trigger the destructive-ops cap at 3.	3 / 5
Progressive Disclosure	The skill is organized with clear section headers and no deep nesting, but at ~140 lines all reference-style content (the clientAction state reference, the proxy flag table) is inlined in SKILL.md with no separate-file split or signaled navigation, fitting the some-structure-but-could-be-better-organized anchor.	3 / 5
	Total	13 / 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 cleanly states what the skill does and when to use it with an explicit trigger clause, scoring well on completeness and distinctiveness. It is held back by generic action phrasing and missing natural HR-domain keywords.

Suggestions

Replace generic verbs with concrete HR actions, e.g. "manage employee records, approve time off, and run HR workflows".

Add natural trigger terms users say, such as "HR", "employee", "time off", or "payroll", alongside "Sage People data".

Broaden the "Use when" clause with concrete scenarios (e.g. querying employee records or submitting time-off requests) to reduce overlap with other Sage-family skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Sage People") and lists a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, matching the anchor for naming a domain with 1-2 non-comprehensive actions.	3 / 5
Completeness	It explicitly answers both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Sage People data"), but the trigger could be more specific with concrete scenarios, matching the has-both-but-when-could-be-more-explicit anchor.	4 / 5
Trigger Term Quality	It includes the natural brand term "Sage People" and "data"/"records", but omits common HR-domain variations users actually say (HR, employee, time off, payroll), fitting the anchor for some relevant keywords missing common synonyms.	3 / 5
Distinctiveness Conflict Risk	"Sage People" is a specific product niche with a distinct trigger, but the generic "interact with data" framing and possible overlap with other Sage-family skills leave minor conflict risk, fitting mostly-distinct with minor overlap.	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/sage-people/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.