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

bigmailer

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

Quality

Content

63%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 actionable and well-sequenced with real checkpoints around connection state, but it opens with unnecessary product marketing and inlines a large reference table that would benefit from a separate file.

Suggestions

Cut or condense the opening marketing paragraph so the skill starts with what to do, not what BigMailer is.

Move the "Popular actions" table into a separate reference file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Reconcile the "#### 1b" heading against the "Step 2" references so the connection workflow numbering is consistent.

Dimension	Reasoning	Score
Conciseness	The opening marketing paragraph ("BigMailer is an email marketing platform designed for businesses... cost-effective solution with advanced segmentation") explains the product rather than instructing Claude; the remainder is lean with executable commands, so mostly efficient with some unnecessary padding.	3 / 5
Actionability	Provides copy-paste ready commands throughout (membrane login, membrane connection ensure, membrane action list/run, membrane request) with flags; minor placeholders like CONNECTION_ID and actionId keep it from a 5.	4 / 5
Workflow Clarity	Clear install→auth→connect→poll→search→run sequence with state-based checkpoints (READY skip, BUILDING poll, CLIENT_ACTION_REQUIRED feedback, error handling); minor gaps such as the inconsistent "1b"/"Step 2" labeling keep it from a 5.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in one ~187-line file; sections are well-organized but the large "Popular actions" reference table is bulk content that would be better placed in a separate one-level-deep reference file.	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 answers both what and when in third person, anchored by a distinctive product name, but the capability verbs and trigger terms are generic and lack the concrete vocabulary (campaigns, lists, contacts) users would naturally say.

Suggestions

Replace generic verbs with concrete BigMailer capabilities, e.g. "Create and manage campaigns, mailing lists, segments, and contacts."

Expand the Use-when clause with natural trigger phrases: "Use when the user wants to manage BigMailer email campaigns, lists, contacts, or automations."

Add file/extension or feature synonyms users say (e.g. email marketing, bulk/transactional campaigns) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the BigMailer domain and lists a few action verbs ("Manage data, records, and automate workflows"), but the nouns "data" and "records" are generic rather than concrete capabilities; not below a 2 because multiple actions are named.	3 / 5
Completeness	Provides both a "what" (BigMailer integration; manage data, records, workflows) and an explicit "Use when" trigger, but the when-clause is generic; not a 5 because the trigger phrases are not concrete or varied.	4 / 5
Trigger Term Quality	Includes the strong proper-noun trigger "BigMailer" and the phrase "interact with BigMailer data", but omits natural synonyms users would say (email marketing, campaigns, mailing lists, contacts).	3 / 5
Distinctiveness Conflict Risk	"BigMailer integration" is a clearly named niche with minimal conflict risk; the generic verbs keep it from a 5 by allowing slight overlap with other data-management 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/bigmailer/SKILL.md
Commit: f484c82

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