Name: phonecom
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

phonecom

Phone.com integration. Manage Accounts. Use when the user wants to interact with Phone.com data.

Quality

63%

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

Quality

Content

61%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 strongly actionable with real CLI commands and a clear connection-state workflow, but it is slightly verbose, has a broken step reference, and lacks validation checkpoints for destructive proxy operations.

Suggestions

Add an explicit verification/validation checkpoint after destructive proxy calls (e.g. re-fetch the resource or check the response status before proceeding), and fix the undefined 'Step 2' reference.

Trim the Phone.com intro paragraph and the rationale padding in Best practices so every token earns its place.

Either deliver on the 'Popular actions' section with a few concrete worked examples, or remove the heading to avoid the promised-but-missing content.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening paragraph explaining what Phone.com is and phrases like 'so you can focus on the integration logic rather than auth plumbing' and 'This will burn less tokens' are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, executable Membrane CLI commands for install, login, connection, action search/run, and proxy with a full flags table, but examples rely on templated placeholders (<actionId>, CONNECTION_ID), the 'Popular actions' section underdelivers, and no fully worked real invocation with output parsing is shown.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with a polling feedback loop over states (READY/BUILDING/CLIENT_ACTION_REQUIRED), but 'skip to Step 2' references an undefined step, and the proxy/action-run workflows support destructive methods (DELETE/PUT) with no validation or verification checkpoint, capping the score at 3.	3 / 5
Progressive Disclosure	The body is well organized into clear single-level sections (Overview, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references and easy navigation, but at ~155 lines with no external reference files, some inline material (proxy flags, connection state machine) could be split out for a leaner overview.	4 / 5
	Total	14 / 20 Passed

Description

66%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 clear and distinct, answering both what the skill does and when to use it, anchored to a specific product. Its main weakness is thin action and trigger coverage that omits Phone.com's actual feature set.

Suggestions

Expand the action list beyond 'Manage Accounts' to mention concrete capabilities such as calls, SMS, fax, voicemail, contacts, and call routing.

Broaden the trigger clause with natural phrases users say, e.g. 'Use when the user wants to manage Phone.com calls, SMS, voicemail, contacts, or accounts.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('Phone.com integration') and one concrete action ('Manage Accounts'), but the second phrase ('interact with Phone.com data') is generic and the many real capabilities (SMS, fax, voicemail, contacts) are omitted, so coverage is not comprehensive.	3 / 5
Completeness	Both 'what' ('Phone.com integration. Manage Accounts.') and 'when' ('Use when the user wants to interact with Phone.com data.') are present and explicit, but the 'when' is somewhat generic rather than listing concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	'Phone.com' and 'Accounts' are relevant natural terms a user might say, but the trigger clause ('interact with Phone.com data') misses common variations and feature synonyms like calls, SMS, voicemail, fax, or contacts.	3 / 5
Distinctiveness Conflict Risk	Naming a specific named product (Phone.com) establishes a clear niche with distinct, brand-anchored triggers and minimal risk of conflicting with other skills.	5 / 5
	Total	15 / 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/phonecom/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.