Name: metomic
Rating: 55.2 (1 reviews)
Author: membranedev

metomic

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

Quality

62%

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/metomic/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 skill shines on actionability with concrete, executable CLI commands and a clear state-driven connection workflow, but it is dragged down by a large padded entity list and monolithic structure. Trimming the enumeration and splitting reference material would materially improve token efficiency and organization.

Suggestions

Remove or collapse the ~130-line entity/"X Log" enumeration; rely on `membrane action list --intent` for discovery and keep only a few representative examples inline.

Fix the dangling "skip to Step 2" reference by labeling the post-connection section (searching/running actions) as Step 2, or rephrase to avoid numbered cross-references.

Move any retained bulk entity or API reference into a separate references file and link to it from SKILL.md so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	The ~130-line enumeration of entity and "X Log" types is heavy padding — Claude can discover these via `membrane action list`, so listing every variant ("Anonymization Log," "Pseudonymization Log") is noticeably verbose. It is not a 1 because the CLI command sections are lean and actionable.	2 / 5
Actionability	The body provides copy-paste-ready commands for the full lifecycle — install, login (including headless `login complete <code>`), connection ensure, polling with `--wait`, action search/run with JSON input, and proxy requests with a flags table. Specific examples cover the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts). It is not a 5 because the "skip to Step 2" reference dangles with no labeled Step 2, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Headers give the file reasonable structure, but the bulk entity enumeration is inlined content that belongs in a separate reference file or should be removed, and no external references are signaled. It is not a 4 because content that should be separate is inline rather than split out.	3 / 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 correctly includes an explicit "Use when" clause and is distinct thanks to the named product, but it is hurt by generic action verbs and sparse trigger keywords. Tightening the capability list and adding concrete domain terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Metomic capabilities, e.g. "Discover, classify, and manage personal data; handle subject rights requests and consent."

Add natural trigger variations users might say — "privacy compliance," "subject rights requests," "consent management," "data mapping" — alongside "Metomic data."

Make the "Use when" clause more specific, e.g. "Use when the user wants to query Metomic records, manage consent, or run privacy workflows."

Dimension	Reasoning	Score
Specificity	The description names the domain ("Metomic integration") but the actions — "Manage data, records, and automate workflows" — are minimal and generic; "manage" and "automate workflows" are not concrete capabilities. It is below the midpoint because it lacks specific verbs like discover, classify, or audit that Metomic actually performs.	2 / 5
Completeness	Both halves are present: "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Metomic data"). It is not a 5 because the "when" trigger is generic and the "what" lacks concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Metomic data" supplies the natural keyword "Metomic data," but coverage is thin — no synonyms, related phrases (privacy, consent, subject rights), or variations users might say. It sits at 3 rather than 4 because only one domain term is present with no common variations.	3 / 5
Distinctiveness Conflict Risk	Metomic is a specific named product, and the trigger is tied directly to "Metomic data," giving it a clear niche with minimal overlap risk against other skills.	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/metomic/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.