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

vivomeetings

Vivomeetings integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vivomeetings 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vivomeetings/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 body is highly actionable with executable CLI commands and a clear, well-sectioned connection workflow including state-based checkpoints. Minor conciseness trimming and a more explicit error-recovery loop would lift the weakest dimensions.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with executable commands and minimal padding, but it includes light over-explanation such as 'Think of it as a competitor to Zoom or Google Meet' and the Agent Types aside that could be trimmed; it sits above 3 (mostly efficient) but not fully lean enough for 5.	4 / 5
Actionability	It provides fully executable, copy-paste ready commands throughout (membrane login, connection ensure, action list/run, request proxy) with a complete options table, matching the 5 anchor of copy-paste ready commands covering common cases.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state checks (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll loop with --wait, providing most checkpoints; it stops at 4 because error recovery (CONFIGURATION_ERROR/SETUP_FAILED) only says 'check the error field' without an explicit validate-fix-retry loop.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no bundle files and no nested references, and the inline content is appropriately scoped for a single-file skill; it does not reach 5 only because there is no explicit reference structure to navigate, but for a self-contained skill this is strong.	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 is a valid third-person statement with an explicit 'Use when' trigger, but it relies on generic verbs ('Manage', 'automate workflows') and offers only the product name as a natural trigger term. It is functional but not as concrete or trigger-rich as the top examples.

Suggestions

Replace generic verbs with concrete actions a user would request, e.g. 'List meetings, fetch recordings, manage participants, and automate meeting workflows'.

Expand trigger terms beyond the product name to include natural phrases users say, such as 'meeting schedules, webinar recordings, participant lists, or meeting data'.

Tighten the 'when' clause to reference concrete triggers (e.g. 'Use when the user asks about Vivomeetings meetings, recordings, or participant data') to raise completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain and 1-2 concrete actions ('Manage data, records, and automate workflows') but the actions are generic ('Manage', 'automate') rather than specific concrete operations, so it sits at the 3 anchor and below 4 which requires several specific actions.	3 / 5
Completeness	It states a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vivomeetings data'), satisfying the 4 anchor; the 'when' is somewhat generic rather than listing concrete trigger phrases, so it does not reach 5.	4 / 5
Trigger Term Quality	It includes the trigger clause 'Use when the user wants to interact with Vivomeetings data', but the only natural keyword is 'Vivomeetings' itself — missing common synonyms or variations a user would say, so it matches the 3 anchor ('some relevant keywords but missing common variations').	3 / 5
Distinctiveness Conflict Risk	The 'Vivomeetings' product name gives it a clear niche distinct from other skills with only minor overlap risk against generic 'data/records' skills; it does not reach 5 because the action verbs ('Manage data, records, automate workflows') are broad enough to overlap with adjacent integration skills.	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/vivomeetings/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.