Name: mati
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mati

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

Quality

61%

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/mati/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 body is highly actionable with concrete, executable Membrane CLI commands and a well-instrumented connection state machine, but it is padded with explanatory prose, has inconsistent step numbering, and inlines reference material that a >50-line skill would benefit from splitting into separate files.

Suggestions

Trim explanatory Membrane-behavior prose (e.g. 'so you can focus on the integration logic rather than auth plumbing', the URL-normalization paragraph) to assume Claude's competence and reduce tokens.

Fix the step numbering: add an explicit Step 1 / Step 2 structure so the 'skip to Step 2' and '1b' references resolve, and add a verification checkpoint after running actions that modify Mati records.

Move the proxy flags table and the detailed clientAction field schema into a separate reference file (e.g. reference.md) referenced from the main body, so SKILL.md stays a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary prose such as 'so you can focus on the integration logic rather than auth plumbing' and explanatory Membrane-behavior paragraphs ('The URL is normalized to a domain and matched against known apps...') that could be trimmed, fitting the 3-anchor.	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure/get with --wait, action list/run, request proxy) complete with flags, --json output, and a flags table, matching the 5-anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The connection flow has good state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with polling feedback), but the step numbering is inconsistent (a '1b' with no '1a', dangling 'skip to Step 2' references with no Step 2 header) and the action-running workflow lacks post-execution verification for what may be destructive record changes, triggering the destructive-operation cap at 3.	3 / 5
Progressive Disclosure	The content is sectioned with clear headers and avoids nested references, but at ~140 lines with detailed reference material (the proxy flags table, the full clientAction sub-field schema) inlined into a single SKILL.md with no separate reference files, it fits the 3-anchor where content that should be split remains inline.	3 / 5
	Total	14 / 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 correctly names the Mati domain and includes an explicit 'Use when' trigger, but its capability language is generic ('data, records, workflows') rather than reflecting Mati's actual identity-verification purpose. It is functional but underspecific.

Suggestions

Replace generic verbs with Mati-specific capabilities, e.g. 'Verify user identities, create and manage applicants, and check verification status'.

Sharpen the trigger to natural user phrasing such as 'Use when the user wants to verify a user's identity, onboard an applicant, or check Mati verification status'.

Mention Mati's identity-verification purpose in the description itself so the skill surfaces for fraud/compliance/onboarding requests, not just generic 'Mati data' queries.

Dimension	Reasoning	Score
Specificity	The description names the Mati domain but its actions — "Manage data, records, and automate workflows" — are generic and not concrete Mati capabilities (e.g. identity verification, applicant creation, verification status checks), matching the 'actions are minimal or generic' anchor rather than the 3-anchor which requires concrete actions.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Mati data") are present, but the 'when' trigger is broad and could be more specific, matching the 4-anchor rather than the fully concrete 5-anchor.	4 / 5
Trigger Term Quality	The brand keyword "Mati" and "interact with Mati data" provide a relevant trigger, but the supporting terms ("data", "records", "workflows") are generic and miss natural user phrases like "verify a user" or "create an applicant", fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Mati" creates a mostly distinct niche with low conflict risk, though the generic 'manage data/records/workflows' phrasing leaves minor overlap with general data-management skills, fitting the 4-anchor rather than the minimal-risk 5-anchor.	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/mati/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.