Name: vitel-phone
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

vitel-phone

Vitel Phone integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vitel Phone 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/vitel-phone/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 a well-structured, highly actionable Membrane/CLI integration guide with a strong connection state-machine workflow. Its main weaknesses are a 'Popular actions' section that promises but does not deliver named actions, minor verbosity, and a slightly mislabeled step reference.

Suggestions

Populate the 'Popular actions' section with 3-5 concrete Vitel Phone action examples (e.g. send SMS, list voicemail, place a call) with real actionIds and sample input/output, instead of only the discovery command.

Fix the 'skip to Step 2' reference by explicitly labeling 'Step 2: Search for actions' so the sequence is unambiguous.

Trim the opening product-blurb paragraph and marketing-flavored asides to keep the guide lean.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste CLI commands, but the opening product-description paragraph and a few marketing-flavored lines ('so you can focus on the integration logic rather than auth plumbing', 'This is the fastest way') could be trimmed.	4 / 5
Actionability	It provides concrete, executable membrane commands with flags and a proxy-options table, but the 'Popular actions' section only shows the discovery command and never lists actual Vitel Phone actions (e.g. send SMS, fetch voicemail), leaving a gap in common-case coverage.	4 / 5
Workflow Clarity	The connect-to-ready flow is a clear state-machine with polling and CLIENT_ACTION_REQUIRED handling (a genuine validation feedback loop), but the 'skip to Step 2' reference points to an unlabeled step and there is no explicit post-run verification.	4 / 5
Progressive Disclosure	The single file is well-organized into logical headed sections with no nested references, though some inline detail (the proxy flag table, the connection state machine) could plausibly live in separate reference files for a >100-line skill.	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 third-person, includes an explicit 'Use when' trigger, and names a distinct product niche, but its action vocabulary is generic and the trigger scenarios are narrow. It is solid but could be sharpened with concrete capability and trigger phrases.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Vitel Phone capabilities such as placing calls, sending SMS, retrieving voicemail, and managing contacts/phone numbers.

Expand the trigger clause to name natural user scenarios, e.g. 'Use when the user wants to send Vitel Phone SMS, check voicemail, place or route calls, or manage Vitel Phone contacts and numbers.'

Add common synonyms/keywords a user might actually say (calls, voicemail, SMS, auto-attendant) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Vitel Phone domain and lists a few actions ('Manage data, records, and automate workflows'), but those verbs are generic rather than concrete API-level actions, matching the 'minimal or generic' anchor better than the 'concrete actions' anchor.	2 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Vitel Phone data'), but the trigger clause is somewhat narrow and could name concrete scenarios more explicitly.	4 / 5
Trigger Term Quality	'Vitel Phone' is a strong brand trigger and 'data, records, workflows' add some relevant keywords, but common variations or scenario-specific phrases (calls, SMS, voicemail) are missing, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the named 'Vitel Phone' product gives a clear niche with minimal conflict risk, though the generic 'manage data, records, automate workflows' phrasing leaves minor overlap with other integration 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/vitel-phone/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.