Name: telesign
Rating: 59.2 (1 reviews)
Author: membranedev

telesign

TeleSign integration. Manage data, records, and automate workflows. Use when the user wants to interact with TeleSign data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

81%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, mostly executable guide to driving TeleSign through the Membrane CLI, with a strong connection-state workflow that includes validation and a re-poll feedback loop. Its weaknesses are a light TeleSign-background preamble and the absence of any concrete TeleSign-specific action example.

Suggestions

Trim the 3-sentence TeleSign/CPaaS intro to one line; Claude already knows what CPaaS is.

Add at least one concrete TeleSign action example (e.g. sending an SMS or verifying a phone number) with a real action id and input JSON, instead of only generic `action run <actionId>`.

Resolve the orphaned 'skip to Step 2' reference and the duplicate action-list command under 'Popular actions' to tighten navigation.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable CLI reference (commands, a flags table, state transitions); the only real padding is the 3-sentence intro explaining what TeleSign/CPaaS is, which is trimmable. Not a 3 because the intro is a minor portion and the rest earns its tokens.	4 / 5
Actionability	Concrete, executable commands cover install, login (incl. headless), connection ensure, polling, action list/run, and proxy with a full flags table; the gap is that no concrete TeleSign-specific action example is shown — TeleSign use cases are deferred to `action list --intent` discovery rather than illustrated.	4 / 5
Workflow Clarity	The connect-to-TeleSign flow is clearly sequenced with explicit validation via the connection `state` field and a feedback loop: poll until not BUILDING, handle CLIENT_ACTION_REQUIRED, re-poll after the user acts, and inspect `error` on CONFIGURATION_ERROR/SETUP_FAILED.	5 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, and no bundle files exist to split into; minor gaps are the orphaned 'Step 2' reference and the 'Popular actions' section re-stating the action-list command already shown under 'Searching for actions'.	4 / 5
	Total	17 / 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 correctly includes an explicit 'Use when' trigger and names the TeleSign niche, but its action vocabulary is generic ('manage data, records, and automate workflows') rather than concrete TeleSign capabilities. It is distinct due to the brand name yet thin on natural trigger terms.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete TeleSign actions, e.g. 'Send SMS, verify phone numbers, and score phone-number risk via TeleSign'.

Expand the trigger to natural user phrases: 'Use when the user wants to send SMS, verify a phone number, or check phone reputation/fraud risk with TeleSign'.

Drop generic terms like 'data' and 'records' that add no distinctiveness and could trigger unrelated skills.

Dimension	Reasoning	Score
Specificity	It names the domain ('TeleSign integration') but the actions are minimal and generic — 'Manage data, records, and automate workflows' is abstract with no concrete TeleSign actions like send SMS or verify a phone number.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with TeleSign data') are present; the 'when' could be more specific, matching the anchor where both exist but the trigger is not fully concrete.	4 / 5
Trigger Term Quality	'TeleSign' is the relevant natural keyword and anchors the trigger, but the phrase 'interact with TeleSign data' is generic and misses common variations users would say (SMS, verify, phone verification, OTP, fraud).	3 / 5
Distinctiveness Conflict Risk	The 'TeleSign' brand names a distinct CPaaS niche with low overlap risk, but the generic action language ('manage data, records') leaves minor overlap risk with broad data-handling skills rather than a fully distinct trigger set.	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/telesign/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.