Name: macrometa
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

macrometa

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

Quality

63%

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/macrometa/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 highly actionable with concrete CLI commands and a clear state-driven connection flow, weakened by duplicated action-discovery instructions, orphaned 'Step 2'/'1b' references, and some inline content that could be separated.

Suggestions

Merge 'Popular actions' into 'Searching for actions' to remove the duplicated `action list --intent` command and tighten the body.

Relabel the connection flow with explicit Step 1 / Step 2 headers (or remove the 'skip to Step 2' / '1b' references) so the sequence is unambiguous.

Add one end-to-end example showing a real action run (a concrete actionId and its JSON output) to lift actionability to fully copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the 'Searching for actions' and 'Popular actions' sections repeat the same `action list --intent` invocation, and the long concept bullet-list plus the one-line platform definition add padding; matches 'mostly efficient but includes some unnecessary explanation or could be tightened', not a 4 due to the duplicated action-list command.	3 / 5
Actionability	Concrete executable commands appear throughout (`npm install -g @membranehq/cli@latest`, `membrane connection ensure`, `membrane action run ... --input '{"key": "value"}'`, `membrane request CONNECTION_ID /path`) plus a full proxy-flags table; mostly executable with minor gaps (CONNECTION_ID/<actionId> placeholders and no example of a real action run with real output), so 4 rather than 5.	4 / 5
Workflow Clarity	The connection flow has a real sequence with state checkpoints (READY / BUILDING poll / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR), but 'skip to Step 2' and '1b. Wait for the connection' reference a Step 2 and Step 1a that are never labeled, leaving sequence gaps; fits 'steps listed but validation gaps; checkpoints missing or implicit', not a 4 due to the orphaned step references.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), and the body is organized into clearly headed sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content reasonably placed inline; good structure with minor organization gaps (the concept list and proxy options table could be split out), matching the 4 anchor rather than a 3.	4 / 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 cleanly answers what and when for a clearly distinct branded platform, with an explicit trigger clause. It is held back by generic action verbs ('manage data/records') and limited trigger-term variation.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Create and query collections, publish to streams, run Query Workers, and manage records'.

Expand the trigger with natural variations: 'Use when the user wants to query, insert, or stream Macrometa data, or manage collections and Query Workers.'

Mention key artifacts users name (collections, streams, Query Workers, geo-distributed data) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Macrometa domain plus three action areas, but the actions are generic ('manage data' overlaps 'records') rather than concrete, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor; not a 4 because the actions lack the specificity of 'extracts text, fills forms, converts pages'.	3 / 5
Completeness	Both 'what' ('Macrometa integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Macrometa data.') are present; not a 5 because the trigger is a single clause rather than the multiple concrete trigger phrases of the 5 anchor.	4 / 5
Trigger Term Quality	The phrase 'Use when the user wants to interact with Macrometa data' supplies the core natural term 'Macrometa data', but coverage is thin with no synonyms or variations, fitting 'some relevant keywords but missing common variations'; not a 4 because only the single branded trigger is present.	3 / 5
Distinctiveness Conflict Risk	'Macrometa integration' pins a specific branded platform giving it a clear niche with distinct triggers and minimal conflict risk with other skills, matching the 'clear niche with distinct triggers' anchor.	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/macrometa/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.