Name: mboum
Rating: 56.8 (1 reviews)
Author: membranedev

mboum

Mboum integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Mboum data.

Quality

65%

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

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 content is largely actionable with concrete Membrane CLI commands and a good state-driven connection workflow, but it is weakened by placeholder filler, an inconsistent/incoherent Mboum Overview that contradicts the description (Patient/Practitioner/Appointment vs. Persons/Deals/Leads), and broken step numbering. Conciseness is the weakest dimension.

Suggestions

Remove the placeholder paragraph ("exact purpose and target audience are currently unknown") and replace the vague Mboum Overview with the actual object model, ensuring it matches the entities in the description.

Fix the step numbering: relabel "1b. Wait for the connection to be ready" as Step 2 and resolve the dangling "skip to Step 2" reference so the sequence is coherent.

Either delete the redundant "Popular actions" section (it repeats the action list command) or populate it with 2-3 real popular action examples for Mboum.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight CLI commands, but the placeholder filler ("Mboum is a SaaS application that likely caters to a specific niche, but its exact purpose and target audience are currently unknown") and the vague "Use action names and parameters as needed." are unnecessary padding that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy with a flags table), with only minor gaps such as placeholder actionIds and the thin "Popular actions" section that repeats the search command without real examples.	4 / 5
Workflow Clarity	The connection setup has a clear state-based sequence with explicit checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-until-ready feedback loop, though the step numbering is broken ("skip to Step 2" with no Step 2; a "1b" subsection instead of Step 2).	4 / 5
Progressive Disclosure	It is a single well-sectioned file (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with clear headers and no external references needed for a CLI skill, but the redundant "Popular actions" section and the placeholder "Mboum Overview" are minor organization gaps.	4 / 5
	Total	15 / 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 answers both what and when and is anchored to a distinct app name, but it leans on a single generic action verb ("Manage") plus "and more" filler and lacks concrete trigger phrases. Trigger term and specificity are the weakest dimensions.

Suggestions

Replace the generic "Manage ... and more" with 2-3 concrete verbs (e.g., "Create, update, and query Persons, Organizations, Deals, Leads, Projects, and Activities") to lift specificity.

Add concrete natural-language trigger phrases to the "Use when" clause, e.g., "Use when the user wants to create or look up Mboum deals, manage leads, or query Mboum records."

Drop the vague "and more" padding; either enumerate the full object list or omit the filler.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Deals, Leads, Projects, Activities and more" names the domain and several concrete entities, but relies on a single generic verb ("Manage") with vague "and more" padding rather than listing multiple distinct actions.	3 / 5
Completeness	It has both a clear "what" ("Mboum integration. Manage Persons, Organizations...") and an explicit "when" ("Use when the user wants to interact with Mboum data"), though the trigger is somewhat generic rather than concrete phrases.	4 / 5
Trigger Term Quality	"interact with Mboum data" plus the entity list (Persons, Organizations, Deals, Leads, Projects, Activities) provides some natural keywords, but "Mboum" is merely repeated and common variations or synonyms a user would say are missing.	3 / 5
Distinctiveness Conflict Risk	The proper noun "Mboum" gives it a clear niche with minimal conflict risk, but the generic CRM vocabulary (Persons, Organizations, Deals, Leads) creates minor overlap risk with other CRM-style 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/mboum/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.