Name: mono
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mono

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

78%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 executable commands and a clear connection-readiness feedback loop, but it is a monolithic single file with no progressive disclosure and carries minor over-explanation. Splitting the state-machine and proxy reference detail into separate files and tightening the intro would raise it further.

Suggestions

Move the detailed clientAction state machine and the proxy flags/options table into a separate reference file (e.g. references/connections.md) referenced one level deep from the body.

Remove or condense the "Mono is a platform for embedding banking..." paragraph and the placeholder "Mono Overview" list, which add little actionable value.

Replace the dangling "Step 2" / "1b" references with an explicit numbered sequence so the install→connect→search→run flow is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening "Mono is a platform for embedding banking..." paragraph and the placeholder "Mono Overview" list (Contact/Conversation/User with "Use action names and parameters as needed") are minor over-explanation that could be trimmed, matching the 'efficient, minor instances of over-explanation' anchor rather than the lean level 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every step (install, login, connection ensure/get with --wait, action list/run with --input, request with a complete flags table) covering the common cases, matching the 'fully executable, copy-paste ready' anchor.	5 / 5
Workflow Clarity	There is a clear install→authenticate→connect→search→run sequence with an explicit state-polling feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and "poll again after the user completes the action"), but the flow references an unlabeled "Step 2" and uses an odd "1b" subsection, leaving minor structural gaps that keep it below the fully checklist-driven level 5.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a single ~140-line file; sections are present but the detailed clientAction state machine and proxy options table are inline rather than split into one-level-deep reference files, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	16 / 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 includes both a capability statement and an explicit "Use when" trigger in third-person voice, but the actions and trigger terms are generic and Mono-specific synonyms are absent. It is functional but could be sharper about the concrete financial/banking capabilities Mono provides.

Suggestions

Replace generic verbs ("Manage data, records, automate workflows") with concrete Mono capabilities, e.g. "Fetch connected accounts, transactions, balances, and income; reconcile statements."

Add natural trigger terms and synonyms users actually say, e.g. "Use when the user wants to access Mono financial accounts, transactions, balances, or banking data."

State the domain explicitly in the trigger (financial/banking data) so it does not overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	Names the domain ("Mono integration") and a few actions ("Manage data, records, and automate workflows"), but the actions are generic rather than concrete, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multiple-specific-actions level above.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Mono data") are present, but the "when" clause is generic and could be more explicit, matching the 'both what and when, when could be more specific' anchor rather than the fully concrete level 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Mono data" provides some relevant keywords but only surfaces "Mono" and "data", missing natural synonyms or specific terms users would say, so it sits at the 'some relevant keywords but missing variations' anchor rather than good coverage (4) or only-jargon (2).	3 / 5
Distinctiveness Conflict Risk	"Mono integration" ties it to a specific platform giving it a clear niche, but the generic "Manage data, records" wording creates minor overlap risk with other data-handling skills, so it is mostly distinct rather than fully conflict-free (5).	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/mono/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.