Name: mailbox-power
Rating: 62.4 (1 reviews)
Author: membranedev

mailbox-power

Mailbox Power integration. Manage Persons, Organizations, Deals, Pipelines, Activities, Notes and more. Use when the user wants to interact with Mailbox Power data.

Quality

73%

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/mailbox-power/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 concrete CLI commands and a solid connection workflow, but it is padded with a marketing paragraph and a long entity list, and lacks validation checkpoints for destructive action/proxy operations. Organization is good for a single-file skill.

Suggestions

Remove the opening SaaS/marketing paragraph and trim or relocate the 30-item entity bullet list to cut tokens that do not aid execution.

Add an explicit validation checkpoint for destructive proxy/action calls (e.g., 'For -X DELETE, confirm the target id and inspect the response output/error field before proceeding') to lift workflow clarity above the cap.

Fix the 'Popular actions' section so it lists representative actions or remove it to eliminate the duplicated search-command guidance.

Dimension	Reasoning	Score
Conciseness	The CLI command guidance is mostly efficient, but the opening marketing paragraph about who uses Mailbox Power and the ~30-item bullet list of entity types add unnecessary tokens Claude does not need, and the action-list command is stated twice.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands covering the common workflow (install, login, connection ensure, polling, action list/run, proxy) with a clear flags table, matching the comprehensive executable anchor.	5 / 5
Workflow Clarity	The connection setup is well sequenced with a state-handling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the action-running and proxy steps support destructive methods (e.g. DELETE) with no validation or verification checkpoint, capping this skill at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	A single self-contained file with clear section headers and no nested references; structure is good with only minor organization gaps such as the 'Popular actions' section that repeats the search command instead of listing actions.	4 / 5
	Total	15 / 20 Passed

Description

78%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 is clear and distinct, naming a specific product and several concrete entities plus an explicit 'Use when' trigger. It stops short of anchor 5 because the action verb is generic, 'and more' is a mild over-claim, and the trigger guidance is a single phrase rather than varied concrete triggers.

Suggestions

Replace the generic 'Manage' with two or three distinct concrete verbs (e.g., 'Create, update, and query Persons, Organizations, Deals...') to lift specificity toward anchor 5.

Drop the 'and more' over-claim and expand the trigger clause with concrete user phrases (e.g., 'Use when the user wants to manage Mailbox Power contacts, deals, or pipelines').

Dimension	Reasoning	Score
Specificity	Lists several concrete managed entities ('Persons, Organizations, Deals, Pipelines, Activities, Notes'), giving multiple specific capabilities, though the single generic verb 'Manage' plus the vague 'and more' keep it just below the comprehensive-anchor 5.	4 / 5
Completeness	Provides a clear 'what' (Mailbox Power integration managing named entities) and an explicit 'when' ('Use when the user wants to interact with Mailbox Power data'), but the trigger is a single phrase rather than the multiple concrete trigger phrases that define anchor 5.	4 / 5
Trigger Term Quality	Includes the natural product name 'Mailbox Power' and entity keywords users would say (Deals, Pipelines, Notes), but offers few synonyms or variations beyond the single product-centric trigger phrase.	4 / 5
Distinctiveness Conflict Risk	Targets a specific named SaaS product ('Mailbox Power') with distinct product-scoped triggers, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	17 / 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/mailbox-power/SKILL.md
Commit: f484c82

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