Name: conversionomics
Rating: 61.6 (1 reviews)
Author: membranedev

conversionomics

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

Quality

72%

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

Quality

Content

82%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 a tight, highly actionable CLI integration guide with executable commands at every step and a clear connection workflow with state-based checkpoints. It is held back only by minor verbosity and a slightly informal 'Step 2' reference plus missing explicit error-recovery guidance.

Suggestions

Label the post-connection section as 'Step 2' (or remove the dangling 'skip to Step 2' reference) so the workflow sequence is unambiguous.

Add a brief error-recovery checklist for CONFIGURATION_ERROR and SETUP_FAILED states instead of only 'check the error field for details'.

Trim the entity bullet list and the line 'Use action names and parameters as needed', or move the entity/action reference into a separate reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands with brief, justified context (the one-paragraph product intro is reasonable since Conversionomics is niche), fitting 'efficient; minor instances of over-explanation that could be trimmed'. Not a 5 because the entity list and lines like 'Use action names and parameters as needed' add little value, and not a 3 because padding is minor.	4 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure/get, action list/run, request proxy) plus a flag table, matching 'fully executable; copy-paste ready; specific examples cover the common cases'. Placeholders like CONNECTION_ID are appropriate and do not reduce executability.	5 / 5
Workflow Clarity	The connect-and-use flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-until-ready feedback loop, fitting 'clear sequence with most checkpoints present'. Not a 5 because the 'Step 2' reference is unlabeled and there is no explicit error-recovery checklist for CONFIGURATION_ERROR/SETUP_FAILED beyond 'check the error field'.	4 / 5
Progressive Disclosure	No bundle files exist, so all content is self-contained in a single well-sectioned file (Overview, Install, Auth, Connecting, Searching, Actions, Best practices), fitting 'good structure; most content appropriately placed'. Not a 5 because the entity list and proxy/action reference could live in separate files, and not a 3 because organization is clear with no buried or nested references.	4 / 5
	Total	17 / 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 answers both what the skill does and when to use it, and the product name gives it good distinctiveness. Its main weakness is generic action language and thin trigger-term coverage that misses the natural vocabulary marketers would use.

Suggestions

Replace generic actions ('Manage data, records') with concrete Conversionomics capabilities such as 'run A/B tests, analyze conversion funnels, and build reports'.

Expand the 'Use when' clause with natural trigger phrases a user would actually say, e.g. 'Use when the user wants to analyze conversion rates, review A/B test results, or pull Conversionomics reports'.

Add a synonym or file/context cue (e.g. 'marketing analytics', 'conversion optimization') to improve trigger-term match quality.

Dimension	Reasoning	Score
Specificity	Names the domain (Conversionomics integration) and a few actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete capabilities, matching the '1-2 concrete actions, not comprehensive' anchor. It is above a 2 because multiple actions are named, but not a 4 since none are specific (no A/B testing, reporting, or analytics mentioned).	3 / 5
Completeness	It has both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Conversionomics data'), matching the 4 anchor where both are present but the 'when' could be more specific. Not a 5 because the trigger phrases are not concrete (no list of distinct triggering situations).	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with Conversionomics data' includes the product name and 'data'/'records', but lacks common variations, synonyms, or the natural phrases a marketer would say (e.g. 'conversion rates', 'A/B test', 'analytics'). It fits the 'some relevant keywords but missing common variations' anchor rather than a 4 with broader coverage.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product 'Conversionomics' gives it a clear niche with minimal conflict risk, fitting 'mostly distinct; minor overlap risk'. Not a 5 because the generic 'interact with Conversionomics data' trigger is less sharply distinguished than the anchor's explicit multi-trigger example.	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/conversionomics/SKILL.md
Commit: f484c82

Reviewed: 4 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.