Name: moneyhub-enterprise
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

moneyhub-enterprise

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

Quality

63%

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/moneyhub-enterprise/SKILL.md

Quality

Content

65%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 and token-efficient, dominated by executable Membrane CLI commands and a clear options table. Its main weaknesses are inconsistent workflow sequencing with missing validation checkpoints for risky operations and a monolithic structure with no external reference files to split out detailed material.

Suggestions

Make the multi-step connection workflow explicit and numbered (Step 1 ensure -> Step 1b wait/poll -> Step 2 search actions -> Step 3 run), with a validation checkpoint confirming state is READY before proceeding.

Add an explicit validate/verify step before running batch or destructive actions (e.g., confirm the discovered actionId and inputSchema match intent before `action run`).

Move the proxy options table and detailed clientAction field reference into a separate reference file, signaling it from SKILL.md to reduce inline bulk.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable CLI commands and minimal padding, though the opening paragraph explaining what Moneyhub Enterprise is and who uses it is unnecessary context Claude doesn't need, fitting the 'efficient; minor instances of over-explanation' anchor.	4 / 5
Actionability	It provides concrete, copy-pasteable `membrane` commands with flags and a clear options table, but some examples use placeholders like CONNECTION_ID and <actionId> without showing how to obtain them inline, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connection setup is sequenced with state checks and polling, but the document mixes 'Step 2' references without a defined step 1/2 sequence, and action-running workflows lack validation checkpoints, matching 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	There is reasonable section structure, but all content is inlined in SKILL.md with no external reference files to offload the API/options detail, and section ordering is slightly inconsistent (e.g., 'Popular actions' before 'Running actions'), fitting 'some structure but could be better organized'.	3 / 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 clearly identifies the target product and includes an explicit 'Use when' clause, giving it solid completeness and distinctiveness. Its weakness is generic action verbs and a lack of natural trigger-term variations, which keeps specificity and trigger-term quality at the middle of the scale.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with specific actions users perform (e.g., 'list accounts, fetch transactions, create payment requests').

Add natural user phrases and synonyms to the trigger clause (e.g., 'Use when the user mentions Moneyhub connections, transactions, or payment requests').

Dimension	Reasoning	Score
Specificity	It names the domain ('Moneyhub Enterprise') and a couple of concrete actions ('Manage data, records, and automate workflows'), but the verbs are generic rather than comprehensive, matching the 'names domain and 1-2 concrete actions' anchor.	3 / 5
Completeness	It states a clear 'what' (manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Moneyhub Enterprise data'), but the trigger phrase is somewhat generic, fitting the 'has both what and when; when could be more explicit' anchor.	4 / 5
Trigger Term Quality	'Moneyhub Enterprise data', 'records', and 'workflows' are relevant keywords but it lacks common user synonyms or variations, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Moneyhub Enterprise brand name gives it a clear niche with minimal overlap risk, though 'manage data, records, automate workflows' is broad enough to risk minor overlap with generic data skills, fitting the 'mostly distinct; minor overlap risk' anchor.	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/moneyhub-enterprise/SKILL.md
Commit: f484c82

Reviewed: 5 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.