Name: treasury-prime
Rating: 48 (1 reviews)
Author: membranedev

treasury-prime

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

Quality

51%

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/treasury-prime/SKILL.md

Quality

Content

57%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 actionable with executable CLI commands and a recognizable workflow, but it carries unnecessary overview prose and omits validation checkpoints for risky banking operations. It is a single inlined file with no progressive-disclosure references.

Suggestions

Trim the introductory BaaS explanation and auth-plumbing prose that Claude can infer, keeping only the Membrane-specific operational facts.

Add explicit validation/checkpoint steps before running payment orders or proxy POST requests (e.g. confirm the connection is READY, dry-run or confirm destructive payment actions with the user, and a validate-fix-retry loop on CLIENT_ACTION_REQUIRED).

Move the proxy flags reference and best-practices detail into a separate reference file (e.g. REFERENCE.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some padding Claude does not need (the opening 'Treasury Prime is a banking-as-a-service platform...' overview and explanatory prose around the connection lifecycle), so it could be tightened.	3 / 5
Actionability	It provides concrete, copy-pasteable CLI commands for install, login, connection, action listing/running, and proxy requests with a clear flags table, with only minor gaps (e.g. placeholders CONNECTION_ID and <agentType> left abstract).	4 / 5
Workflow Clarity	A clear sequence (install → authenticate → connect → search/run actions → proxy) is present with state-based polling for connections, but there is no validation/verification step before executing actions or proxy requests against live banking data, and batch/destructive operations lack a validate-fix-retry loop.	3 / 5
Progressive Disclosure	Structure is reasonable with section headers and an overview, but all content is inlined in SKILL.md with no bundle files or one-level-deep references; the API/proxy details and best practices could live in separate reference files.	3 / 5
	Total	13 / 20 Passed

Description

46%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 names the Treasury Prime domain and includes a usable 'Use when' clause, but its action list is generic and its trigger phrasing is narrow. It is distinguishable mainly by the platform name rather than by concrete capabilities.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete Treasury Prime operations such as creating payment orders, listing transactions, managing counterparties, and retrieving account balances.

Broaden the trigger phrase to natural variations users would say, e.g. 'Use when the user wants to send payments, query transactions, or manage banking records in Treasury Prime'.

Tie the 'Use when' clause to specific trigger terms (payment orders, wires, counterparties, account balances) to reduce overlap with other data-integration skills.

Dimension	Reasoning	Score
Specificity	It names the domain (Treasury Prime integration) and lists only minimal generic actions — 'Manage data, records, and automate workflows' — with no concrete banking-specific operations, matching the 'names domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Treasury Prime data'), but the 'when' is generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural trigger phrase is essentially 'interact with Treasury Prime data', a single generic phrasing that lacks the variations or synonyms a user would naturally say; no file extensions or alternative terms are present.	2 / 5
Distinctiveness Conflict Risk	Naming the specific Treasury Prime platform gives it a niche, but the generic 'Manage data, records, and automate workflows' could overlap with other data-integration skills, so it is only somewhat specific.	3 / 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/treasury-prime/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.