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

Blog Docs Log in Get started

labsmobile

LabsMobile integration. Manage SMSes, Contacts, Groups. Use when the user wants to interact with LabsMobile data.

Quality

68%

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

Quality

Content

75%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 content is an efficient, highly actionable CLI guide with a well-sequenced, validated connection workflow. Its main weakness is the absence of an explicit validation/confirmation step before batch or consequential SMS sends, which caps workflow clarity just short of excellent.

Suggestions

Add a pre-send validation checkpoint for batch/bulk SMS actions (e.g. confirm recipient count and content with the user before running send-sms) to close the workflow-clarity gap.

Include one complete 'action run' example with real input JSON and a note on parsing the 'output' field, to move actionability from mostly-executable to fully copy-paste ready.

Consider splitting the proxy flag reference and Popular actions table into a one-level-deep reference file so the SKILL.md overview stays leaner.

Dimension	Reasoning	Score
Conciseness	The body is dominated by copy-paste commands and tables with tight prose; the only mild over-explanation is the opening LabsMobile marketing paragraph, which is justified context for a niche vendor rather than concepts Claude already knows, fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) plus a Popular actions table with real action keys and a flag reference table, with only a minor gap in that no fully populated 'action run' example shows real input values and output parsing.	4 / 5
Workflow Clarity	The connect-to-ready flow is clearly sequenced with explicit validation checkpoints (polling state, branching on READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR with a poll-again feedback loop), but action execution for batch/consequential SMS sends lacks an explicit pre-send confirmation/validation step, leaving a minor validation gap at level 4 rather than 5.	4 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections (Overview, Working with LabsMobile, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and the ~150-line CLI guide is reasonably kept in one file, though it is monolithic with no one-level-deep reference files, matching 'good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	16 / 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 is concise and includes an explicit 'Use when' clause plus a named vendor, giving it solid completeness and distinctiveness. It is held back by a single generic verb and a generic trigger phrase that omit common natural terms like 'text messages'.

Suggestions

Replace the single generic verb 'Manage' with several distinct concrete actions (e.g. 'Send and schedule SMS, manage contacts and groups, check balance') to lift specificity.

Add common natural trigger terms users actually say, such as 'text messages', 'texting', or 'SMS notifications', to improve trigger-term coverage.

Tighten the 'when' clause to name concrete intents (e.g. 'Use when the user wants to send or schedule SMS, manage contacts/groups, or check LabsMobile balance') instead of 'interact with LabsMobile data'.

Dimension	Reasoning	Score
Specificity	The description names the LabsMobile domain and three concrete objects ("Manage SMSes, Contacts, Groups") but applies a single generic verb ("Manage") rather than listing several distinct actions, so it sits at the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the multi-action level 4.	3 / 5
Completeness	It states both a clear "what" ("LabsMobile integration. Manage SMSes, Contacts, Groups.") and an explicit "when" ("Use when the user wants to interact with LabsMobile data"), but the "when" clause is somewhat generic rather than naming concrete triggers, fitting the level-4 anchor where "when could be more explicit or specific".	4 / 5
Trigger Term Quality	"SMSes", "Contacts", and "Groups" are relevant keywords, but common natural variations a user would say ("text messages", "texting", "phone numbers") are absent and the trigger phrase "interact with LabsMobile data" is generic, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific vendor LabsMobile gives it a clear niche with minimal conflict risk against unrelated skills, though the generic SMS/Contacts/Groups surface leaves minor overlap risk with other messaging skills, matching 'mostly distinct; minor overlap risk'.	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/labsmobile/SKILL.md
Commit: f484c82

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