Name: message-bird
Rating: 60.8 (1 reviews)
Author: membranedev

message-bird

Message Bird integration. Manage Persons, Organizations, Pipelines, Users, Goals, Filters. Use when the user wants to interact with Message Bird data.

Quality

71%

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

Quality

Content

76%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 highly actionable with concrete CLI commands and a solid connection-state workflow, but it loses workflow-clarity points because destructive operations lack validation steps, and it carries minor background over-explanation. Structure is good for a single-file skill though some reference material could be split out.

Suggestions

Add a validation/confirmation checkpoint before destructive actions, e.g. verify the contact ID via get-contact and confirm with the user before running delete-contact/delete-message.

Trim the opening background paragraph and the "focus on the integration logic" commentary; lead directly with the install/auth commands.

Fix the dangling "Step 2" reference ("skip to Step 2") since no Step 2 is labeled, and clean up the "1b" heading that has no "1a"/"Step 1" counterpart.

Dimension	Reasoning	Score
Conciseness	The body is largely command-driven and efficient, but the opening paragraph ("Message Bird is a cloud communications platform...") and phrases like "so you can focus on the integration logic rather than auth plumbing" are mild over-explanation Claude does not need.	4 / 5
Actionability	It provides copy-paste-ready commands throughout (login, connection ensure, action list/run, request proxy) with real flags, a --json convention, and a Popular actions table with concrete keys covering the common cases.	5 / 5
Workflow Clarity	The connection workflow is well-sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but destructive actions (delete-contact, delete-message) appear with no validation/verification guidance, capping this dimension at 3.	3 / 5
Progressive Disclosure	Single self-contained file with clear section headers and no nested references; organization is good, though at ~155 lines the Popular actions table and proxy flag reference are candidates for a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

66%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 answers both what and when in third person and is clearly distinct, but it relies on one generic verb and the trigger phrase is product-name-only without common synonyms. Note also the listed entities appear inconsistent with Message Bird's actual objects (Contacts/Conversations/Messages) shown in the body, which weakens specificity.

Suggestions

Replace the single generic verb "Manage" with concrete actions that map to Message Bird's real objects (e.g. "Send SMS, list and create contacts, manage conversations and groups").

Expand the trigger clause with natural terms users actually say, e.g. "Use when the user wants to send SMS, manage contacts or conversations, or work with MessageBird data."

Align the listed entities with the body's actual objects (Contacts, Conversations, Groups, Messages, Templates, Webhooks) instead of Persons/Organizations/Pipelines/Goals.

Dimension	Reasoning	Score
Specificity	Names the Message Bird domain and lists several concrete objects ("Persons, Organizations, Pipelines, Users, Goals, Filters") but only offers the single generic verb "Manage", so action coverage is not comprehensive.	3 / 5
Completeness	Both "what" (manage the listed entities) and "when" (interact with Message Bird data) are present, though the "when" clause is somewhat generic rather than tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Message Bird data" includes the product name but misses common natural variations users would say (e.g. SMS, messaging, send messages).	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("Message Bird integration") with a narrow trigger ("interact with Message Bird data") gives it a clear niche with minimal overlap against other skills.	5 / 5
	Total	15 / 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/message-bird/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.