CtrlK
BlogDocsLog inGet started
Tessl Logo

waboxapp

Waboxapp integration. Manage Organizations, Users, Filters. Use when the user wants to interact with Waboxapp data.

64

Quality

76%

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/waboxapp/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 strong, actionable integration guide with executable commands, a clear workflow, and built-in feedback loops; its main weaknesses are minor padding in the prose and slightly loose step numbering plus an all-inline structure.

Suggestions

Fix the step numbering: introduce an explicit "Step 1a"/"Step 1b" pairing or relabel the "Skip to Step 2" reference to a real, numbered heading so the sequence is unambiguous.

Trim the introductory Waboxapp description paragraph to one line, since the brand context is already conveyed by the description frontmatter and the "Official docs" link.

Consider moving the "Popular actions" table and proxy options into a short reference file (e.g. ACTIONS.md) so the main SKILL.md stays a lean overview pointing one level deep.

DimensionReasoningScore

Conciseness

The body is largely lean and command-driven with copy-paste CLI examples; only minor prose such as the opening Waboxapp description and "This is the fastest way to get a connection" could be trimmed.

4 / 5

Actionability

Provides fully executable `membrane` commands with flags, JSON output, parameter passing, and a proxy-options table, covering install, auth, connect, search, run, and proxy cases in copy-paste-ready form.

5 / 5

Workflow Clarity

A clear install→login→connect→poll→search→run sequence with explicit state branches and a retry-after-action feedback loop, but step numbering is loose ("Step 2" is referenced but unlabeled, a "1b" section appears with no "1a").

4 / 5

Progressive Disclosure

Well-organized into clear sections with no nested or buried references and a self-contained structure, but everything is inlined in a ~145-line file with no external reference split, leaving minor organization gaps.

4 / 5

Total

17

/

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 covers both what the skill does and when to use it with a distinct brand trigger, but relies on the generic verb "manage" and omits the common "WhatsApp" trigger terms users would naturally say.

Suggestions

Replace or augment the generic "Manage" verb with concrete actions (e.g., "Send messages, fetch account status, upload media") to lift specificity.

Add natural-language trigger terms users actually say, such as "WhatsApp Business" or "WhatsApp messaging", not just the brand name "Waboxapp".

Tighten the "when" clause to name concrete use cases (e.g., "Use when sending WhatsApp notifications or querying account status") rather than "interact with Waboxapp data".

DimensionReasoningScore

Specificity

"Manage Organizations, Users, Filters" lists several specific entity operations on the named Waboxapp domain, with only minor coverage gaps, though "manage" is a generic verb.

4 / 5

Completeness

Both an explicit "what" ("Manage Organizations, Users, Filters") and a "when" ("Use when the user wants to interact with Waboxapp data") are present, though the trigger phrase is fairly generic.

4 / 5

Trigger Term Quality

The brand term "Waboxapp" is present as a trigger, but the much more common user phrase "WhatsApp"/"WhatsApp Business API" and synonyms are missing, leaving keyword coverage partial.

3 / 5

Distinctiveness Conflict Risk

"Waboxapp" is a unique proper-noun brand giving the skill a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

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.