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

cashbuddy

Cashbuddy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cashbuddy 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/cashbuddy/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 well-structured, actionable CLI integration guide with concrete commands, but it lacks validation checkpoints for potentially destructive action/proxy calls and carries mild verbosity and a dangling step reference. Adding an explicit verify step and trimming padding prose would raise the weaker dimensions.

Suggestions

Add an explicit validation/verification step after `membrane action run` and proxy requests (e.g. inspect the `output` field and confirm counts before proceeding) to support destructive or batch operations.

Remove the dangling 'Step 2' reference or add a matching 'Step 2' heading so the connection → action workflow is unambiguous.

Trim filler sentences like 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection' to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, built around concrete CLI commands and a flags table, but includes some unnecessary prose such as "so you can focus on the integration logic rather than auth plumbing" and "This is the fastest way to get a connection" that could be trimmed. It is not a 4 because several padded explanatory sentences remain, and not a 2 because the bulk is actionable command reference rather than concept explanation.	3 / 5
Actionability	The skill provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) plus a detailed flags table, matching the anchor for mostly executable guidance with minor gaps. It does not reach 5 because placeholders like <actionId>, CONNECTION_ID, and the abstract QUERY intent require substitution and there is no fully worked end-to-end example.	4 / 5
Workflow Clarity	A clear sequence is present (install → authenticate → connect with polling states READY/BUILDING/CLIENT_ACTION_REQUIRED → search → run/proxy) and the connection-polling loop is a feedback mechanism, but `membrane action run` and proxy POST/PUT/DELETE are potentially destructive or batch operations with no validation/verification step, which caps this at 3 per the rubric. A dangling 'Step 2' reference with no matching heading adds a sequencing gap.	3 / 5
Progressive Disclosure	There are no bundle files; the single SKILL.md is organized into well-labeled sections (Overview, Working with Cashbuddy, Popular actions, Best practices) with content appropriately placed inline for a CLI integration guide, matching the good-structure anchor. It does not reach 5 because 'Popular actions' repeats the action-list command already shown under 'Searching for actions', a minor organization redundancy.	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 includes an explicit 'Use when' trigger and a product-specific niche, but its capability list is generic. Tightening the 'what' with concrete Cashbuddy actions would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete Cashbuddy capabilities, e.g. 'Create budgets, record transactions, and track savings goals' to improve specificity.

Expand trigger terms beyond 'Cashbuddy data' to the natural phrases users say, such as 'budgets', 'transactions', or 'spending', for better trigger coverage.

Keep the explicit 'Use when' clause but pair it with the concrete actions so both 'what' and 'when' are equally specific.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Cashbuddy integration") but the actions — "Manage data, records, and automate workflows" — are generic verbs rather than concrete capabilities, matching the anchor where the domain is named but actions are minimal or generic. It does not rise to 3 because no concrete actions (e.g. 'create budgets', 'list transactions') are specified.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Cashbuddy data") are present, satisfying the anchor for both being present with room for improvement. It is capped below 5 because the 'what' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with Cashbuddy data" plus the product name "Cashbuddy" give some relevant keywords, but coverage is narrow — only the single term "Cashbuddy" is really surfaced, missing common variations. It is not a 4 because the natural keyword set is thin rather than merely 'a few terms missing'.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Cashbuddy" gives it a clear niche and mostly distinct triggers with minimal conflict risk. It does not reach 5 because the generic action language ("Manage data, records") still overlaps loosely with broad data-management 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/cashbuddy/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.