Name: momo
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

momo

MoMo integration. Manage Recordses. Use when the user wants to interact with MoMo data.

Quality

66%

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

Quality

Content

75%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 CLI commands and a well-structured connection workflow including validation checkpoints, but it carries some explanatory padding and a couple of structural inconsistencies (dangling 'Step 2' reference, a duplicated actions section). Trimming the prose and fixing the step numbering would raise conciseness and workflow clarity.

Suggestions

Cut non-essential rationale asides (e.g. 'so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection') to tighten token efficiency.

Fix the step labeling: either label 'Step 1 / Step 2' explicitly or replace the 'skip to Step 2' reference with a concrete section name.

Merge or differentiate the 'Searching for actions' and 'Popular actions' sections to remove the near-duplicate action-listing guidance.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete CLI commands, but several padded asides ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way to get a connection', the token-burn rationale in Best practices) could be trimmed, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure/wait, action list/run, proxy request) with a concrete flag table, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Clear install→auth→connect→discover→run sequence with explicit validation checkpoints (state polling, READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR handling) and a re-poll feedback loop, but step labels are inconsistent ('skip to Step 2' with no labeled Step 2), fitting the 'clear sequence with most checkpoints; minor gaps' anchor.	4 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers and no nested references (and no bundle files present), but the file exceeds the simple-skill threshold and has minor duplication ('Popular actions' re-states 'Searching for actions'), matching the 'good structure; minor organization gaps' anchor.	4 / 5
	Total	16 / 20 Passed

Description

57%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 covers both what and when with an explicit 'Use when' clause and a distinct brand trigger, but its action language is generic ('Manage Recordses') and trigger-term coverage is narrow. Tightening the 'what' with concrete operations and adding natural synonyms would lift specificity and trigger quality.

Suggestions

Replace the generic 'Manage Recordses' with concrete operations, e.g. 'Create, read, update, delete, and list Records in MoMo'.

Expand trigger terms with natural variations users might say, such as 'MoMo records', 'query MoMo data', or 'sync with MoMo'.

Make the 'when' clause more specific than 'interact with MoMo data' by naming the tasks it covers (e.g. 'Use when creating, querying, or updating Records in MoMo').

Dimension	Reasoning	Score
Specificity	Names the MoMo domain and the 'Records' entity, but the only stated action ('Manage Recordses') is generic rather than a concrete operation, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions required for a 3.	2 / 5
Completeness	Explicitly answers both 'what' ('MoMo integration. Manage Recordses.') and 'when' ('Use when the user wants to interact with MoMo data'); the trigger clause is present but generic, fitting the anchor where both exist yet 'when' could be more specific.	4 / 5
Trigger Term Quality	Includes the brand keyword 'MoMo', the entity 'Records', and a trigger phrase ('interact with MoMo data'), but lacks common variations or synonyms, matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	MoMo is a named platform with brand-specific triggers ('interact with MoMo data'), making it mostly distinct with only minor overlap risk against other generic data-management skills.	4 / 5
	Total	13 / 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/momo/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.