CtrlK
BlogDocsLog inGet started
Tessl Logo

engagebay

EngageBay integration. Manage Persons, Organizations, Deals, Leads, Projects, Activities and more. Use when the user wants to interact with EngageBay data.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/engagebay/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A highly actionable, well-structured CLI integration guide with concrete commands and a clear connection state machine. Its weaknesses are the lack of validation/confirmation guidance around destructive delete operations (capping workflow clarity) and a small amount of introductory padding.

Suggestions

Add a validation/confirmation checkpoint before destructive operations: e.g., instruct Claude to confirm the target ID with the user and verify via a get-* call before running delete-contact/delete-company/delete-deal, then re-check afterward.

Trim the opening marketing paragraph ("EngageBay is an integrated marketing, sales, and service automation platform... Users include marketing teams...") since it restates background Claude already knows.

Optionally move the 20-row Popular actions table into a references/ file (e.g. ACTIONS.md) and link to it, keeping only a few key examples inline in SKILL.md.

DimensionReasoningScore

Conciseness

The bulk is lean, executable CLI guidance, but the opening marketing paragraph ("EngageBay is an integrated marketing, sales, and service automation platform... Users include marketing teams, sales representatives...") explains context Claude largely already knows and could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready `membrane` commands with real flags and `--json` examples, a concrete popular-actions table with action keys, and a proxy-options table covering the common cases.

5 / 5

Workflow Clarity

The connection flow is well sequenced with a state machine (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and polling checkpoints, but the listed destructive delete-* actions have no validation or confirmation guidance, which caps this dimension at 3 per the rubric.

3 / 5

Progressive Disclosure

Well-organized into clear ## sections in a single file with no nested or broken references; the inline 20-row actions table is reference material that could optionally live in a separate file, a minor organization gap rather than a structural problem.

4 / 5

Total

16

/

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.

A concise, third-person description that names the product and many concrete entity types and includes an explicit Use-when trigger. It is clearly distinct from other skills; the main gap is the somewhat generic when-clause and use of "Persons" rather than EngageBay's native "contacts" terminology.

DimensionReasoningScore

Specificity

Enumerates many concrete entity types ("Persons, Organizations, Deals, Leads, Projects, Activities") rather than vague language, though the single verb "Manage" is shared across them, leaving minor coverage gaps signalled by "and more".

4 / 5

Completeness

Explicitly answers both what ("Manage Persons, Organizations, Deals, Leads, Projects, Activities and more") and when ("Use when the user wants to interact with EngageBay data"), but the when-clause is fairly generic and could name concrete tasks to reach a 5.

4 / 5

Trigger Term Quality

Includes the natural product name "EngageBay" plus entity keywords users would say and an explicit "Use when the user wants to interact with EngageBay data" trigger, but misses common synonyms such as "contacts" (EngageBay's actual term) versus "Persons".

4 / 5

Distinctiveness Conflict Risk

The "EngageBay" product name gives it a clear, distinct niche with minimal overlap risk against other skills' triggers.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.