CtrlK
BlogDocsLog inGet started
Tessl Logo

enable-banking

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

62

Quality

74%

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

Quality

Content

82%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 concrete Membrane CLI commands and a solid connection-state feedback loop, supported by clear section structure. Main weaknesses are minor prose padding and an incompletely labeled step sequence.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but includes light explanatory prose (e.g. the opening SaaS description and "focus on the integration logic rather than auth plumbing") that could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands throughout (login, connection ensure, action list/run, request) with documented flags and a proxy-options table, covering the common cases concretely.

5 / 5

Workflow Clarity

The connection setup has explicit state handling and feedback loops (poll until READY, act on CLIENT_ACTION_REQUIRED, inspect CONFIGURATION_ERROR), but "skip to Step 2" references an unlabeled Step 2 and the overall sequence is not cleanly numbered.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references, but it is a single ~140-line file with no bundle files; the proxy/action reference could be split out for a cleaner overview.

4 / 5

Total

17

/

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 answers both what and when in third person and is tied to a distinct named app, but its action list and trigger terms are generic rather than banking-specific. Tightening the actions to concrete banking verbs would lift specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete banking actions such as listing accounts, fetching transactions, and initiating payments.

Add natural trigger terms users would actually say, e.g. "banking data", "transactions", "payments", "accounts".

Make the "Use when" clause more specific, e.g. "Use when the user wants to query accounts, transactions, or initiate payments via Enable Banking."

DimensionReasoningScore

Specificity

It names the domain and a few actions ("Manage data, records, and automate workflows") but those actions are generic rather than banking-specific, so coverage is not comprehensive.

3 / 5

Completeness

Both a "what" (Enable Banking integration, manage data/records/workflows) and a "when" ("Use when the user wants to interact with Enable Banking data") are present, though the trigger is somewhat generic.

4 / 5

Trigger Term Quality

"Enable Banking" and "data" are relevant keywords, but common natural banking terms like payments, transactions, and accounts are missing, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

The Enable Banking domain and its "Use when...interact with Enable Banking data" trigger form a clear, named niche with minimal overlap risk against 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.