CtrlK
BlogDocsLog inGet started
Tessl Logo

interswitch-group

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

51

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/interswitch-group/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 solid, actionable guide with concrete CLI commands, an explicit auth/connection state machine, and a polling feedback loop. It loses points for some company-background padding, a duplicated search/actions section, and the absence of any external reference files despite a structure that implies deeper material.

Suggestions

Remove the company-background paragraph and trim explanatory prose that Claude can infer, to tighten token efficiency.

Consolidate the duplicate 'Searching for actions' and 'Popular actions' sections into a single clear block.

If detailed action catalogs exist, move them to a references file and link one level deep; otherwise drop the implication of external material.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but it explains things Claude largely knows (a company background paragraph, what 'Discover before you build' means at length) and could be tightened.

3 / 5

Actionability

It provides mostly executable, copy-paste-ready CLI commands for install, login, connection ensure, action list/run, and proxy requests, with only minor gaps (e.g. actionId and CONNECTION_ID placeholders are unexplained).

4 / 5

Workflow Clarity

It sequences install -> auth -> connection -> search -> run with explicit state-checking checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, missing only a final output-validation step.

4 / 5

Progressive Disclosure

Content is organized into headed sections but there are no external reference files (none exist in the bundle), and the 'Popular actions' section duplicates the earlier 'Searching for actions' guidance rather than splitting it out.

3 / 5

Total

14

/

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 identifies a specific niche (Interswitch Group) and includes a 'Use when' clause, but its stated actions are generic ('manage data, records, automate workflows') rather than concrete payment/transaction operations. Trigger terms are reasonable but lack payment-specific synonyms.

Suggestions

Replace generic verbs with concrete Interswitch-specific actions, e.g. 'process payments, create payment links, and query transactions'.

Add concrete trigger phrases users would say, such as 'when the user mentions Interswitch payments, payment links, or transaction records'.

Tighten 'interact with Interswitch Group data' to name the actual objects (payments, transactions) to improve distinctiveness.

DimensionReasoningScore

Specificity

It names the domain ('Interswitch Group integration') but only states generic actions ('Manage data, records, and automate workflows') rather than concrete operations like processing payments or listing transactions.

2 / 5

Completeness

It has a clear 'what' (Interswitch Group integration) and a 'Use when' clause, but the 'when' is generic ('interact with Interswitch Group data') rather than concrete trigger phrases, so it does not fully reach a 5.

3 / 5

Trigger Term Quality

It contains the natural phrase 'Use when the user wants to interact with Interswitch Group data' plus 'Interswitch Group', but misses common synonyms and payment-specific keywords a user would actually say.

3 / 5

Distinctiveness Conflict Risk

The 'Interswitch Group' trigger is niche and largely distinct, with only minor overlap risk against other generic data/records 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.