Name: myphoner
Rating: 64.8 (1 reviews)
Author: membranedev

myphoner

Myphoner integration. Manage Leads, Persons, Organizations, Pipelines, Users, Roles and more. Use when the user wants to interact with Myphoner data.

Quality

78%

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/myphoner/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 strong, executable guide to the Membrane CLI workflow with clear connection-state validation and feedback loops. Its chief weaknesses are minor verbosity and the absence of error-handling guidance for action runs.

Suggestions

Trim the introductory "Myphoner is a cloud-based phone system..." paragraph and the filler line "Use action names and parameters as needed." to tighten conciseness.

Add a short error-handling note for `membrane action run` (e.g., inspect the response error field and retry or surface it to the user) to complete the workflow's validation loop.

De-duplicate the action-discovery command, which appears under both "Searching for actions" and "Popular actions".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient executable commands and necessary connection-state detail, with only minor padding (the "cloud-based phone system" intro, the filler line "Use action names and parameters as needed.", and a repeated action-list command), so it sits above anchor 3 but short of the fully lean anchor 5.	4 / 5
Actionability	It provides copy-paste-ready CLI commands across the common cases (install, login, connection ensure, polling, action list, action run with JSON input, proxy requests) plus a flags table, all with clearly indicated placeholders — matching the fully-executable anchor 5.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit state validation (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop, but the action-running section offers no error-handling guidance, leaving a minor validation gap below anchor 5.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with well-organized, clearly headed sections and no broken or buried references; since no external bundle files exist and the content is appropriately placed, it is well-structured with only minor organization gaps rather than the clean one-level-deep reference split of anchor 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 clearly identifies a distinct named integration and provides an explicit "Use when" trigger, with good coverage of the entities users would reference. Its main weakness is relying on the single generic verb "Manage" rather than enumerating distinct concrete actions.

Suggestions

Replace or expand the single verb "Manage" with distinct concrete actions (e.g., "create, update, search, and assign Leads, Persons, and Organizations") to lift specificity.

Broaden the "when" clause with concrete entity-based trigger phrases (e.g., "Use when the user mentions Myphoner leads, call lists, or pipeline status").

Drop the hedging "and more" in favor of the most important remaining capability, since vague tail terms dilute specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates concrete entities ("Manage Leads, Persons, Organizations, Pipelines, Users, Roles and more"), but relies on a single generic verb ("Manage") rather than multiple distinct concrete actions, so it sits above anchor 2 yet below the several-specific-actions bar of anchor 4.	3 / 5
Completeness	It explicitly answers both "what" (Myphoner integration; manage the listed entities) and "when" ("Use when the user wants to interact with Myphoner data"), but the "when" is a single phrased trigger rather than multiple concrete trigger phrases, keeping it below anchor 5.	4 / 5
Trigger Term Quality	Natural terms are present via the brand "Myphoner", "Myphoner data", and the entity names (Leads, Persons, Organizations) users would say; a named SaaS has few synonyms, so coverage is good but not the comprehensive synonym/extension spread of anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Myphoner" is a specific named SaaS app and the trigger is brand-anchored ("interact with Myphoner data"), giving a clear niche with minimal risk of firing for the wrong skill.	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/myphoner/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.