Name: paycor
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

paycor

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

Quality

61%

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/paycor/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 highly actionable with concrete Membrane CLI commands and a clear connection-state feedback loop, but it over-explains Paycor basics and lacks verification checkpoints before its destructive employee write operations.

Suggestions

Trim the opening HCM explainer and Membrane marketing prose so the skill starts with the install/auth workflow.

Add a verification/confirmation checkpoint before running write actions like create-employee or update-employee (e.g., confirm the legal entity and review the input payload before running).

Consider moving the Popular actions reference table into a separate references/ file linked from a short 'Popular actions' pointer, to keep the main workflow lean.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but it opens with an explanatory Paycor/HCM intro paragraph and includes marketing prose ('so you can focus on the integration logic rather than auth plumbing') and an auto-connector aside that could be trimmed, matching 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Concrete copy-paste commands cover the common cases (login, connection ensure, action list/run, request proxy) plus a Popular actions key table and proxy flag table, with only minor gaps like placeholders and no end-to-end worked example using a real action id.	4 / 5
Workflow Clarity	The install→auth→connect→search→run→proxy sequence is clear with a real connection-readiness feedback loop, but the skill includes destructive write actions (Create/Update Employee, Create Pay Rate) with no pre-write verification or confirm checkpoint, which caps workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Content is well-organized into clear, well-labeled sections with no nested references and no bundle files to navigate, though the 17-row Popular actions reference table is inlined rather than split to a dedicated reference file.	4 / 5
	Total	14 / 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 cleanly establishes Paycor as a distinct niche and includes an explicit 'Use when' trigger, but its capability list relies on generic verbs ('manage data, records, and automate workflows') rather than concrete Paycor actions.

Suggestions

Replace generic verbs with concrete Paycor actions, e.g. 'List employees and legal entities, fetch pay statements and tax forms, update employee records'.

Add natural trigger phrases a user would actually say, such as 'employee records', 'pay stubs', 'payroll data', or 'Paycor API'.

Tighten the 'when' clause to name concrete intents ('Use when the user wants to query Paycor employee, payroll, or time-off data').

Dimension	Reasoning	Score
Specificity	It names the Paycor domain, but the only actions ('Manage data, records, and automate workflows') are generic rather than concrete Paycor operations, matching the 'minimal or generic' anchor rather than the '1-2 concrete actions' level above.	2 / 5
Completeness	Both a 'what' (Paycor integration managing data/records/workflows) and an explicit 'Use when the user wants to interact with Paycor data' clause are present, but the trigger phrases are not concrete enough for anchor 5.	4 / 5
Trigger Term Quality	'Paycor' and 'Paycor data' are natural user terms, but coverage is thin and the remaining words (data, records, workflows) are generic with no synonyms or variations, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	'Paycor' is a specific named HCM product, giving a clear niche with a distinct trigger 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/paycor/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.