Name: payfit
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

payfit

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

Quality

70%

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

Quality

Content

67%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 CLI commands and a clear connection-readiness workflow, but it spends tokens explaining PayFit and Membrane concepts Claude already knows and never shows a concrete PayFit action example. Structure is clean, though denser sections could be split into references.

Suggestions

Cut the opening "PayFit is a SaaS platform..." paragraph and the filler "Use action names and parameters as needed." line; Claude does not need PayFit explained.

Add at least one concrete PayFit action example with a real actionId and a sample --input JSON payload so the guidance is fully copy-paste ready.

Label the referenced "Step 2" explicitly (e.g. a numbered "### 2. Search for actions" header) so the forward references resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and flags, but opens by explaining what PayFit is ("PayFit is a SaaS platform that automates payroll and HR management...") and includes filler like the bare "Use action names and parameters as needed." line, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run, request proxy) plus a flag table, matching score 4; it stops short of 5 because no real PayFit-specific actionId or input JSON example with actual PayFit fields is shown, only generic placeholders.	4 / 5
Workflow Clarity	The install → auth → connect → search → run → proxy sequence is clear, and the connection state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with re-polling forms a real feedback loop, matching score 4; it is not 5 because "Step 2" is referenced but never labeled, and there is no validation step after running an action.	4 / 5
Progressive Disclosure	The content is well-organized into clear section headers with no broken or deeply nested references and no bundle files, matching the score-4 anchor of good structure; it is not 5 because at ~140 lines all content is inline with no signaled one-level-deep references for the denser material (proxy flags, clientAction handling).	4 / 5
	Total	15 / 20 Passed

Description

73%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 clearly identifies its niche (PayFit) and includes an explicit "Use when..." trigger, but the capability list ("manage data, records, automate workflows") is generic rather than concrete. It is strong on distinctiveness and completeness, weaker on specificity.

Suggestions

Replace generic verbs with concrete PayFit capabilities, e.g. "Manage employee records, time-off requests, and payslips; automate payroll and HR workflows."

Add a few natural trigger synonyms users might say, such as "PayFit", "payroll", "payslips", or "time off", to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Manage data, records, and automate workflows" names the PayFit domain plus a couple of actions, but those actions are generic ("manage data, records") rather than concrete like "extract text, fill forms", fitting the score-3 anchor and falling below score 4 which requires several specific actions.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with PayFit data") are present and explicit, matching the score-4 anchor; it is not a 5 because the "what" clause stays generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	"PayFit", "PayFit data", "records", and "automate workflows" are natural terms a user would say, giving good keyword coverage; it stops short of score 5 only because there is little synonym/variation breadth for a single named SaaS.	4 / 5
Distinctiveness Conflict Risk	"PayFit integration" targets a single named SaaS with distinct triggers ("PayFit", "PayFit data"), giving it a clear niche with minimal conflict risk, matching the score-5 anchor.	5 / 5
	Total	16 / 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/payfit/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.