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

superphone

SuperPhone integration. Manage Persons, Organizations, Leads, Deals, Activities, Notes and more. Use when the user wants to interact with SuperPhone 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/superphone/SKILL.md

Quality

Content

82%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 a well-structured, highly actionable guide with copy-paste-ready Membrane CLI commands and a real state-polling feedback loop for connection setup. Its main gaps are minor numbering inconsistency in the workflow and some inline detail that could be split into reference files.

Suggestions

Normalize the connection workflow numbering (label '1a' alongside '1b' and add the referenced 'Step 2' header) so the sequence is unambiguous.

Move the detailed clientAction sub-bullets and the proxy flag table into a separate REFERENCE.md and link to it, tightening the main body and improving progressive disclosure.

Trim the soft commentary (e.g. 'so you can focus on the integration logic rather than auth plumbing') to push conciseness toward fully lean.

Dimension	Reasoning	Score
Conciseness	Largely efficient with concrete commands and minimal padding; a few minor instances of over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the product intro sentence, matching the 'efficient; minor over-explanation that could be trimmed' anchor rather than 5.	4 / 5
Actionability	Provides copy-paste-ready, executable commands across install, login, connection ensure, polling, action list/run, and proxy requests, plus a full flag table, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow has clear state-based branching with an explicit poll-retry feedback loop (CLIENT_ACTION_REQUIRED -> poll again until READY), but overall step numbering is inconsistent ('1b' without a labeled '1a', an unlabeled 'Step 2'), fitting 'clear sequence with most checkpoints; minor gaps' rather than 5.	4 / 5
Progressive Disclosure	Well-organized into clear headed sections with no nested or buried references and no bundle files to score against, but at ~160 lines some inlineable detail (full clientAction sub-bullets, proxy flag table) could live in separate reference files, matching 'good structure; minor organization gaps' rather than the under-50-line exception's 5.	4 / 5
	Total	17 / 20 Passed

Description

71%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 specific and distinctive, clearly naming a SuperPhone integration with multiple managed entity types and an explicit Use-when clause. Its main weakness is a generic trigger phrase that lacks the concrete variations a user might naturally say.

Suggestions

Add concrete trigger phrases to the Use-when clause, e.g. 'Use when the user wants to manage SuperPhone calls, contacts, leads, or deals' to improve trigger-term quality and completeness.

Replace the single generic verb 'Manage' with a few distinct action verbs (create, update, search, log) to push specificity toward comprehensive coverage.

Consider dropping 'and more' or replacing it with the next few concrete entity types to close the coverage gap.

Dimension	Reasoning	Score
Specificity	Lists several concrete domain objects to manage ("Persons, Organizations, Leads, Deals, Activities, Notes and more"), matching the 'several specific actions; minor gaps' anchor; not 5 because all use the single generic verb 'Manage' and 'and more' leaves coverage incomplete.	4 / 5
Completeness	Explicitly states both what (manage the listed entities) and when ('Use when the user wants to interact with SuperPhone data'), but the 'when' is generic rather than concrete trigger phrases, matching the 'both what and when; when could be more explicit' anchor rather than 5.	4 / 5
Trigger Term Quality	Includes the natural brand keyword 'SuperPhone' and a Use-when clause, but the trigger ('interact with SuperPhone data') is generic and misses common user variations like SuperPhone calls, contacts, or leads, fitting the 'some relevant keywords but missing synonyms' anchor.	3 / 5
Distinctiveness Conflict Risk	'SuperPhone' is a specific named product niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 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/superphone/SKILL.md
Commit: f484c82

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