CtrlK
BlogDocsLog inGet started
Tessl Logo

processout

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

60

Quality

70%

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/processout/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 executable CLI commands and a sensible validated connection workflow, held back only by an unnecessary introductory explainer and slightly loose step numbering.

Suggestions

Trim the opening 'ProcessOut is a payment orchestration platform...' paragraph and the 'so you can focus on the integration logic' aside to respect the token budget.

Reconcile the step numbering: either label 'Searching for actions' explicitly as Step 2 or remove the 'skip to Step 2' forward references.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste commands, but the opening paragraph explaining what ProcessOut is ('a payment orchestration platform that helps online businesses...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding Claude does not need.

3 / 5

Actionability

Every section gives fully executable, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) with concrete flag examples and a parameter table covering the common cases.

5 / 5

Workflow Clarity

There is a clear install→auth→connect→poll sequence with validation via connection state polling and a retry loop ('poll again... to check if the state moved to READY'), but the step numbering is loose ('skip to Step 2' references a section that is not explicitly labeled Step 2).

4 / 5

Progressive Disclosure

With no bundle files present, the single SKILL.md is well-organized into clearly headed sections (Overview, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) making navigation easy with no nested references.

5 / 5

Total

17

/

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 has an explicit use-when clause and is highly distinct thanks to the named platform, but its capability list is generic and it misses the payment-specific trigger terms users would naturally say.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete ProcessOut actions such as 'route transactions, manage customers and gateways, configure webhooks, and monitor payment performance'.

Add natural trigger terms like 'payments', 'payment orchestration', 'transactions', or 'gateways' alongside 'ProcessOut'.

Tighten the 'when' clause to reference payment-specific scenarios, e.g. 'Use when the user wants to manage ProcessOut payments, gateways, customers, or webhooks'.

DimensionReasoningScore

Specificity

The description names ProcessOut but its actions ('Manage data, records, and automate workflows') are generic and never mention payments, customers, gateways, or transactions that the body reveals as the real capabilities.

2 / 5

Completeness

Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with ProcessOut data') are present, though the 'what' is vague rather than concrete.

4 / 5

Trigger Term Quality

It surfaces the product name 'ProcessOut' and 'ProcessOut data' but omits natural synonyms a user would say such as 'payments', 'transactions', 'gateways', or 'webhooks'.

3 / 5

Distinctiveness Conflict Risk

The named platform 'ProcessOut' with a specific trigger ('interact with ProcessOut data') carves out a clear niche with minimal overlap against other skills.

5 / 5

Total

14

/

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.