Name: aivie
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

aivie

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

Quality

70%

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

Quality

Content

61%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 body delivers concrete, executable Membrane CLI guidance with a clear connection workflow and state-machine feedback loop, but it carries background fluff and—critically—lacks validation/verification checkpoints for destructive or batch data operations, capping workflow clarity. Structure is good but has a couple of redundant or under-explained sections.

Suggestions

Add explicit validation checkpoints after destructive/batch operations, e.g. 'After running a mutating action, re-query the record with membrane action run <readActionId> to confirm the change applied' — this would lift the workflow_clarity cap.

Remove the background paragraph ('Aivie is a platform that helps users create and manage AI models...') and the filler line 'Use action names and parameters as needed' to improve conciseness.

Flesh out the 'Popular actions' section with the actual common Aivie actions (e.g. list/search patients, create note) instead of repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but includes unnecessary background ('Aivie is a platform that helps users create and manage AI models without needing extensive coding knowledge... business analysts, marketers') and filler ('Use action names and parameters as needed') that could be trimmed.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action run with --input JSON, proxy request) plus a flag table; minor gaps remain since placeholders like <agentType> and CONNECTION_ID need substitution and no end-to-end worked example is given.	4 / 5
Workflow Clarity	A clear install→auth→connect→search→run sequence exists with a connection-state feedback loop, but the skill operates on Aivie records via actions and proxy requests (destructive/batch-capable) with no validation or verification checkpoints, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized section headers and no external references (appropriate given it needs none); minor organization gaps include a redundant 'Popular actions' section that repeats the discovery command instead of listing actions and a sparse unexplained entity bullet list.	4 / 5
	Total	14 / 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.

The description clearly names the Aivie platform, lists several concrete capabilities, and provides an explicit 'Use when' trigger, making it distinct and unlikely to misfire. It falls just short of the top tier because the trigger is a single condition and the capability verbs are somewhat generic rather than comprehensive.

Suggestions

Add concrete trigger variations users would actually say, e.g. 'Use when the user wants to query, create, or update Aivie records, automate Aivie workflows, or work with Aivie data.'

Replace the generic verb 'Manage' with specific Aivie operations (e.g. 'Create, update, and query patient and user records; automate Aivie workflows').

Dimension	Reasoning	Score
Specificity	Names the Aivie domain and lists several concrete actions ('Manage data, records, and automate workflows'), matching the score-4 anchor of several specific actions with minor coverage gaps; not 5 because 'manage data' and 'records' are somewhat generic rather than comprehensively concrete.	4 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Aivie data'); the 'when' is explicit but tied to a single scenario, so it does not reach the comprehensive concrete trigger phrases of score 5.	4 / 5
Trigger Term Quality	Includes the natural trigger phrase 'Use when the user wants to interact with Aivie data' with the product name, giving good keyword coverage; not 5 because it lacks common synonyms and variations a user might actually say.	4 / 5
Distinctiveness Conflict Risk	Targets a distinct named third-party platform (Aivie) with a niche-specific trigger, giving 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/aivie/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.