Name: maximizer
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

maximizer

Maximizer integration. Manage data, records, and automate workflows. Use when the user wants to interact with Maximizer data.

Quality

61%

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

Quality

Content

61%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 provides concrete, executable Membrane CLI commands and a well-validated connection workflow. It loses points for an unnecessary CRM overview paragraph, duplicated action-list guidance, broken step numbering, and missing validation around destructive proxy requests.

Suggestions

Remove the opening 'Maximizer CRM is a customer relationship management software...' paragraph and consolidate the 'Searching for actions' and 'Popular actions' sections to eliminate the duplicated action-list command.

Fix the step numbering (define Step 1 and Step 2 explicitly) and add a validation checkpoint before destructive proxy calls, e.g. verify the target resource exists and confirm DELETE/PUT/PATCH with the user before running `membrane request`.

Show one fully-resolved example with a real connection id and action id so the run/proxy commands are copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI documentation, but the opening CRM overview paragraph restates what Maximizer is and the 'Popular actions' section duplicates the action-list command already shown in 'Searching for actions'.	3 / 5
Actionability	Concrete, executable commands are given throughout (install, login, connection ensure/get, action list/run, request) with a flags table, though placeholders like CONNECTION_ID and actionId require substitution so it is not fully copy-paste ready.	4 / 5
Workflow Clarity	The connection setup has a clear poll/validate sequence (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is broken ('Step 2' is referenced yet never defined) and the proxy section supports destructive methods (DELETE/PUT/PATCH) with no validation, capping this at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the ~140-line body is organized into clear sections (Overview, Authentication, Connecting, Searching, Popular actions, Best practices); minor redundancy between the two action-list sections keeps it just below a 5.	4 / 5
	Total	14 / 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, names the domain, and includes an explicit 'Use when' trigger, so it answers both what and when. It is held back by generic action verbs and limited natural trigger-term coverage.

Suggestions

Replace generic verbs with concrete actions, e.g. "Create and update leads, opportunities, contacts, and cases in Maximizer, and run or search Maximizer actions."

Expand the trigger clause with natural phrasings and entity names: "Use when the user wants to manage Maximizer CRM data — leads, opportunities, customers, contacts, or cases."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Maximizer domain plus a few actions, but the verbs (manage, automate) are generic rather than concrete, matching the '1-2 concrete actions but not comprehensive' anchor.	3 / 5
Completeness	Both 'what' (Maximizer integration, manage data/records, automate workflows) and 'when' ("Use when the user wants to interact with Maximizer data") are present and explicit, though the trigger clause is single and could be more specific.	4 / 5
Trigger Term Quality	"Maximizer data" and "records" surface the brand keyword, but natural user phrasings like "sync Maximizer leads", "CRM", or entity names (leads, opportunities) are missing, so coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The named brand "Maximizer" carves a clear niche with minimal conflict risk, though the generic "manage data, records" phrasing leaves minor overlap with other CRM/data 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/maximizer/SKILL.md
Commit: f484c82

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