Name: mobivate
Rating: 58.4 (1 reviews)
Author: membranedev

mobivate

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

Quality

67%

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

Quality

Content

72%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 executable commands and a clear connect workflow, but it is held back by the absence of any validation step for destructive API operations and by an inlined reference-style catalog that progressive disclosure would normally move into a separate file.

Suggestions

Add a verification/validation checkpoint before running or proxying mutating requests (POST/PUT/PATCH/DELETE) — e.g., preview the action's inputSchema and confirm scope before execute — to satisfy the workflow-clarity requirement for destructive/batch operations.

Extract the clientAction field schema and the Mobivate Overview entity tree into a references/ file and link to it one level deep, keeping SKILL.md a lean overview.

Trim the soft prose in Best practices ('burn less tokens', 'rather than auth plumbing') for tighter token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is command-driven with compact executable membrane commands and a flag table, with only minor over-explanation ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens').	4 / 5
Actionability	Copy-paste-ready membrane commands with exact flags and --json are given throughout (login, connection ensure, action list/run, request) and a specific flag table covers the common cases.	5 / 5
Workflow Clarity	The connect flow is well sequenced with state branches and a poll-again feedback loop, but because the skill runs actions and proxies POST/PUT/DELETE requests (destructive/batch-capable) with no validation or verify step, workflow clarity is capped at 3 per the rubric.	3 / 5
Progressive Disclosure	The body is well-headed and organized, but no bundle/reference files exist and inlined bulk (the clientAction field-schema breakdown and the Mobivate Overview entity tree) that could live in a separate reference file keeps it at the 'could be better split' tier.	3 / 5
	Total	15 / 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 establishes a clear branded niche and provides an explicit 'when' trigger, but leans on a single generic verb ('Manage') and a thin set of natural keywords that undersell the platform's SMS/marketing capabilities.

Suggestions

Replace the generic 'Manage' with concrete actions (e.g., 'Send SMS campaigns, build contact lists, schedule messages, and pull delivery reports') to raise specificity.

Add natural trigger terms users actually say — 'SMS campaigns', 'mobile marketing', 'contact lists', 'delivery reports' — instead of the single phrase 'interact with Mobivate data'.

Drop the 'and more' padding; it adds length without information.

Dimension	Reasoning	Score
Specificity	Names the Mobivate domain and concrete entity objects (Persons, Organizations, Deals, Leads, Projects, Activities), but the only action verb is the generic 'Manage' plus 'and more', so concrete actions are not enumerated.	3 / 5
Completeness	It explicitly answers both 'what' (manage Persons, Organizations, Deals, Leads, Projects, Activities) and 'when' (use when the user wants to interact with Mobivate data), though the 'when' is a single broad clause rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	A trigger phrase is present ('Use when the user wants to interact with Mobivate data') but natural terms users would actually say (campaigns, SMS, contacts, lists, templates) are missing, leaving only relevant-but-incomplete keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The named 'Mobivate' platform gives a clear niche with minimal conflict risk, though the generic CRM-style entity vocabulary (Persons, Organizations, Deals, Leads) creates minor overlap with other CRM tools.	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/mobivate/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.