Name: plivo
Rating: 64 (1 reviews)
Author: membranedev

plivo

Plivo integration. Manage Accounts, Applications, Numbers, Messages, Calls, Conferences. Use when the user wants to interact with Plivo data.

Quality

76%

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/plivo/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 concrete, copy-paste commands and a clear workflow with validation checkpoints. Its main weakness is a verbose introductory paragraph that explains background concepts Claude already knows.

Suggestions

Cut or drastically shorten the opening paragraph ('Plivo is a cloud communications platform...') — Claude already knows what Plivo is; lead instead with how to use the skill.

Resolve the ambiguous 'Step 2' cross-reference by giving the action-search/run sections explicit numbered labels that match the 'skip to Step 2' instruction.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Plivo is, who uses it, and its use cases — concepts Claude already knows — which is unnecessary padding; the remainder is reasonably lean but not tight enough for anchor 4.	3 / 5
Actionability	Provides copy-paste ready commands throughout ('npm install -g @membranehq/cli@latest', 'membrane connection ensure', 'membrane action run', 'membrane request') with concrete flags, schemas, and a popular-actions table covering common cases.	5 / 5
Workflow Clarity	A clear sequenced flow (install → authenticate → connect → poll state → search actions → run → proxy fallback) with state-based checkpoints and feedback loops ('poll again', 'CLIENT_ACTION_REQUIRED'); minor gaps like the ambiguous 'Step 2' reference keep it below anchor 5.	4 / 5
Progressive Disclosure	Well-organized into logical sections with no nested references and no bundle files to navigate; the popular-actions table is reasonably placed inline, but the ~150-line single-file body has minor organization gaps versus the ideal overview-pointing-to-references structure.	4 / 5
	Total	16 / 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 is well-targeted to a distinct platform niche and answers both what and when, with concrete resource categories. Its main weakness is the generic 'Manage' verb and a 'when' clause that lacks concrete trigger phrases.

Suggestions

Replace the generic 'Manage' verb with a few distinct concrete actions (e.g. 'Send SMS, make and hang up calls, list and buy phone numbers, manage applications and subaccounts').

Expand the 'Use when' clause with concrete trigger phrases and synonyms users actually say, e.g. 'Use when the user wants to send SMS/MMS, make or hang up calls, or manage Plivo phone numbers, applications, and accounts.'

Dimension	Reasoning	Score
Specificity	Lists several concrete resource categories ('Accounts, Applications, Numbers, Messages, Calls, Conferences') but applies a single generic verb ('Manage') to all of them rather than distinct actions, so it falls short of the comprehensive multi-action anchor 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Manage Accounts, Applications, Numbers, Messages, Calls, Conferences') and 'when' ('Use when the user wants to interact with Plivo data'), but the when-clause is generic rather than concrete trigger phrases, matching anchor 4 not 5.	4 / 5
Trigger Term Quality	Good keyword coverage including 'Plivo', 'Messages', 'Calls', and 'Conferences', but missing common natural synonyms users would say like SMS, MMS, voice, or phone numbers, so not anchor 5.	4 / 5
Distinctiveness Conflict Risk	Plivo is a specific named platform with distinct resource triggers ('Accounts, Applications, Numbers, Messages, Calls, Conferences'), giving a clear niche with minimal conflict risk.	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/plivo/SKILL.md
Commit: f484c82

Reviewed: ~20 hours 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.