Name: wealthbox
Rating: 56.8 (1 reviews)
Author: membranedev

wealthbox

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

Quality

65%

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/wealthbox/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 content is a well-structured, mostly executable guide to driving Wealthbox via the Membrane CLI, with a clear connection-state workflow and feedback loop. It is held back by mild over-explanation in the intro, an empty 'Popular actions' section, and an undefined 'Step 2' cross-reference.

Suggestions

Trim the introductory paragraph about what Wealthbox/financial advisors are and the 'focus on integration logic' commentary to assume Claude's competence.

Either populate 'Popular actions' with concrete example action ids or remove the heading to avoid an empty section.

Clarify the step numbering — define 'Step 2' explicitly or relabel '1b' so the connect → use workflow reads as a coherent sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening paragraph ('Wealthbox is a CRM specifically designed for financial advisors...') and phrases like 'so you can focus on the integration logic rather than auth plumbing' add explanation Claude does not strictly need.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action list/run, and proxy with flag tables, but the 'Popular actions' heading lists no actual actions and placeholders (CONNECTION_ID, actionId) are never concretized with an example.	4 / 5
Workflow Clarity	There is a clear install → auth → connect → poll → search → run sequence with explicit state-based checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, though the 'Step 2' reference is never explicitly defined and '1b' numbering is inconsistent.	4 / 5
Progressive Disclosure	The single SKILL.md is well-organized into navigable sections (Overview, Working with Wealthbox, Connecting, Searching, Running actions, Proxy, Best practices) with no nested references, though the empty 'Popular actions' section is a minor organization gap.	4 / 5
	Total	15 / 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 clearly identifies the Wealthbox niche and includes an explicit 'Use when' trigger, but the capability list ('Manage data, records, and automate workflows') is generic rather than naming concrete Wealthbox actions. Tightening the action verbs and adding a few natural synonyms would lift specificity and trigger coverage.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Wealthbox capabilities such as 'create and update contacts, tasks, and projects'.

Add natural trigger synonyms users might say, e.g. 'Use when the user wants to manage Wealthbox contacts, tasks, projects, or CRM records.'

Make the 'when' clause more task-specific so it is distinguishable from a generic data-management skill.

Dimension	Reasoning	Score
Specificity	Names the domain (Wealthbox) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic ('manage data') rather than concrete Wealthbox-specific capabilities, so it is not comprehensive.	3 / 5
Completeness	It has both a 'what' ('Wealthbox integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with Wealthbox data.'), though the 'when' could be more specific about which tasks warrant the skill.	4 / 5
Trigger Term Quality	'Wealthbox' and 'interact with Wealthbox data' are natural terms a user would say, but there are no synonyms or variations (e.g. CRM, contacts, advisor), leaving common phrasings uncovered.	3 / 5
Distinctiveness Conflict Risk	'Wealthbox' is a distinct proper-noun niche with minimal conflict risk against other skills, but the generic 'manage data, records' phrasing leaves minor overlap with general 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/wealthbox/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.