Name: msg91
Rating: 55.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

msg91

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

Quality

62%

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/msg91/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 strong, executable guide with a clear connection workflow and concrete commands, held back mainly by minor verbosity and marketing-flavored prose. It is well-structured and largely copy-paste ready.

Suggestions

Trim explanatory/marketing prose such as "so you can focus on the integration logic rather than auth plumbing" and the "Developers and businesses use it..." sentence to respect Claude's existing knowledge.

Make the CONNECTION_ID placeholder explicit (e.g. show how to capture it from the `connection ensure --json` output) so the run/search commands are fully end-to-end executable.

Consider moving the proxy flags reference table into a references file to keep SKILL.md a lean overview, since the skill already exceeds ~140 lines.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the marketing-style "so you can focus on the integration logic rather than auth plumbing" and the general-purpose description of who uses MSG91, which Claude already knows.	3 / 5
Actionability	It provides copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with a clear flags table for proxying, with only minor gaps such as unresolved CONNECTION_ID placeholders.	4 / 5
Workflow Clarity	The install → authenticate → connect → wait → search → run sequence is clear with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a polling feedback loop, though a couple of transitions are implicit.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references, and the proxy/action material is reasonably placed inline; there are no bundle files, and a few sections (e.g. the proxy flags) could arguably live in a reference.	4 / 5
	Total	15 / 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 is functional with an explicit "Use when" trigger and a distinct product name, but its action list is generic and it omits the concrete capabilities (SMS, email, voice) that would make it sharper. Tightening the verbs and naming MSG91's actual features would lift specificity and trigger coverage.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete MSG91 capabilities such as sending SMS/email/voice, managing contacts and templates, and running campaigns.

Expand the trigger clause to mention the natural terms users say, e.g. "Use when the user wants to send SMS, email, or voice messages via MSG91, or manage MSG91 contacts and templates."

Keep the explicit "Use when..." clause but make the "when" more specific to reduce overlap with generic data-management skills.

Dimension	Reasoning	Score
Specificity	The description names the MSG91 domain and lists three actions ("Manage data, records, and automate workflows"), but the actions are generic and abstract rather than concrete, matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both a "what" (MSG91 integration, managing data/records/workflows) and an explicit "when" ("Use when the user wants to interact with MSG91 data") are present, though the "when" clause is somewhat generic.	4 / 5
Trigger Term Quality	It surfaces the natural product name "MSG91" and the trigger phrase "interact with MSG91 data", but offers no synonyms or variations (e.g. SMS, email, voice), so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The named product "MSG91" gives it a clear niche with minimal conflict risk, but the generic action verbs could overlap slightly with other communication or data-management skills.	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/msg91/SKILL.md
Commit: f484c82

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