Name: wire2air
Rating: 56.00000000000001 (1 reviews)
Author: membranedev

wire2air

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

Quality

63%

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

Quality

Content

65%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, copy-paste Membrane CLI commands and a clear connection lifecycle, but it pads orientation prose, repeats the action-discovery guidance, and omits validation/verification checkpoints for destructive or batch API operations. Splitting reference-heavy detail into bundled files would improve progressive disclosure.

Suggestions

Add explicit validation/verify steps before destructive or batch operations, e.g. dry-run or GET-before-mutate and a confirm checkpoint for `membrane request ... -X DELETE` / `action run` mutations.

Remove redundant orientation and the duplicate "Popular actions" discovery block; consolidate action-search guidance into one section to tighten token efficiency.

Extract the proxy flag table and best-practices detail into a bundled reference file (e.g. references/proxy.md) and link to it from the body, with one-level-deep, clearly signaled references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with runnable CLI commands, but includes unnecessary orientation ("Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic") and a redundant Popular-actions section that repeats the action list/search guidance.	3 / 5
Actionability	Commands are fully executable and copy-paste ready (install, login, connection ensure, action list/run, request proxy), with concrete flag tables and a worked --input JSON example covering the common cases.	5 / 5
Workflow Clarity	A rough connect→search→run sequence exists with state handling, but destructive/batch operations (action run, proxy POST/PUT/DELETE) lack validation or verify-then-proceed checkpoints; the cap for batch/destructive ops without validation applies.	3 / 5
Progressive Disclosure	The body is a single inline monolith with section headers but no external reference files (none present in references/scripts/assets); the API and best-practices detail that could live in separate files is all inlined and not clearly signaled.	3 / 5
	Total	14 / 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 names the domain and includes an explicit use-when trigger, satisfying both the 'what' and 'when' requirements, but its capability list is generic rather than reflecting Wire2Air's actual feature set. Tightening the actions to concrete Wire2Air operations (campaigns, contacts, SMS) would raise specificity and trigger quality.

Suggestions

Replace generic "Manage data, records, and automate workflows" with concrete Wire2Air actions, e.g. "Send and schedule SMS campaigns, manage contacts and lists, and automate messaging workflows."

Add natural user trigger phrases and file-type/keyword synonyms, e.g. "Use when the user wants to send SMS, manage contact lists, or automate Wire2Air messaging campaigns."

Keep the third-person voice consistent and avoid the comma-separated abstractions that blur the skill's niche.

Dimension	Reasoning	Score
Specificity	Names the domain (Wire2Air integration) and lists actions ("Manage data, records, and automate workflows") but these are generic categories rather than concrete capabilities specific to Wire2Air's API surface.	3 / 5
Completeness	It states what the skill does ("Manage data, records, and automate workflows") and includes an explicit "Use when the user wants to interact with Wire2Air data" trigger clause, though the 'what' is somewhat generic.	4 / 5
Trigger Term Quality	"Wire2Air" and "data"/"records" appear, but the natural user phrasing around SMS campaigns, contacts, lists, or numbers is absent; only the brand name and a generic trigger clause are present.	3 / 5
Distinctiveness Conflict Risk	The Wire2Air brand name provides a clear niche with distinct triggers, though the generic "manage data" phrasing creates minor overlap risk with other data-integration 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/wire2air/SKILL.md
Commit: f484c82

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