Name: paylocity
Rating: 58.4 (1 reviews)
Author: membranedev

paylocity

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

Quality

67%

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/paylocity/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 copy-paste CLI commands and a strong connection-state workflow, but it over-explains the product upfront, inlines a large actions table, and lacks validation guidance for the destructive actions it exposes.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. 'For Delete Earning or Update Employee, confirm the target employee ID and review the inputSchema before running').

Trim the introductory paragraph explaining what Paylocity is; Claude can treat it as a known SaaS product and jump straight to the CLI workflow.

Move the 16-row 'Popular actions' table to a references/popular-actions.md and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and tables, but opens with an unnecessary explanation of what Paylocity is ('Paylocity is a cloud-based payroll and human capital management (HCM) software. It's used by businesses of all sizes...') and includes mild padding ('so you can focus on the integration logic rather than auth plumbing'), matching 'mostly efficient but includes some unnecessary explanation or could be tightened.'	3 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case — install (`npm install -g @membranehq/cli@latest`), auth, `membrane connection ensure`, `membrane action list/run`, and `membrane request` with flag tables — covering the common cases fully, matching the score-5 anchor.	5 / 5
Workflow Clarity	The connect-to-ready flow is well sequenced with explicit state checkpoints and a re-poll feedback loop, but the 'Running actions' workflow invokes destructive operations (Delete Earning, Update Employee, Create Employee) with no validation or confirmation step, triggering the rubric's destructive-operations cap at 3.	3 / 5
Progressive Disclosure	The body is organized into clear, well-signaled sections (Overview, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, but the 16-row 'Popular actions' table is a sizable inlined chunk that could live in a separate reference file — a minor organization gap matching score 4.	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 correctly answers both what the skill does and when to use it, anchored by a highly distinctive product name. Its main weakness is generic action verbs and a narrow trigger clause that omits natural payroll/HR synonyms users would actually say.

Suggestions

Replace generic verbs with concrete Paylocity actions, e.g. 'Manage employee records, run payroll, pull pay statements, and submit time-off requests.'

Expand the trigger clause with natural terms: 'Use when the user wants to work with Paylocity payroll, HR data, employees, paychecks, or time-off requests.'

Keep the third-person voice but add 1-2 specific capabilities (e.g. pay statements, local taxes) to lift specificity toward a 4-5.

Dimension	Reasoning	Score
Specificity	The description names the Paylocity domain and several actions ('Manage data, records, and automate workflows'), but those actions are generic and abstract rather than concrete, fitting the 'names domain and 1-2 concrete actions but not comprehensive' anchor and falling short of the specific-action coverage of score 4.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Paylocity data') are present, but the 'when' is generic rather than listing concrete trigger phrases, matching the score-4 anchor and stopping short of the explicit multi-trigger 'when' required for a 5.	4 / 5
Trigger Term Quality	It includes the natural product keyword 'Paylocity' in the trigger clause ('Use when the user wants to interact with Paylocity data'), but misses common synonyms a user would actually say like payroll, HR, employees, paychecks, or time-off, matching 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	The named product 'Paylocity' creates a clear, distinct niche with minimal conflict risk against other skills, matching 'clear niche with distinct triggers; minimal conflict risk'; it is more distinctive than the score-4 'minor overlap risk with closely related skills' anchor.	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/paylocity/SKILL.md
Commit: f484c82

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