Name: smartengage
Rating: 58.4 (1 reviews)
Author: membranedev

smartengage

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

Quality

67%

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/smartengage/SKILL.md

Quality

Content

67%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 a solid, actionable guide to driving SmartEngage through the Membrane CLI, with executable commands and a clear connection workflow including error-recovery feedback. It is slightly verbose and its single-file structure leaves room for progressive disclosure.

Suggestions

Cut the marketing-platform introductory paragraph and merge the duplicated action-list instructions under "Popular actions" to reduce token overhead.

Either populate "Popular actions" with the actual common SmartEngage actions or rename the section to "Discovering actions" to avoid the misleading heading.

Move the proxy flags table and the detailed clientAction state machine into a separate reference file referenced one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the marketing-platform intro paragraph and the duplicated action-list command (in both "Searching for actions" and "Popular actions") add unnecessary tokens.	3 / 5
Actionability	Concrete copy-paste commands cover install, auth, connection, search, run, and proxy flows with a clear flags table, but the "Popular actions" heading only restates the discovery command instead of listing actual actions.	4 / 5
Workflow Clarity	A clear install→login→connect→poll→search→run sequence is present with a state-machine feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, error states), though the "Step 2"/"1b" labeling is slightly inconsistent.	4 / 5
Progressive Disclosure	Content is a single well-organized file with clear section headers and no nested references, but at ~145 lines some material (the proxy flags table, the clientAction state machine) could be split into separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

67%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 with concrete named resources and an explicit use-when clause, anchored clearly to the SmartEngage product. Its main weakness is generic trigger phrasing and incomplete resource coverage relative to the body.

Suggestions

Replace the generic "interact with SmartEngage data" trigger with concrete phrases users would say, e.g. "Use when managing SmartEngage organizations, users, contacts, sequences, or filters".

Align the listed resources with the body (Contact, Sequence, Tag, Task, Bulk Operation, Email Account, Webhook) so the description's capability list is comprehensive.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Users, Filters" lists several concrete resources with an explicit action verb, though it omits many resources surfaced in the body (Contact, Sequence, Tag, Task, etc.), leaving minor coverage gaps.	4 / 5
Completeness	It states both what ("SmartEngage integration. Manage Organizations, Users, Filters.") and when ("Use when the user wants to interact with SmartEngage data"), though the "when" clause could be more specific with concrete trigger phrases.	4 / 5
Trigger Term Quality	Relevant keywords like "SmartEngage" and "Organizations, Users, Filters" appear, but the trigger phrasing "interact with SmartEngage data" is generic and lacks natural synonyms or variations a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The named product "SmartEngage" carves a clear niche with low conflict risk, but the broad action set (Organizations, Users, Filters) could overlap with other SmartEngage-specific skills.	4 / 5
	Total	15 / 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/smartengage/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.