CtrlK
BlogDocsLog inGet started
Tessl Logo

faspay

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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

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

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 delivers actionable, well-structured CLI guidance with a solid connection-state workflow. Main weaknesses are mild verbosity from the introductory paragraph and duplicated action-discovery sections.

Suggestions

Trim or remove the opening paragraph explaining what Faspay is; Claude can infer domain context and the official-docs link already covers it.

Merge 'Searching for actions' and 'Popular actions' into one section to remove the duplicated `membrane action list --intent=QUERY` example.

Fix the dangling 'skip to Step 2' reference by labeling the next step explicitly or rewording to 'skip to Running actions below'.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the opening paragraph over-explains what Faspay is and the 'Searching for actions' and 'Popular actions' sections duplicate the same `membrane action list --intent=QUERY` guidance.

3 / 5

Actionability

It provides concrete, executable commands throughout (install, login, connection ensure, action run, request) plus a flags table, with only minor placeholder gaps like CONNECTION_ID.

4 / 5

Workflow Clarity

The install→authenticate→connect→poll sequence is clear with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED), but the dangling 'skip to Step 2' reference is a minor sequencing gap.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no need for external references, though the duplicated action-list sections and ~140-line length leave minor organization gaps.

4 / 5

Total

15

/

20

Passed

Description

48%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 pairs an explicit trigger clause with a named niche, but its capability statement is generic and lacks concrete Faspay actions. Tightening the 'what' with specific operations would lift completeness and specificity.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete Faspay operations, e.g. 'Create payouts, query transactions, and manage merchants via the Faspay gateway.'

Add natural trigger variations such as 'payment gateway', 'Indonesian payments', or 'Faspay transactions' so users phrasing it differently still match.

Keep the existing 'Use when...' clause but tie it to concrete intents, e.g. 'Use when the user wants to process payments or query Faspay transactions.'

DimensionReasoningScore

Specificity

It names the Faspay domain but the actions are minimal and generic ('Manage data, records, and automate workflows') rather than concrete capabilities like creating payouts or querying transactions.

2 / 5

Completeness

An explicit 'Use when the user wants to interact with Faspay data' clause provides the 'when', but the 'what' ('Manage data, records, and automate workflows') is too vague to be a clear statement of capability.

3 / 5

Trigger Term Quality

It surfaces 'Faspay' and 'Faspay data' as triggers, but offers no common variations, synonyms, or concrete task terms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The Faspay brand name gives it a distinct niche with minimal conflict risk, though the generic action verbs ('manage data, records') leave minor overlap with broad data skills.

4 / 5

Total

12

/

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.