Name: engage
Rating: 56.8 (1 reviews)
Author: membranedev

engage

Engage integration. Manage Organizations, Pipelines, Users, Filters. Use when the user wants to interact with Engage data.

Quality

65%

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/engage/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.

This is a highly actionable, well-structured CLI integration skill whose main connection workflow has strong validation checkpoints. Its weaknesses are an unnecessary introductory/marketing paragraph and a lack of verification guidance before destructive user actions.

Suggestions

Cut the opening marketing paragraph and the cryptic Engage Overview bullets; Claude can infer what Engage is, and those lines add no executable value.

Add a verification/confirmation checkpoint before destructive actions, e.g. confirm the target user/account IDs with the user before running merge-users, remove-user-from-account, or convert-to-account.

Consider moving the Popular actions catalog and proxy flag table into a references file (e.g. ACTIONS.md) and linking from the body to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command documentation, but the opening marketing paragraph ("helps businesses build stronger relationships... customer success teams use Engage to onboard...") and the cryptic Engage Overview bullets explain context Claude can infer or cannot use, so it could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for the full path (install, login, connection ensure, action list/run with --input JSON, request proxy) plus a concrete popular-actions table and a flags table, covering the common cases executably.	5 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state checkpoints and feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED, check CONFIGURATION_ERROR), but running destructive actions like merge-users, remove-user-from-account, or convert-to-account has no verification step, which caps this dimension at 3.	3 / 5
Progressive Disclosure	The body is organized into clear, well-signaled sections with no nested references, though the action catalog and proxy-flag tables are inlined rather than split into a separate reference file.	4 / 5
	Total	15 / 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 is third-person, covers what and when, and names a distinct product niche, but its actions and triggers stay generic. Tightening the verb and adding task-oriented trigger phrases would lift specificity and trigger quality.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create and merge users, manage organizations and pipelines, track events."

Expand the trigger clause with natural task phrases: "Use when the user wants to onboard users, manage organizations/pipelines, or track events in Engage."

Add the file or entity synonyms users actually say (e.g. contacts, accounts) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Engage domain and several concrete entities ("Organizations, Pipelines, Users, Filters") but applies only the generic verb "Manage" rather than specific actions like create/merge/track, so it sits at the domain-plus-minimal-actions level.	3 / 5
Completeness	It answers both what ("Manage Organizations, Pipelines, Users, Filters") and when via an explicit "Use when" clause, but the when-condition is generic rather than listing concrete trigger phrases, keeping it just below a 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Engage data" surfaces the product name but relies on the generic phrase "interact with Engage data," missing natural task-oriented synonyms (e.g., onboarding users, tracking events, merging contacts).	3 / 5
Distinctiveness Conflict Risk	Anchoring on the named product "Engage" gives it a clear niche with low conflict risk, though the entity terms (Organizations, Pipelines, Users) overlap somewhat with general CRM/messaging 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/engage/SKILL.md
Commit: f484c82

Reviewed: 4 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.