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

Blog Docs Log in Get started

kandy

Kandy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Kandy 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/kandy/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 body is highly actionable with executable Membrane CLI commands and a clear connection workflow including validation. The main weaknesses are mild verbosity (intro explainer, a duplicated command section) and sectioned rather than fully numbered workflow sequencing.

Suggestions

Trim the opening 'Kandy is a real-time communications platform as a service (CPaaS)...' paragraph or move it under a collapsed overview; Claude can infer the platform purpose.

Remove the redundant 'Popular actions' section that repeats the action-list command already shown in 'Searching for actions', or merge them.

Add a short numbered end-to-end quickstart (install → login → connection ensure → search actions → run action) with an explicit validation checkpoint before running actions.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command reference, but the opening CPaaS explainer and the redundant 'Popular actions' section (which repeats the action-list command) add unnecessary tokens that could be trimmed.	3 / 5
Actionability	Provides copy-paste ready, executable commands across install, login, connection, action search/run, and proxying with flag tables, covering the common cases fully.	5 / 5
Workflow Clarity	The connection workflow has explicit state-polling validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after user action), but the overall flow is sectioned rather than a single numbered sequence with checkpoints.	4 / 5
Progressive Disclosure	A single well-organized SKILL.md with clear sections and no nested references; at ~140 lines it exceeds the simple-skill threshold, so it sits at 'good structure, minor organization gaps' rather than 5.	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 correctly includes an explicit 'Use when...' trigger and names a distinctive platform, but its capability verbs are generic rather than concrete. Tightening 'Manage data, records, and automate workflows' into specific Kandy actions would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Kandy capabilities, e.g. 'Make and manage voice/video calls, send messages, and retrieve call history and voicemail'.

Expand the trigger to natural phrasings users would say, e.g. 'Use when the user wants to place Kandy calls, send Kandy messages, or query call history/voicemail'.

Add the file/extension or API surface terms (e.g. 'Kandy API', 'CPaaS') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the Kandy domain but the actions ('Manage data, records, and automate workflows') are generic verbs rather than concrete capabilities, matching the 'names domain but actions minimal/generic' anchor.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Kandy data') are present, though the 'what' is generic so it sits at the 'both present, when could be more specific' anchor.	4 / 5
Trigger Term Quality	'Kandy' and 'interact with Kandy data' provide a relevant keyword but no synonyms, variations, or file extensions, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	Kandy is a specific named platform giving a clear niche with minimal conflict risk, but the generic 'manage data, records, automate workflows' verbs leave minor overlap with other integration skills, keeping it just below 5.	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/kandy/SKILL.md
Commit: f484c82

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