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

Blog Docs Log in Get started

matterport

Matterport integration. Manage Spaces. Use when the user wants to interact with Matterport data.

Quality

64%

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

Quality

Content

63%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 concrete CLI commands and a sound connection workflow including a polling feedback loop. Its main weaknesses are a placeholder Overview section and duplicated/inconsistent guidance that hurt conciseness, plus an all-inline structure with no progressive disclosure for a skill of this length.

Suggestions

Remove or fill in the placeholder "Matterport Overview" section ("- **Model** / - **Note**") and trim the introductory Matterport background paragraph that Claude can infer, to tighten conciseness.

Fix the dangling "skip to Step 2" references by either adding a labeled Step 2 header or rewording to point at the actual section (e.g., "Searching for actions").

Consolidate the duplicated action-discovery guidance in "Searching for actions" and "Popular actions" into one section, and move the proxy-options table / clientAction detail into reference files to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding: an introductory paragraph explaining what Matterport is, a placeholder "Matterport Overview" section ("- Model / - Note"), and duplicated action-discovery guidance in both "Searching for actions" and "Popular actions". It is not verbose enough for score 2 nor lean enough for score 4.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) covering the common cases. Minor gaps come from the vague placeholder Overview ("Use action names and parameters as needed") and an inconsistency between `membrane` and `npx @membranehq/cli@latest` invocations, keeping it just below score 5.	4 / 5
Workflow Clarity	The connect -> poll-for-ready -> search-actions -> run sequence is clear and includes a real feedback loop (poll connection state, handle CLIENT_ACTION_REQUIRED, re-poll after user action). It falls short of score 5 because of broken "skip to Step 2" references with no corresponding Step 2 header and the absence of post-action validation.	4 / 5
Progressive Disclosure	The skill is well over 50 lines with no bundle files or external references, so all detail lives inline — including the proxy-options table and the detailed clientAction object structure that could reasonably be split out. Structure exists via clear headers, but no content is offloaded to separate files, matching score 3 rather than score 4.	3 / 5
	Total	14 / 20 Passed

Description

66%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 concise, uses third person, and includes an explicit "Use when" trigger, giving it solid completeness and distinctiveness. It is weakest on trigger-term breadth and action specificity, naming only one capability and few synonyms.

Suggestions

Add 1-2 more concrete capabilities beyond "Manage Spaces" (e.g., browse Spaces, fetch models/scans, retrieve measurement data) to lift specificity toward score 4-5.

Broaden trigger terms with natural synonyms users say, such as "3D tours", "digital twins", "virtual tours", or "Matterport scans", to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the Matterport domain and one concrete, domain-specific action ("Manage Spaces"), but offers only a single action rather than a comprehensive set. It sits above score 2 (which names only the domain with generic actions) but below score 4 (which lists several specific actions).	3 / 5
Completeness	Explicitly answers both "what" ("Matterport integration. Manage Spaces.") and "when" ("Use when the user wants to interact with Matterport data."), though the "when" clause is somewhat generic. Falls short of score 5's concrete, multi-trigger phrasing but clearly exceeds score 3's missing/weak "when".	4 / 5
Trigger Term Quality	Includes relevant keywords ("Matterport", "Spaces", "Matterport data") a user would naturally say, but misses common synonyms and variations such as "3D tour", "digital twin", "virtual tour", or "scan". Not sparse enough for score 2, not comprehensive enough for score 4.	3 / 5
Distinctiveness Conflict Risk	Matterport is a specific, named platform with a distinct trigger phrase ("interact with Matterport data"), giving it a clear niche with minimal conflict risk. It matches the score-5 anchor of a clear niche with distinct triggers.	5 / 5
	Total	15 / 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/matterport/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.