Name: wealthengine
Rating: 55.2 (1 reviews)
Author: membranedev

wealthengine

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

Quality

62%

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/wealthengine/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 delivers concrete, executable Membrane commands and a well-sequenced connection workflow with strong error-recovery feedback loops. It loses points mainly on conciseness due to a redundant actions section and a few throwaway lines, and on minor structural inconsistencies in step numbering.

Suggestions

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated `membrane action list` command and trim tokens.

Delete the throwaway line 'Use action names and parameters as needed.' and instead show one concrete WealthEngine action invocation example once a connection is ready.

Replace the loose 'Skip to Step 2' / '1b' references with a consistently numbered step sequence (1. Install, 2. Authenticate, 3. Connect, 4. Discover & run actions) so the workflow checkpoints are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the 'Popular actions' section duplicates the 'Searching for actions' command, the line 'Use action names and parameters as needed.' is throwaway, and a few sentences of connect-flow prose could be tightened, fitting the 'mostly efficient but could be tightened' anchor rather than a 4.	3 / 5
Actionability	It provides concrete, executable commands for install, login, connection ensure, polling, action list/run, and proxy requests plus a flag table, but relies on placeholders (CONNECTION_ID, <actionId>) and dynamic discovery rather than fully copy-paste WealthEngine-specific examples, so it stops short of the 5 anchor.	4 / 5
Workflow Clarity	There is a clear install→authenticate→connect→poll→search→run sequence with explicit connection-state feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and re-poll instructions, but the 'Skip to Step 2' and '1b' numbering is inconsistent, leaving minor checkpoint gaps.	4 / 5
Progressive Disclosure	The content is organized into clearly headed sections in a single SKILL.md with no bundle files, so structure is good; the redundant 'Popular actions' vs 'Searching for actions' section and the sparse 'WealthEngine Overview' list are minor organization gaps keeping it below 5.	4 / 5
	Total	15 / 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 is clearly scoped to a named platform and includes an explicit 'Use when' trigger, satisfying both the what and when. Its main weakness is generic action language that fails to convey the concrete WealthEngine capabilities a user would actually invoke.

Suggestions

Replace generic verbs with concrete WealthEngine actions, e.g. 'Screen prospects, look up wealth profiles, and search for high-capacity donors' instead of 'Manage data, records, and automate workflows'.

Expand the trigger clause with natural user phrases such as 'Use when the user wants to look up donor wealth data, screen prospects, or query WealthEngine profiles'.

Add a file extension or product-specific keyword (e.g. 'wealth screening', 'prospect research') to broaden natural trigger coverage beyond the single brand name.

Dimension	Reasoning	Score
Specificity	It names the WealthEngine domain but the actions ('Manage data, records, and automate workflows') are generic rather than concrete WealthEngine-specific operations such as screening prospects or looking up wealth profiles, matching the score-2 anchor of minimal/generic actions.	2 / 5
Completeness	It states both a 'what' (WealthEngine integration, manage data/records/workflows) and an explicit 'when' ('Use when the user wants to interact with WealthEngine data'), but the 'when' could be more specific with concrete trigger phrases, so it is below the 5 anchor.	4 / 5
Trigger Term Quality	The only real keyword is the branded noun 'WealthEngine' plus 'interact with WealthEngine data'; there are no natural synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	WealthEngine is a named third-party platform giving it a clear, distinct niche with low conflict risk, though the generic verb phrases ('manage data, records') introduce minor overlap with adjacent data-integration 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/wealthengine/SKILL.md
Commit: f484c82

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