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

mattermark

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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mattermark/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 body is a well-structured, actionable Membrane CLI integration guide with clear command examples and good state-handling checkpoints for the connection workflow. Its main weaknesses are minor redundancy across the action-discovery sections and a generic proxy flag table rather than Mattermark-specific examples.

Suggestions

Consolidate the duplicate action-discovery content in 'Searching for actions' and 'Popular actions' into a single section to remove redundancy.

Replace the generic proxy flag table with one or two Mattermark-specific request examples (e.g. a company search or list query) to lift actionability.

Add a brief validation/confirmation checkpoint before running batch actions (e.g. confirm the returned action's inputSchema against the request) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes repetition (the action-list command appears under both 'Searching for actions' and 'Popular actions') and light padding ('so you can focus on the integration logic rather than auth plumbing'), fitting 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands for install, login, connection ensure, action search/run, and proxy requests, covering the common cases; minor gaps remain (CONNECTION_ID placeholders and the proxy section is generic CLI flags rather than Mattermark-specific examples).	4 / 5
Workflow Clarity	The install -> auth -> connect -> poll-for-state -> search -> run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; minor gaps come from the jumbled 'Popular actions' section and no validation step before running batch read actions.	4 / 5
Progressive Disclosure	As a single-file skill with no bundle directories, it is well-organized into clearly headed sections (Overview, Working with Mattermark, Connecting, Searching, Proxy, Best practices); it stays at 4 rather than 5 because inlined content like the generic proxy flag table could live elsewhere and section ordering is slightly redundant.	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 correctly pairs a 'what' with an explicit 'Use when...' trigger and anchors on the distinct Mattermark domain, but the capability verbs are generic and the trigger lacks synonyms or concrete use cases. It is solid but unspectacular, sitting just above the midpoint on most dimensions.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Mattermark actions such as 'search companies, fetch company profiles, manage lists, and pull growth/funding data'.

Broaden the trigger clause with natural synonyms and use cases, e.g. 'Use when the user wants to search Mattermark company data, qualify leads, or work with company lists and profiles'.

Mention file/identifier cues users actually reference (company domains, organization IDs, list names) to improve distinctiveness and trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Mattermark domain and a few actions ('Manage data, records, and automate workflows'), but the verbs are generic and not comprehensive, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor rather than the vague score-2 or the multi-action score-4.	3 / 5
Completeness	It states both what ('Mattermark integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Mattermark data'), but the 'when' is generic rather than tied to concrete use cases, matching the 'has both what and when; when could be more explicit' anchor and clearly above score-3.	4 / 5
Trigger Term Quality	'Mattermark' and 'interact with Mattermark data' are natural trigger phrases, but it lacks common variations or synonyms (company data, leads, company profiles, search), fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The distinct 'Mattermark' name carves a clear niche with minimal conflict risk against non-Mattermark skills, though the generic 'manage data/records/workflows' phrasing leaves minor overlap risk with other integration 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/mattermark/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.