Name: totalexpert
Rating: 52.8 (1 reviews)
Author: membranedev

totalexpert

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

Quality

59%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/totalexpert/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 content is a solid, command-heavy CLI usage guide with strong actionability and clean single-file organization. Its main weaknesses are filler prose, broken step numbering, and the absence of validation guidance for destructive proxy operations.

Suggestions

Fix the step numbering: add a labeled "1a"/Step 1 and define the referenced "Step 2", or convert the connection flow into a single numbered sequence with explicit validation checkpoints.

Add a validation/confirmation step before destructive proxy calls, e.g. confirm the method and path before running `membrane request ... -X DELETE` and verify the response status.

Trim filler — remove "Use action names and parameters as needed." and either populate "Popular actions" with actual named actions or drop the redundant discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven, but includes filler ("Use action names and parameters as needed."), an introductory paragraph explaining what a CRM is, and a "Popular actions" section that repeats the already-given discovery command instead of listing actions.	3 / 5
Actionability	It provides many concrete, executable commands (install, login, connection ensure/get, action list/run, request) with flag tables and JSON examples; minor gaps remain where placeholders like CONNECTION_ID are unsubstituted.	4 / 5
Workflow Clarity	A connection-state feedback loop is documented (poll until READY after CLIENT_ACTION_REQUIRED), but step numbering is broken (a "1b" with no "1a", and references to an undefined "Step 2"), and the proxy section enables destructive methods (DELETE/PUT) with no validation checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files are provided, so this is scored on structure: the single-file guide is well-organized into clear headed sections (Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested or buried references, leaving only minor organization gaps.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly pairs a "what" with an explicit "Use when..." trigger and names a distinctive platform, but its action verbs are generic and its trigger terms lack natural variations. It is functional but not concrete enough to score at the top of the scale.

Suggestions

Replace generic verbs with concrete Total Expert operations, e.g. "Manage contacts and loan-officer records, track opportunities, and automate marketing workflows."

Expand the trigger phrase with natural user phrasings and synonyms, e.g. "Use when the user wants to manage Total Expert contacts, opportunities, loan officers, or marketing campaigns."

Add a couple of domain-specific trigger terms (e.g. "mortgage CRM", "leads", "borrowers") so the skill surfaces for realistic user requests.

Dimension	Reasoning	Score
Specificity	The named actions are generic verbs — "Manage data, records, and automate workflows" — rather than concrete operations (no "extract", "fill", "merge"-level specifics), matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Total Expert data") are explicitly present, but the trigger clause is somewhat generic rather than listing concrete scenarios.	4 / 5
Trigger Term Quality	"Total Expert" is the dominant natural keyword a user would say, but the supporting terms ("data", "records", "workflows") are generic and lack common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	The named platform "Total Expert" gives it a clear, specific niche with low conflict risk, though the generic "manage data/records" phrasing leaves minor overlap with other CRM/data skills.	4 / 5
	Total	13 / 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/totalexpert/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.