Name: ambivo
Rating: 59.2 (1 reviews)
Author: membranedev

ambivo

Ambivo integration. Manage Organizations, Pipelines, Users, Filters, Activities, Notes and more. Use when the user wants to interact with Ambivo data.

Quality

69%

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

Quality

Content

71%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 strong, executable integration guide with clear CLI commands, a connection-state workflow, and a useful actions table. Its weaker points are the absence of bundle reference files for the large action/proxy detail and missing explicit validation checkpoints for run/proxy operations.

Suggestions

Move the Popular actions table and proxy flag reference into separate one-level-deep reference files (e.g. references/actions.md, references/proxy.md) and link them from SKILL.md to improve progressive disclosure.

Add explicit validation/verify steps after destructive or batch operations (e.g. checking the action run output or confirming a proxy request status) to lift workflow clarity to 5.

Trim minor redundant explanation (such as repeated descriptions of Membrane credential handling) to make the body leaner and lift conciseness.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable CLI commands and tables rather than padded explanations; minor over-explanation (e.g. restating what Membrane does for auth) could be trimmed.	4 / 5
Actionability	It provides concrete, copy-pasteable membrane CLI commands with flags and example payloads plus a Popular actions table, though some workflows reference placeholders (CONNECTION_ID) without showing how to obtain the resolved value inline.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks and polling (BUILDING -> READY/CLIENT_ACTION_REQUIRED), but the destructive/batch 'action run' and proxy request steps lack explicit validation or verify checkpoints, so it does not reach 5.	4 / 5
Progressive Disclosure	No bundle files (references/scripts/assets) exist, and the Popular actions table plus proxy flag reference are inlined into SKILL.md rather than split into one-level-deep reference files; structure is present but not split for deep navigation.	3 / 5
	Total	15 / 20 Passed

Description

67%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 is well-targeted to the Ambivo CDP domain with an explicit 'Use when' clause and a concrete list of managed resources, satisfying both what and when. Its main weakness is somewhat generic trigger phrasing and the vague 'and more' hedge.

Suggestions

Add natural-language trigger phrases a user would actually say (e.g. 'list Ambivo orders', 'create an Ambivo lead', 'sync Ambivo contacts') to improve trigger term quality.

Replace the 'and more' hedge with a concrete enumeration or a clear scope boundary so specificity is comprehensive rather than open-ended.

Tighten the 'Use when' clause to reference specific intents (e.g. querying, creating, updating Ambivo records) instead of the generic 'interact with Ambivo data'.

Dimension	Reasoning	Score
Specificity	It names the domain (Ambivo) and enumerates several concrete manageables ('Manage Organizations, Pipelines, Users, Filters, Activities, Notes and more'), giving multiple specific actions, though the 'and more' weakens comprehensiveness.	4 / 5
Completeness	It states both a clear 'what' (manage Organizations, Pipelines, Users, etc.) and an explicit 'when' ('Use when the user wants to interact with Ambivo data'); the 'when' is explicit but fairly generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	'Ambivo integration' and 'interact with Ambivo data' are reasonable trigger terms but there are few natural synonyms a user would say and no common variations, so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The Ambivo CDP niche is distinct with clear triggers, so conflict risk is low, though the generic 'Use when the user wants to interact with Ambivo data' is broadly phrased.	4 / 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/ambivo/SKILL.md
Commit: f484c82

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