Name: vivocalendar
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

vivocalendar

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

Quality

66%

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

Quality

Content

75%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 CLI commands and a clear connection workflow, weakened mainly by a padded speculative opener and a minor dangling step reference.

Suggestions

Delete or replace the hedged opener ("likely used... probably used") with a one-line factual statement of what Vivocalendar is.

Label the section referenced as "Step 2" (action discovery/running) so the "skip to Step 2" pointer resolves.

Add an explicit validation checkpoint before destructive proxy requests (e.g. confirm method/path) to strengthen the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but the opening speculative paragraph ("likely used for scheduling... probably used by individuals or teams") explains a concept Claude already knows and pads the token budget.	3 / 5
Actionability	The skill provides fully executable, copy-paste-ready commands throughout (login, connection ensure, action list/run, request) plus a comprehensive proxy flags table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based polling feedback (BUILDING → CLIENT_ACTION_REQUIRED → READY), though the "skip to Step 2" reference points to an unlabeled section and validation gaps remain for destructive proxy calls.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear headers with no nested references and no monolithic wall of text; content is appropriately scoped for a CLI integration skill though no bundle files split out deeper detail.	4 / 5
	Total	16 / 20 Passed

Description

57%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 functional with an explicit trigger clause and a distinct brand name, but its action language is generic and it omits the natural calendar/event vocabulary users would actually say.

Suggestions

Replace generic verbs with concrete Vivocalendar operations, e.g. "create and update calendar events, manage contacts, and list schedules".

Add natural trigger terms users say aloud — "calendar", "events", "appointments", "scheduling" — alongside the brand name.

Tighten the "Use when" clause to reference specific intents like booking or rescheduling events rather than "interact with Vivocalendar data".

Dimension	Reasoning	Score
Specificity	The description names the domain but uses only generic actions like "Manage data, records, and automate workflows" — no concrete operations such as creating events or listing calendars, matching the anchor where actions are minimal or generic.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "Use when the user wants to interact with Vivocalendar data" trigger are present, though the "when" is somewhat generic.	4 / 5
Trigger Term Quality	The brand name "Vivocalendar" is a relevant trigger, but natural phrases users would say (calendar, events, appointments, scheduling) are absent, leaving common variations and synonyms missing.	3 / 5
Distinctiveness Conflict Risk	The named app "Vivocalendar" gives it a mostly distinct niche, but the generic "manage data, records, and automate workflows" phrasing creates minor overlap risk with other data-management skills.	4 / 5
	Total	13 / 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/vivocalendar/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.