Name: mambu
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mambu

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

Quality

68%

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

Quality

Content

63%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 real, copy-pasteable Membrane CLI commands and a well-sequenced, validated connection workflow. It is held back by an unnecessary background intro, an inline entity catalog that would benefit from a reference file, and lighter validation guidance in the action/proxy sections.

Suggestions

Move the ~40-item entity bullet list into a references/catalog file and keep SKILL.md as an overview that links to it, improving both conciseness and progressive disclosure.

Trim the opening "Mambu is a cloud banking platform..." paragraph to one line or remove it, since Claude can infer domain context from the description.

Add a validation/check step after running actions (e.g., inspect the `output` field for errors, retry on non-2xx) to strengthen workflow clarity for potentially destructive banking operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening "Mambu is a cloud banking platform..." background paragraph and the ~40-item entity bullet list that could be trimmed or moved, fitting the 3 anchor rather than the lean 5.	3 / 5
Actionability	It provides concrete, executable commands throughout (npm install, membrane login, connection ensure, action list/run, request) with a flags table, but minor gaps like unresolved CONNECTION_ID placeholders and the vague "Use action names and parameters as needed" keep it just below 5.	4 / 5
Workflow Clarity	The connection flow is a clear sequence with validation checkpoints (poll --wait, branch on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but the action-running and proxy sections lack equivalent validation guidance, so it stops at 4.	4 / 5
Progressive Disclosure	No bundle files exist and no references are signaled; the skill is a single ~190-line file with decent section headers, but content that could be split out (the entity catalog, the full connection state machine) is inlined, matching the 3 anchor.	3 / 5
	Total	14 / 20 Passed

Description

73%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 targets the Mambu niche with an explicit use-when trigger, but its capability statement relies on generic verbs ("manage," "automate") rather than concrete actions. Strong distinctiveness and trigger clarity, weaker on specificity.

Suggestions

Replace generic verbs with concrete Mambu actions, e.g. "Manage loan and deposit accounts, process transactions, and automate workflows. Use when the user wants to interact with Mambu data."

Add natural trigger variations such as "Mambu accounts," "Mambu loans," or "Mambu API" to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Mambu domain and lists a few actions, but the actions are generic ("manage", "automate") rather than concrete like "extract" or "fill," so it sits above the minimal/generic anchor of 2 but lacks the specificity of 4.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Mambu data"), but the "what" is generic and the trigger could be more specific, so it does not reach the fully concrete 5.	4 / 5
Trigger Term Quality	"Mambu integration" and "Use when the user wants to interact with Mambu data" provide good natural keyword coverage centered on the proper noun "Mambu," with only minor variations missing, fitting the 4 anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	"Mambu integration" targets a clear niche (a specific cloud banking platform) with distinct triggers, giving minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/mambu/SKILL.md
Commit: f484c82

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