CtrlK
BlogDocsLog inGet started
Tessl Logo

payrexx

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

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/payrexx/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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-ready commands and a clear connection state-machine, but lacks validation/verification checkpoints for the destructive and proxy operations it enables.

Suggestions

Add a validation checkpoint before destructive actions (refunds, payouts, DELETE/PUT proxy calls), e.g. confirm parameters and verify the returned state/output before proceeding.

Populate the "Popular actions" section with a few concrete named actions and example invocations instead of pointing only to `action list`.

DimensionReasoningScore

Conciseness

Mostly efficient CLI commands with brief context; minor over-explanation in the intro paragraph ("Payrexx is an all-in-one platform...") and a few editorial phrases that could be trimmed.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action run with JSON input, proxy with a full flag table), with placeholders clearly marked.

5 / 5

Workflow Clarity

A clear install→auth→connect→search→run sequence with state-machine handling exists, but running actions and proxy requests (which support POST/PUT/DELETE) lack validation checkpoints, capping destructive/batch workflow clarity at 3.

3 / 5

Progressive Disclosure

A single well-organized SKILL.md with clear section headers and no nested references; appropriate for a CLI integration skill, though the thin "Popular actions" section is a minor gap.

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 is well-formed with explicit what/when structure and a distinct product trigger, but its actions and trigger terms are generic rather than tied to Payrexx's actual payment/subscription/invoice capabilities.

Suggestions

Replace generic actions with concrete Payrexx capabilities, e.g. "Create payment forms, process transactions and refunds, manage subscriptions and invoices".

Expand the trigger clause with natural user phrases, e.g. "Use when the user mentions Payrexx, payment forms, transactions, refunds, subscriptions, or invoices."

DimensionReasoningScore

Specificity

Names the Payrexx domain and lists actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete Payrexx capabilities like payments, refunds, or subscriptions.

3 / 5

Completeness

Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Payrexx data"), though the when-clause is generic rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes the product-name trigger ("Payrexx") and "interact with Payrexx data", but misses natural user synonyms (payments, payment forms, subscriptions, invoices, refunds) and file extensions.

3 / 5

Distinctiveness Conflict Risk

Names a specific product ("Payrexx integration") giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.