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

infobip

Infobip integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with Infobip 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/infobip/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 body is highly actionable with complete, executable CLI commands and a real connection-state feedback loop, supported by good section organization. Its main drag is conciseness: an explanatory intro, a redundant overview tree, and filler lines add tokens Claude does not need.

Suggestions

Cut the opening "Infobip is a cloud communications platform..." paragraph and the "Use action names and parameters as needed" filler; Claude already knows what Infobip is.

Collapse the flat "Infobip Overview" tree (which repeats "Report" under every channel) into the more useful "Popular actions" table, or move it to a references file to reduce inline noise.

Label the workflow steps explicitly (e.g. "Step 1: Connect", "Step 2: Discover actions", "Step 3: Run") so the current "skip to Step 2" reference has a clear target.

Dimension	Reasoning	Score
Conciseness	The core content is efficient and command-focused, but the opening paragraph explaining what Infobip is, the low-signal "Infobip Overview" tree, and the filler line "Use action names and parameters as needed" add unnecessary explanation Claude already knows.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy, plus an 18-row table of real action keys and a full proxy-flag table covering the common cases.	5 / 5
Workflow Clarity	There is a clear connect→discover→run sequence with a genuine polling feedback loop (BUILDING/READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the dangling "Step 2" reference and the absence of a pre-send confirmation step for outward-facing message actions are minor validation gaps.	4 / 5
Progressive Disclosure	Sections are well-organized with clear headers and no nested references, but the skill is a single self-contained file with a sizable inline actions table that could be externalized, so content is not fully "appropriately split."	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 has both a clear capability statement and an explicit "Use when..." trigger, anchored by the Infobip brand, but it relies on one generic verb and omits the messaging-channel keywords that match real user requests. Tightening the actions and triggers would raise it from mid-range to strong.

Suggestions

Replace the single generic verb "Manage" with distinct concrete actions that match the skill's real capabilities, e.g. "Send SMS, WhatsApp, email, and voice messages; verify 2FA PINs; manage contacts and numbers."

Add the natural trigger terms users actually say — "SMS", "WhatsApp", "email", "voice", "2FA/OTP" — instead of relying only on the generic phrase "interact with Infobip data".

Make the "when" clause more specific, e.g. "Use when the user wants to send messages, validate phone numbers, or work with Infobip communications APIs.", and reconcile it with the entities listed so the description reflects the messaging focus shown in the body.

Dimension	Reasoning	Score
Specificity	It names the domain and several concrete objects ("Persons, Organizations, Deals, Leads, Projects, Activities"), but applies a single generic verb ("Manage") rather than listing several distinct actions, so it sits at anchor 3 rather than 4.	3 / 5
Completeness	It gives a clear "what" ("Manage Persons, Organizations, Deals, Leads, Projects, Activities and more") and an explicit "Use when the user wants to interact with Infobip data" clause, but the trigger is generic rather than concrete.	4 / 5
Trigger Term Quality	The brand term "Infobip" and several entity nouns are present, but the description omits the messaging-channel keywords users actually say (SMS, WhatsApp, email, voice, 2FA/OTP), missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "Infobip" brand name in both the what and when clauses makes it largely distinct, though the generic CRM-style entities (Persons, Deals, Leads) create minor overlap risk with CRM skills.	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/infobip/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.