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

paycaptain

PayCaptain integration. Manage data, records, and automate workflows. Use when the user wants to interact with PayCaptain 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/paycaptain/SKILL.md

Quality

Content

75%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 a strongly actionable, well-sequenced CLI guide with explicit connection-state checkpoints, scoring high on actionability and workflow clarity. Its main weaknesses are mild verbosity (a marketing intro and a duplicated action-list example) and a missing "Step 2" anchor that breaks the step numbering.

Suggestions

Remove the marketing-style opening paragraph ("helps employees manage their finances...") or trim it to a single line; Claude does not need the business rationale.

Deduplicate the action-list example: keep it in one place ("Searching for actions" or "Popular actions") rather than repeating near-identical commands in both sections.

Fix the dangling "skip to Step 2" references by either labeling the subsequent sections as numbered steps or removing the Step 2 phrasing.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete commands, but the opening marketing paragraph ("helps employees manage their finances and get paid flexibly") and the duplicated action-list example in both "Searching for actions" and "Popular actions" are unnecessary padding. It is not a 4 because the redundancy is more than minor, and not a 2 because the bulk is genuinely useful command reference.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every step (install, login, connection ensure, polling, action list/run, request) plus a proxy flag table, covering the common cases. Placeholders like CONNECTION_ID are necessary and not penalized, matching the anchor-5 example.	5 / 5
Workflow Clarity	The install → login → connect → poll-state → search → run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR). It is not a 5 because of a dangling "Step 2" reference with no matching header and no validation checkpoint around running potentially destructive actions (payments/deductions).	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, and all guidance is one cohesive CLI guide. It is not a 5 because at ~140 lines the detailed clientAction breakdown and proxy-options table could be split into reference files, and not a 3 because the structure is genuinely good.	4 / 5
	Total	16 / 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 identifies the named PayCaptain niche and includes an explicit Use-when clause, but its capability list is generic ("data, records, workflows") and it lacks the natural domain keywords (payroll, payslips, pay runs) that would sharpen triggering. Distinctiveness is strong thanks to the product-specific naming.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete PayCaptain actions (e.g., "Run payroll, manage employee records, fetch payslips, and apply deductions").

Expand the Use-when clause to list natural trigger terms users would actually say ("Use when the user wants to run payroll, view payslips, manage employees, or query PayCaptain").

Add file-extension or entity keywords (pay runs, payslips, deductions, payments) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the PayCaptain domain plus a few actions, but the actions are generic rather than concrete. It is not a 2 because it lists multiple actions, and not a 4 because it omits the specific capabilities the body covers (payslips, pay runs, deductions).	3 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with PayCaptain data"). It is not a 5 because the what/when are generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"interact with PayCaptain data" is a natural trigger phrase, but the description misses common synonyms users would say (payroll, payslips, pay runs, employees). It is not a 4 because the keyword coverage is thin on natural variations.	3 / 5
Distinctiveness Conflict Risk	"PayCaptain" is a specific named application, giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	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/paycaptain/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.