Name: bulkgate
Rating: 55.2 (1 reviews)
Author: membranedev

bulkgate

BulkGate integration. Manage data, records, and automate workflows. Use when the user wants to interact with BulkGate 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/bulkgate/SKILL.md

Quality

Content

68%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 copy-paste Membrane CLI commands and a strong connection-state feedback loop, but it opens with unnecessary marketing prose and, critically, sends bulk SMS without any pre-send validation. Structure is clean and self-contained with no bundle files to navigate.

Suggestions

Trim the opening "BulkGate is a platform..." paragraph to one line; Claude already knows what SMS platforms are.

Add a pre-send validation checkpoint before bulk/promotional SMS, e.g. run check-credit-balance and confirm recipient count with the user before executing send-promotional-sms.

Move the proxy-flags option table and popular-actions reference into a separate references file so the SKILL.md overview stays a lean entry point.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean executable commands and tables, but the opening paragraph explaining what BulkGate is ("a platform that provides SMS messaging solutions... used by businesses of all sizes") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready commands for every stage (install, login, connection ensure, action list/run with JSON input, proxy requests) plus a popular-actions table with concrete keys, fully covering the common cases.	5 / 5
Workflow Clarity	The connection-setup sequence is well ordered with explicit state feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR polling), but the skill drives batch/destructive operations (bulk promotional SMS) with no pre-send validation step, so the batch guideline caps workflow clarity at 3.	3 / 5
Progressive Disclosure	The skill is a single self-contained file (no bundle files present) organized under clear headers (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices), giving good structure with only minor organization gaps and no nested references.	4 / 5
	Total	15 / 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 includes an explicit "Use when" trigger and names the specific product, but its capability list is generic and it fails to surface the SMS/messaging keywords users would naturally invoke. It is adequate for routing yet undersells and under-specifies the actual domain.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete SMS actions, e.g. "Send promotional and transactional SMS, check credit balance, and perform HLR/number lookups via BulkGate."

Add natural trigger keywords and synonyms so users' phrasing matches, e.g. "Use when the user wants to send SMS messages, check SMS credit, or do number/HLR lookups via BulkGate."

Mention multi-channel messaging (SMS, Viber, RCS, WhatsApp) to sharpen distinctiveness from generic data-integration skills.

Dimension	Reasoning	Score
Specificity	The description names the BulkGate domain but its actions ("Manage data, records, and automate workflows") are entirely generic and never mention concrete SMS-specific capabilities, matching the "names the domain but actions are minimal or generic" anchor.	2 / 5
Completeness	Both a "what" ("BulkGate integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with BulkGate data") are present, but the trigger clause is generic and could be more specific, fitting the "both present, when could be more explicit" anchor.	4 / 5
Trigger Term Quality	It surfaces the relevant product keyword "BulkGate" but omits the natural terms a user would actually say ("SMS", "send a text", "messaging", "notifications"), so keyword coverage has the right domain term yet misses common variations and synonyms.	3 / 5
Distinctiveness Conflict Risk	The named product "BulkGate" gives the skill a distinct niche with low conflict risk, but the generic "manage data / records / workflows" phrasing leaves minor overlap with other data-integration skills rather than a fully distinct trigger set.	4 / 5
	Total	13 / 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/bulkgate/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.