Name: tellmoney
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

tellmoney

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

61%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 highly actionable with executable Membrane CLI commands and a good connection-state feedback loop, but it is held back by command duplication, a 'Popular actions' section that does not list actions, and missing validation for destructive payment operations.

Suggestions

Add a validation/confirmation checkpoint before running destructive or batch actions (e.g. payment orders, proxy POST/PUT/DELETE) — show the parsed input and confirm with the user before executing.

De-duplicate the `membrane action list` instructions: keep one canonical 'Discover actions' section and have 'Popular actions' actually list common Tell.money actions (list balances, fetch counterparties, create payment order) instead of repeating the discovery command.

Trim the opening 'Tell.money is a financial data aggregation platform...' paragraph and the auth-plumbing commentary; assume Claude's competence and lead with the integration steps.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but it repeats the `membrane action list` command across 'Searching for actions', 'Popular actions', and the 'Discover before you build' best practice, and the opening paragraph explains what Tell.money is — tightening would remove these redundancies.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure, polling, action run, and proxy with a full flag table; the gap is the 'Popular actions' section, which repeats the discovery command instead of listing actual popular actions.	4 / 5
Workflow Clarity	The connection flow has an explicit state feedback loop (BUILDING → READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but the skill covers destructive financial operations (Payment Orders) and proxy POSTs with no validation/verification checkpoint before execution, which caps workflow clarity per the destructive-operations rule.	3 / 5
Progressive Disclosure	Single-file skill (no references/scripts/assets) organized into clear, well-labeled sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references; the detailed clientAction state machine and proxy flag table are inlined rather than split out, leaving a minor organization gap.	4 / 5
	Total	14 / 20 Passed

Description

62%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 is third-person, names a specific platform, and includes an explicit 'Use when...' trigger, but its action verbs are generic and it lacks concrete trigger synonyms. It is solid but not exemplary.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete operations a user would request, e.g. 'List account balances, fetch counterparties, create and submit payment orders and payment requests'.

Broaden the trigger with natural user phrasings and file/extension-style synonyms, e.g. 'Use when the user asks to query Tell.money accounts, balances, counterparties, or payment orders'.

Make the 'when' clause enumerate the concrete entities from the body (Account/Balance, Counterparty, Payment Request, Payment Order) so the trigger is specific rather than 'interact with Tell.money data'.

Dimension	Reasoning	Score
Specificity	Names the domain and several action phrases ('Manage data, records, and automate workflows'), but the verbs are generic ('manage', 'automate') rather than concrete operations, so it sits at the 'names domain and 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	Has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' clause ('Use when the user wants to interact with Tell.money data'), but the trigger is somewhat narrow/generic rather than concrete trigger phrases, so it is above the no-when cap but below the fully-explicit anchor.	4 / 5
Trigger Term Quality	Includes the specific app name 'Tell.money' plus 'data', 'records', 'workflows', but lacks common user synonyms and natural phrasing variations, matching 'some relevant keywords but missing common variations or synonyms.'	3 / 5
Distinctiveness Conflict Risk	Binding to the specific named platform 'Tell.money' gives it a clear niche with minimal conflict risk, though the generic action verbs ('manage data') leave minor overlap risk with adjacent integration skills.	4 / 5
	Total	14 / 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/tellmoney/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.