CtrlK
BlogDocsLog inGet started
Tessl Logo

modern-treasury

Modern Treasury integration. Manage Organizations. Use when the user wants to interact with Modern Treasury data.

56

Quality

64%

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/modern-treasury/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 is a solid, actionable guide to driving Modern Treasury through the Membrane CLI, with executable commands and a validated connection workflow. Its main weaknesses are verbosity (product intro and a long entity list) and slightly inconsistent workflow numbering rather than structural problems.

Suggestions

Trim the introductory paragraph explaining Modern Treasury and condense the entity bullet list (deduplicate "Balances") to respect token budget.

Fix the workflow numbering so "skip to Step 2" and the "1b" sub-step map to explicitly labeled steps in the sequence.

Add a brief verification note for action results, especially for payment-order creation, given the financial/destructive nature of those operations.

DimensionReasoningScore

Conciseness

The core CLI guidance is efficient, but the opening paragraph explaining what Modern Treasury is and the 20+ item entity bullet list (including a duplicated "Balances" entry) are padding that could be trimmed.

3 / 5

Actionability

It provides concrete, copy-paste-ready bash commands for install, login, connection, action search/run, and proxying with a clear flags table; minor gaps remain (e.g. the vague "Use action names and parameters as needed" and unmapped entity-to-action guidance).

4 / 5

Workflow Clarity

The connection lifecycle is clearly sequenced with state-based checkpoints and a poll-after-action feedback loop plus error-state handling; minor gaps include inconsistent step numbering ("1b" with no labeled "Step 2") and no result verification for run actions.

4 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections with no external bundle files present; the main gap is the inlined entity list that could be split out, keeping it just short of fully optimal structure.

4 / 5

Total

15

/

20

Passed

Description

61%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 pairs a what/when structure anchored to a distinctive named product, but its capability statement is too sparse and generic ("Manage Organizations") to convey the skill's true scope. Expanding the action list and adding natural trigger terms would meaningfully raise specificity and trigger-term quality.

Suggestions

Replace the generic "Manage Organizations" with concrete capabilities drawn from the body, e.g. "Manage payment orders, ledger accounts, counterparties, and balances."

Add natural trigger phrases users would say, such as "payments", "payment orders", "ledger", or "reconciliation", alongside "Modern Treasury".

Tighten the "when" clause to name the data types involved (e.g. "Use when the user wants to query or create Modern Treasury payments, ledgers, or counterparties").

DimensionReasoningScore

Specificity

The description names the domain ("Modern Treasury") but the only action stated is the generic "Manage Organizations", which is minimal and does not reflect the many capabilities (payments, ledgers, reconciliation) the body lists.

2 / 5

Completeness

It provides both a "what" ("Modern Treasury integration. Manage Organizations.") and an explicit "when" ("Use when the user wants to interact with Modern Treasury data"), though the "what" is thin and the "when" could be more specific.

4 / 5

Trigger Term Quality

It includes the strong natural product-name keyword "Modern Treasury" and the entity "Organizations", but misses common natural variations and synonyms a user would say (payments, payment orders, ledger, reconciliation).

3 / 5

Distinctiveness Conflict Risk

Naming the specific SaaS product "Modern Treasury" gives it a clear niche with distinct triggers and minimal risk of firing for an unrelated skill.

5 / 5

Total

14

/

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.