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

smoove

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

Quality

68%

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/smoove/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 content is highly actionable with executable commands for the entire Membrane/Smoove workflow and a strong connection-state feedback loop, but it is held back by redundant/padded sections, missing verification for destructive operations, and a broken step cross-reference. No bundle files are present, so structure relies on the single well-sectioned file.

Suggestions

Remove the duplicated "Popular actions" section (it restates the "Searching for actions" command) and trim the marketing intro and "fastest way" filler to tighten token use.

Add explicit validation/verification before destructive proxy or action calls (e.g. confirm the operation, check the response `error` field, and verify state changed as expected).

Fix the dangling "Step 2" reference (and the unlabeled 1b numbering) so the multi-step connection workflow is internally consistent.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-dense, but the opening marketing paragraph ("Smoove is a marketing automation platform..."), the duplicated "Popular actions" section that repeats the "Searching for actions" command, and filler like "This is the fastest way to get a connection" are unnecessary and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for the full workflow (install, login, connection ensure, poll, action list/run, request proxy) plus a flags table, with specific examples covering the common cases.	5 / 5
Workflow Clarity	The connection setup is well-sequenced with state checkpoints and a poll loop, but destructive proxy operations (DELETE/PUT/PATCH) and action runs lack validation/verification steps, capping the score at 3 per the rubric; a dangling "Step 2" reference also breaks the sequence.	3 / 5
Progressive Disclosure	The single file is well-organized with clear headers, code blocks, and a table, with no nested references; minor gaps are the broken "Step 2" cross-reference and reference-grade material (clientAction schema, proxy flags) kept inline rather than split out.	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 clearly states the domain and lists concrete resources with an explicit trigger clause, but the trigger phrasing is generic and the action vocabulary is limited to a single verb. It is solid but could be sharpened with natural trigger terms and more specific verbs.

Suggestions

Replace the generic trigger with concrete phrases a user would actually say, e.g. "Use when the user wants to manage Smoove contacts, campaigns, pipelines, or marketing automation data."

Vary the action verbs beyond "Manage" (e.g. "Create and update Organizations, Pipelines, Users, Goals, and Filters") to better signal specific capabilities.

Add natural synonyms/extensions users might mention (e.g. email marketing, SMS campaigns, contacts) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	"Manage Organizations, Pipelines, Users, Goals, Filters" enumerates five concrete resource types, but relies on a single generic verb ("Manage"), leaving minor gaps versus the multiple distinct actions in the anchor-5 example.	4 / 5
Completeness	It answers both "what" (Smoove integration managing five resources) and "when" (explicit "Use when..." clause), but the "when" is generic rather than concrete trigger phrases, matching the anchor-4 example.	4 / 5
Trigger Term Quality	The brand "Smoove" and the resource names supply some relevant keywords, but the only explicit trigger ("Use when the user wants to interact with Smoove data") is generic and missing natural variations like "campaigns", "contacts", or "email marketing".	3 / 5
Distinctiveness Conflict Risk	The "Smoove" brand name gives a clear niche, but generic resource terms (Pipelines, Goals, Filters, Users) create minor overlap risk with other CRM/marketing-automation 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/smoove/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.