Name: omniconvert
Rating: 64 (1 reviews)
Author: membranedev

omniconvert

Omniconvert integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Omniconvert data.

Quality

76%

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

Quality

Content

75%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.

A well-structured, mostly executable CLI integration guide with a clear connection workflow and explicit state-handling feedback loops. It could tighten minor fluff, add Omniconvert-specific action examples, and fix the dangling "Step 2" reference.

Suggestions

Replace the generic action examples with at least one Omniconvert-specific illustration (e.g., listing experiments or variations) so the guidance is actionable for this integration rather than only for the Membrane CLI generally.

Fix the dangling "skip to Step 2" reference by labeling the "Searching for actions" section as Step 2, or remove the step-numbering language to avoid confusion.

Trim marketing-style phrasing (e.g., "so you can focus on the integration logic rather than auth plumbing") and consolidate the overlapping "Popular actions" and "Searching for actions" sections to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly lean with executable commands and a useful flag table, but includes minor fluff such as "so you can focus on the integration logic rather than auth plumbing" and a background paragraph that could be trimmed.	4 / 5
Actionability	Provides concrete, copy-paste-ready CLI commands with clear placeholders (connection ensure, action list, action run, request proxy), but examples stay generic to the Membrane CLI with no Omniconvert-specific action illustrations.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-after-action feedback loop, but "skip to Step 2" references a section that is not labeled as Step 2.	4 / 5
Progressive Disclosure	Well organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references and no bundle files, though "Popular actions" partially duplicates "Searching for actions".	4 / 5
	Total	16 / 20 Passed

Description

78%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.

A solid description that names concrete entities and provides an explicit "Use when" trigger tied to a distinct product niche. The main weakness is the somewhat generic trigger phrasing ("interact with Omniconvert data") rather than concrete user scenarios.

Dimension	Reasoning	Score
Specificity	Lists several concrete entity types ("Persons, Organizations, Deals, Leads, Projects, Activities"), giving specific coverage of what can be managed, though the repeated verb "Manage" is generic and "and more" leaves minor gaps.	4 / 5
Completeness	Explicitly states both what ("Manage Persons, Organizations, Deals, Leads, Projects, Activities") and when ("Use when the user wants to interact with Omniconvert data"), but the "when" is generic and could tie to more concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes the natural brand term "Omniconvert" and concrete entity names (Deals, Leads, Persons) a user would say, plus an explicit "Use when..." trigger, but lacks synonyms or variations beyond the brand name.	4 / 5
Distinctiveness Conflict Risk	Tied to the specific named product "Omniconvert" with distinct brand-keyed triggers, giving it a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	17 / 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/omniconvert/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.