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

Blog Docs Log in Get started

mattr

MATTR integration. Manage data, records, and automate workflows. Use when the user wants to interact with MATTR 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/mattr/SKILL.md

Quality

Content

61%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 actionable and well-structured CLI guidance with a real error-recovery loop for connection states, but it is padded with removable prose, has muddled step numbering, and inlines material that could be split out. Overall a solid, executable skill with modest trimming and organization gains available.

Suggestions

Remove the opening "MATTR is a platform..." paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside; assume Claude knows what the platform is.

Fix the incoherent step labels: define explicit "Step 1 / Step 2" headers instead of a lone "1b" and a "skip to Step 2" with no visible Step 2.

Add a validation checkpoint before running actions (e.g., "review inputSchema and confirm parameters with the user before running actions that mutate data") and provide one fully worked action-run example with real input and output.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and tables, but retains unnecessary prose such as the MATTR intro paragraph, the "auth plumbing" aside, and a redundant second "Popular actions" action-list example.	3 / 5
Actionability	Concrete, executable membrane commands with flags, JSON input examples, and a proxy options table cover the common cases; the only gap is a fully worked example showing a real actionId and its output payload.	4 / 5
Workflow Clarity	The connection state-polling branch (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) is a genuine feedback loop, but the "skip to Step 2" and "1b" labeling is incoherent and there is no validation checkpoint before running potentially destructive actions.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and the skill is self-contained with no broken references, but inlined reference material (the clientAction schema and the proxy flag table) could live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

61%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 is distinctive due to the branded MATTR name and includes an explicit trigger clause, but its stated capabilities are generic and the trigger vocabulary is thin. It answers what and when without being concrete about either.

Suggestions

Replace generic actions with concrete MATTR capabilities, e.g. "Issue and verify credentials, manage DIDs and schemas, handle presentations" instead of "Manage data, records, and automate workflows".

Expand trigger terms to include natural synonyms users say, such as "verifiable credentials", "DIDs", "presentations", or "decentralized identity" alongside "MATTR".

Make the "Use when..." clause specific to MATTR tasks rather than reusing the vague "interact with MATTR data" phrasing.

Dimension	Reasoning	Score
Specificity	The description names the MATTR domain but the actions ("Manage data, records, and automate workflows") are generic verbs on generic nouns rather than concrete MATTR-specific operations like issuing verifiable credentials or managing DIDs.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "Use when..." trigger are present, but both are vague and the when-clause largely mirrors the what.	4 / 5
Trigger Term Quality	The only natural trigger keyword is the platform name "MATTR" / "MATTR data", which is relevant but lacks common variations or synonyms a user might say.	3 / 5
Distinctiveness Conflict Risk	"MATTR" is a unique branded platform name, so the trigger is highly distinct and unlikely to fire for an unrelated skill.	5 / 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/mattr/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.