Name: truelayer
Rating: 52 (1 reviews)
Author: membranedev

truelayer

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

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/truelayer/SKILL.md

Quality

Content

75%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 executable Membrane CLI commands and a well-sequenced connection workflow including state-handling branches. The main gaps are some unnecessary background explanation, a duplicated action-list command, and the absence of verification steps before reporting action or proxy results.

Suggestions

Trim the opening 'TrueLayer is a platform that provides secure access to banking APIs...' paragraph, which explains concepts Claude already knows.

Remove the duplicated action-list command in 'Popular actions' (already shown in 'Searching for actions') or repurpose that section into distinct examples.

Add a brief verification/feedback step after running actions or proxy requests (e.g. check the output/error field and retry or report) to strengthen workflow clarity for potentially destructive or batch operations.

Dimension	Reasoning	Score
Conciseness	Most sections are efficient with copy-pasteable commands, but the opening paragraph explains what TrueLayer is and why businesses use it — concepts Claude already knows — and the 'Popular actions' section repeats the same action-list command shown two sections earlier, adding padding.	3 / 5
Actionability	Nearly every instruction is a complete, executable shell command with concrete flags and JSON examples, covering login, connection ensure/poll, action list/run with input, and proxy requests with a full flag table — copy-paste ready for the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced (ensure → poll → handle READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR → proceed to Step 2) with an explicit polling loop, though there is no validation/verification step after running actions or proxy requests before reporting results to the user.	4 / 5
Progressive Disclosure	The body is well-organized under clear headers (Install, Authentication, Connecting, Searching, Running actions, Proxy, Best practices) with no bundle files, so one-level structure is appropriate; minor overlap between 'Searching for actions' and 'Popular actions' keeps it just short of fully clean.	4 / 5
	Total	16 / 20 Passed

Description

41%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 correctly identifies a distinct niche (TrueLayer) with an explicit use-trigger, but its stated capabilities are generic ('Manage data, records, and automate workflows') rather than the concrete banking/payments actions TrueLayer actually exposes. Tightening the capability list to specific TrueLayer features would lift specificity and trigger-term quality.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete TrueLayer actions, e.g. 'Initiate payments, manage beneficiaries, and retrieve account and transaction data'.

Add natural trigger terms a user would actually say, such as 'payments', 'payouts', 'bank account access', or 'Open Banking / TrueLayer API'.

Strengthen the 'what' to clearly answer what the skill does in one concrete clause before the 'Use when...' trigger.

Dimension	Reasoning	Score
Specificity	It names the domain (TrueLayer integration) but the only actions are generic 'Manage data, records, and automate workflows' — no concrete TrueLayer capabilities such as payments, beneficiaries, or account verification are stated.	2 / 5
Completeness	It gives a vague 'what' and an explicit 'Use when the user wants to interact with TrueLayer data' trigger, but the 'what' is so generic that completeness is only weakly satisfied rather than clear.	3 / 5
Trigger Term Quality	The only natural user-facing term is 'TrueLayer' itself; 'data, records, and automate workflows' are generic phrases a user would rarely say, and no synonyms or banking/payments vocabulary appear.	2 / 5
Distinctiveness Conflict Risk	The 'TrueLayer' name and 'Use when the user wants to interact with TrueLayer data' trigger pin a clear niche that is unlikely to fire for unrelated skills, though the generic 'data/records/workflows' wording slightly weakens it.	4 / 5
	Total	11 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/truelayer/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.