Name: builderall-mailingboss
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

builderall-mailingboss

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

Quality

66%

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/builderall-mailingboss/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 delivers executable, well-sequenced Membrane CLI guidance with strong state-checkpoint validation in the connection flow. It is efficient and actionable, with only minor labeling and organization gaps.

Suggestions

Trim the opening overview paragraph that restates what Builderall Mailingboss is, since Claude already knows this.

Fix the 'skip to Step 2' reference by explicitly labeling the post-connection step as Step 2.

Consider moving the proxy flag table and clientAction field reference into a separate reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is efficient with executable commands and minimal padding, though the opening overview paragraph ('is an email marketing automation platform...') is mild over-explanation Claude largely already knows.	4 / 5
Actionability	It provides concrete, copy-paste-ready membrane commands with documented flags across install, auth, connection, action, and proxy flows, with only minor placeholder gaps (CONNECTION_ID, actionId).	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; the only gap is an unlabeled 'skip to Step 2' reference.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections with no need for external bundle files, though it is a single inline file rather than split across references, keeping it just below a 5.	4 / 5
	Total	16 / 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 answers both 'what' and 'when' and is anchored by a distinctive brand name, but its action verbs are generic and it omits natural email-marketing trigger terms. It is adequate but could be sharpened.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete actions such as 'create email campaigns, manage subscriber lists, and trigger automation workflows'.

Add natural trigger terms users would say, e.g. 'Use when the user wants to send email campaigns, manage subscribers, or build automations in Mailingboss'.

Mention SMS marketing and automation workflows explicitly to widen natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain but the verbs are generic ('Manage data, records, and automate workflows') rather than concrete actions, matching the anchor for minimal/generic actions.	2 / 5
Completeness	It has both a 'what' clause and a 'when' clause ('Use when the user wants to interact with...'), but both are somewhat generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The brand name 'Builderall Mailingboss' is a natural keyword users would say, but it lacks common variations or synonyms like 'email campaigns', 'subscribers', or 'email lists'.	3 / 5
Distinctiveness Conflict Risk	The unique brand name 'Builderall Mailingboss' makes it mostly distinct, with only minor overlap risk against other email-marketing skills.	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/builderall-mailingboss/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.