CtrlK
BlogDocsLog inGet started
Tessl Logo

apto-payments

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

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/apto-payments/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a well-structured, actionable guide with concrete CLI commands and a clear connection workflow, but it carries some unnecessary explanatory padding and lacks explicit validation checkpoints around action execution.

Suggestions

Add a validation step after running or proxying requests, e.g. checking the response state field and retrying on transient errors before proceeding.

Trim inferable explanations like 'This is the fastest way to get a connection' and the restatement of Membrane's auth handling to improve token efficiency.

Clarify that CONNECTION_ID placeholders must be replaced with the actual id returned from 'membrane connection ensure' to avoid copy-paste failures.

DimensionReasoningScore

Conciseness

The body is mostly efficient with command examples, but spends tokens explaining concepts Claude could infer (e.g. what 'Membrane handles authentication' means, restating that 'This is the fastest way to get a connection') and could be tightened.

3 / 5

Actionability

Provides concrete, copy-pasteable CLI commands with flags and JSON output for login, connection setup, action listing/running, and proxying, with only minor gaps like missing example CONNECTION_ID substitution guidance.

4 / 5

Workflow Clarity

The connection setup is sequenced with state polling and a branching decision tree, but operations that mutate or run actions lack explicit validation/checkpoint steps, so feedback loops for batch or destructive actions are implicit.

3 / 5

Progressive Disclosure

Content is organized into clear sections (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files, so the single-file structure is appropriate and well-signaled for a skill of this scope.

4 / 5

Total

14

/

20

Passed

Description

55%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 identifies a specific product niche and includes an explicit use-trigger, but the capability language ('Manage data, records, and automate workflows') is generic and lacks concrete Apto-specific actions or natural user trigger phrases.

Suggestions

Replace generic verbs with concrete Apto capabilities, e.g. 'Issue and manage branded payment cards, retrieve transactions, and manage funding sources and accounts.'

Add natural trigger phrases users would actually say, such as 'cards', 'payment programs', 'transactions', or 'funding source'.

Tighten the 'Use when' clause to reference Apto-specific scenarios (e.g. 'when the user wants to issue cards or query Apto transactions') rather than 'interact with Apto Payments data'.

DimensionReasoningScore

Specificity

Names the domain (Apto Payments integration) and a couple of generic actions ('Manage data, records, and automate workflows') but the actions are abstract rather than concrete Apto-specific operations like issuing cards or fetching transactions.

3 / 5

Completeness

It states what it does ('Manage data, records, and automate workflows') and an explicit 'Use when the user wants to interact with Apto Payments data' clause, satisfying both what and when, though the 'when' trigger is somewhat generic.

4 / 5

Trigger Term Quality

Beyond the product name 'Apto Payments' there are no natural user trigger phrases; 'interact with Apto Payments data' is generic and lacks synonyms users would naturally say.

2 / 5

Distinctiveness Conflict Risk

Naming a specific branded product ('Apto Payments') gives it a clear niche and low conflict risk with other skills, even though the surrounding action language is broad.

4 / 5

Total

13

/

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.