CtrlK
BlogDocsLog inGet started
Tessl Logo

voodoo-sms

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/voodoo-sms/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, action-dense integration guide with concrete CLI commands and a real connection-state feedback loop. Its main weaknesses are minor: a few padded sentences, placeholder-driven action examples, and inconsistent step numbering between the connection and action stages.

DimensionReasoningScore

Conciseness

The body is mostly lean, built from executable commands, a flag table, and terse state-machine guidance, with only minor padding such as "so you can focus on the integration logic rather than auth plumbing" and the audience sentence about who uses Voodoo SMS.

4 / 5

Actionability

It provides concrete, copy-pasteable commands throughout (membrane login, connection ensure, action list/run, request) with flags and JSON output examples, but the action-run examples rely on placeholders (CONNECTION_ID, actionId, QUERY) rather than a fully concrete worked example.

4 / 5

Workflow Clarity

There is a clear install → authenticate → connect → search → run sequence with a genuine feedback loop around connection state (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), though step numbering is inconsistent ("skip to Step 2" with no Step 2 header; a "1b" subsection) and running actions lacks an explicit pre-flight validation gate.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections with no nested references and no bundle files present; dynamic action discovery via `membrane action list` avoids inlining a large catalog, but the "Popular actions" section partially duplicates "Searching for actions" and the step numbering is slightly off.

4 / 5

Total

16

/

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 uses third person and includes an explicit "Use when" trigger, but its capability list is generic boilerplate rather than concrete SMS-specific actions. Distinctiveness is rescued by the named product, yet trigger terms miss common synonyms like "SMS" and "text messages."

Suggestions

Replace generic actions with concrete SMS capabilities, e.g. "Send and schedule SMS campaigns, manage contacts and lists, and review delivery reports."

Add natural trigger terms users would say, such as "SMS," "text messages," "SMS campaigns," or "bulk SMS," alongside "Voodoo SMS."

Make the "when" clause more specific, e.g. "Use when the user wants to send or manage SMS messages, campaigns, or contacts via Voodoo SMS."

DimensionReasoningScore

Specificity

The description names the domain ("Voodoo SMS integration") but its actions — "Manage data, records, and automate workflows" — are generic abstractions rather than concrete SMS capabilities like sending messages, managing campaigns, or contacts/lists.

2 / 5

Completeness

Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" trigger ("Use when the user wants to interact with Voodoo SMS data") are present, but both are generic rather than concrete, fitting the anchor where each could be more specific.

4 / 5

Trigger Term Quality

It surfaces the primary natural keyword ("Voodoo SMS") via "Use when the user wants to interact with Voodoo SMS data," but omits common synonyms users would actually say such as "SMS," "text messages," "campaigns," or "contacts."

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the named product "Voodoo SMS" gives it a clear niche with minimal conflict risk, though the boilerplate "manage data, records, and automate workflows" phrasing overlaps with sibling Membrane integration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.