Name: signalwire
Rating: 61.6 (1 reviews)
Author: membranedev

signalwire

SignalWire integration. Manage Persons, Organizations, Leads, Deals, Projects, Activities and more. Use when the user wants to interact with SignalWire data.

Quality

73%

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

Quality

Content

67%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.

A highly actionable, well-structured CLI integration guide with a clear state-gated connection workflow. Its main weaknesses are an unnecessary background intro, a duplicated/redundant "Popular actions" section, and a forward reference to an unlabeled "Step 2".

Suggestions

Delete or condense the opening "SignalWire is a cloud communications platform ..." paragraph; Claude does not need the platform explained.

Either populate "Popular actions" with a few concrete example action ids/intents, or remove the section since it duplicates the discovery command from "Searching for actions".

Label the run-actions phase as the "Step 2" referenced earlier (or drop the "skip to Step 2" wording) so the forward reference resolves to an actual heading.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("SignalWire is a cloud communications platform ...") explains background concepts Claude already knows, and the "Popular actions" section repeats the discovery command already shown in "Searching for actions", so the body is mostly efficient but carries clear padding.	3 / 5
Actionability	It provides concrete, copy-pasteable commands throughout (install, login incl. headless completion, connection ensure, polling, action list/run, request proxy) plus a flag table, with only minor gaps such as the "Popular actions" section not actually listing any popular actions.	4 / 5
Workflow Clarity	The install → login → connect → poll-until-ready → search → run sequence is clear and gated by an explicit state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with polling feedback, though the referenced "Step 2" is not a labeled heading and the action-running phase lacks an error-recovery loop.	4 / 5
Progressive Disclosure	The single SKILL.md is well organized into clearly headed sections with no nested references and no bundle files present; at ~150 lines it exceeds the simple-skill threshold, so it does not reach the one-level-deep reference structure of a 5.	4 / 5
	Total	15 / 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.

A solid, third-person description that names the platform and its core entities and provides an explicit use-when clause. It is distinct and unlikely to conflict, but the single generic verb "Manage" and broad "when" phrasing leave it just short of the top anchor.

Suggestions

Replace the generic "Manage" with two or three distinct verbs (e.g., "Create, update, and query Persons, Organizations, Leads, Deals, Projects, and Activities") to strengthen specificity.

Sharpen the trigger clause to name concrete intents, e.g. "Use when the user wants to manage leads, deals, contacts, or other SignalWire records".

Drop the vague "and more" or replace it with the remaining entity types so coverage is explicit rather than implied.

Dimension	Reasoning	Score
Specificity	"Manage Persons, Organizations, Leads, Deals, Projects, Activities and more" lists six concrete domain entities, but the single generic verb "Manage" plus the vague "and more" keeps it from the comprehensive multi-action level of a 5.	4 / 5
Completeness	It states both what ("SignalWire integration. Manage ... data") and when ("Use when the user wants to interact with SignalWire data"), but the "when" is somewhat generic and could name concrete triggers like managing leads or deals to reach a 5.	4 / 5
Trigger Term Quality	Names the platform ("SignalWire") and the natural entity nouns users would say (Persons, Leads, Deals, etc.) with an explicit "Use when the user wants to interact with SignalWire data" trigger, but lacks synonyms or variations beyond the enumerated entities.	4 / 5
Distinctiveness Conflict Risk	"SignalWire integration" is a clearly named platform niche with distinct triggers and minimal risk of firing for an unrelated skill.	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/signalwire/SKILL.md
Commit: f484c82

Reviewed: 4 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.