Name: dexatel
Rating: 56.8 (1 reviews)
Author: membranedev

dexatel

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

Quality

65%

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/dexatel/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.

The body is a well-structured, mostly executable guide with a clearly sequenced connection workflow and concrete CLI commands, held back by some boilerplate Claude already knows and a large inline actions table that could be externalized.

Suggestions

Cut the opening boilerplate ("Dexatel is a cloud communication platform...") and the filler line "Use action names and parameters as needed." to recover token budget.

Add an explicit validation/checkpoint before batch operations such as create-campaign to satisfy the destructive/batch workflow cap.

Move the 14-row Popular actions table into a references file and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but includes unnecessary explanation Claude already knows ("Dexatel is a cloud communication platform that provides businesses with tools for SMS messaging, voice calls..."), filler ("Use action names and parameters as needed.") and a trailing "etc." list that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request proxy) with flags and a --json machine-readable pattern; minor gaps exist around how to obtain CONNECTION_ID end-to-end.	4 / 5
Workflow Clarity	The connection setup is clearly sequenced with explicit state branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), --wait polling, and "skip to Step 2" checkpoints; minor validation gaps remain for the batch-capable actions (bulk campaigns) which lack an explicit pre-send verification step.	4 / 5
Progressive Disclosure	Single-file skill with no bundle directories, well-organized into Overview, Working with, Popular actions, and Best practices sections; the 14-row inline Popular actions table is sizable content that could be split into a reference file, leaving minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

62%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 explicitly covers both what and when and is anchored by a distinctive brand name, but it leans on a single generic verb and a somewhat mismatched entity list while omitting the SMS/messaging trigger terms users would naturally say.

Suggestions

Replace the generic verb "Manage" with concrete Dexatel actions (e.g. "Send SMS, Viber, and WhatsApp messages, verify phone numbers, manage sender IDs and contacts").

Add natural trigger terms users say ("SMS", "messaging", "OTP", "verification", "HLR lookup") alongside the brand name.

Reconcile the entity list with the actual Dexatel API (SMS/Balance/Sender ID shown in the body) instead of generic CRM nouns like Persons and Deals.

Dimension	Reasoning	Score
Specificity	Quotes a single generic verb ("Manage") applied to a list of nouns ("Persons, Organizations, Deals, Leads, Projects, Activities and more"), naming the domain and several entities but not distinct concrete actions; the "and more" hedge signals incomplete coverage.	3 / 5
Completeness	Explicitly answers both what ("Manage Persons, Organizations, Deals...") and when ("Use when the user wants to interact with Dexatel data"), but the when clause is narrow and could be more specific about the SMS/messaging use cases.	4 / 5
Trigger Term Quality	Provides relevant brand triggers ("Dexatel", "interact with Dexatel data") but omits the natural phrases users actually say for this product (SMS, messaging, OTP, verification, voice), missing common synonyms and variations.	3 / 5
Distinctiveness Conflict Risk	The brand name "Dexatel" is highly distinctive and unlikely to fire for the wrong skill, though the listed CRM-style entities (Persons, Deals, Leads) create minor overlap risk with generic CRM/contact skills and mismatch the actual SMS product.	4 / 5
	Total	14 / 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/dexatel/SKILL.md
Commit: f484c82

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