Name: telnyx
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

telnyx

Telnyx integration. Manage Accounts, PhoneNumbers, Medias, Conferences. Use when the user wants to interact with Telnyx data.

Quality

67%

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

Quality

Content

63%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's instructional core is highly actionable with a well-sequenced, validated connection workflow, but it is undermined by a massive block of duplicated bullet lines under Telnyx Overview and an inlined resource catalog that belongs in a separate reference file. Fixing the duplication and externalizing the catalog would lift both conciseness and progressive disclosure.

Suggestions

Remove the ~830 duplicated "Call Screening Rule Destination Settings" lines under Telnyx Overview — this is corrupted/padded content burning the majority of the file's tokens.

Move the full resource catalog into a references/ file (e.g. RESOURCES.md) and keep only the most-used categories in SKILL.md with a clear "See RESOURCES.md" pointer for one-level-deep navigation.

Trim the intro paragraph ("Telnyx is a communications platform that provides...") — Claude already knows what Telnyx is — and add a brief validation/caution note for destructive actions such as delete-phone-number.

Dimension	Reasoning	Score
Conciseness	The CLI instruction core is efficient, but roughly 830 lines under "Telnyx Overview" are the duplicated phrase "Call Screening Rule Destination Settings" repeated verbatim, and the intro paragraph explains what Telnyx is — heavy padding that disrespects the token budget.	2 / 5
Actionability	Provides copy-paste-ready, executable commands for the full flow (npm install, membrane login, connection ensure, action list/run with --input JSON, request proxy) plus a Popular actions table with concrete action keys and a proxy-flag reference table.	5 / 5
Workflow Clarity	A clear install → authenticate → connection ensure → poll-for-READY → search → run sequence with state-based validation (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop; minor gaps in explicit step numbering and no validation guidance for destructive actions like delete-phone-number.	4 / 5
Progressive Disclosure	Section headers (Overview, Working with Telnyx, Popular actions, Best practices) give some structure, but the ~120-item resource catalog is inlined in SKILL.md and there are no bundle files or one-level-deep references to split it out.	3 / 5
	Total	14 / 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 concise, third-person, and explicitly pairs a capability statement with a Use-when clause, giving it a clear niche and low conflict risk. Its main weaknesses are trigger-term thinness (over-reliance on the brand name) and a generic "Manage" verb with only four of the many available resources.

Suggestions

Broaden trigger terms to natural phrases users say, e.g. "Use when the user wants to send SMS, make or manage calls, buy phone numbers, or work with Telnyx messaging/voice data."

Replace the generic "Manage" with concrete verbs (e.g. "List, buy, update, and delete phone numbers; send SMS/MMS; place and control calls") so capabilities read as actions rather than a single bucket.

Consider mentioning messaging profiles or call control since those are the popular actions highlighted in the body.

Dimension	Reasoning	Score
Specificity	Names the domain (Telnyx) plus four concrete resource types ("Accounts, PhoneNumbers, Medias, Conferences"), but the single verb "Manage" is generic and covers only a small slice of the resources the body exposes.	4 / 5
Completeness	Both halves are present — "what" (Telnyx integration managing four resource types) and an explicit "Use when the user wants to interact with Telnyx data" — but the "when" is generic rather than concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	Relies almost entirely on the brand name "Telnyx" / "Telnyx data" as the trigger; natural terms users actually say (SMS, calls, messaging, voice, VoIP) are absent even though "PhoneNumbers" and "Conferences" add a little coverage.	3 / 5
Distinctiveness Conflict Risk	A specific branded platform integration ("Telnyx integration") with a distinct trigger term; minimal realistic overlap with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1114 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/telnyx/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.