Name: budget-insight
Rating: 55.2 (1 reviews)
Author: membranedev

budget-insight

Budget Insight integration. Manage data, records, and automate workflows. Use when the user wants to interact with Budget Insight 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/budget-insight/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 is a well-structured, command-rich guide with executable Membrane CLI examples and a genuine connection-state feedback loop. Its main weaknesses are promotional/background padding and an undefined 'Step 2' reference that breaks the otherwise clear workflow sequence.

Suggestions

Trim the marketing intro and promotional phrases ('so you can focus on the integration logic rather than auth plumbing') to assume Claude's competence.

Resolve the dangling 'Step 2' reference by numbering the main flow (1. Install, 2. Authenticate, 3. Connect, 4. Discover actions, 5. Run) and aligning the '1b' subsection labels.

Standardize on one invocation form ('membrane' vs 'npx @membranehq/cli') or explain when each is required.

Dimension	Reasoning	Score
Conciseness	Mostly command-focused and efficient, but the marketing-style intro ('helps users track their spending... achieve their financial goals') and promotional phrasing ('so you can focus on the integration logic rather than auth plumbing', 'burn less tokens') add padding Claude does not need.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection, action search/run, and proxy with a full flag table; minor gaps from placeholder values and inconsistency between 'membrane' and 'npx @membranehq/cli' invocations.	4 / 5
Workflow Clarity	A clear implicit sequence (install → auth → connect → search → run → proxy) with a real feedback loop on connection state (poll again after user action), but the dangling 'skip to Step 2' reference is undefined and the flow is not explicitly numbered.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Overview, Install, Auth, Connecting, Actions, Proxy, Best practices) in a single file with no nested references; no bundle files exist, and the single-file structure is appropriate for a CLI integration skill.	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 third-person, names the product niche, and includes an explicit Use-when trigger, but its capability list is generic ('manage data, records, automate workflows') rather than concrete. It is clearly distinguishable yet light on specificity and trigger variations.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions, e.g. 'List bank transactions, categorize spending, manage budgets and connections'.

Broaden the trigger with natural user phrases and synonyms, e.g. 'Use when the user wants to track spending, manage Budget Insight accounts, or automate Budget Insight workflows.'

Tighten the 'when' clause to name specific intents (transactions, budgets, categories) so it triggers more reliably.

Dimension	Reasoning	Score
Specificity	Names the domain ('Budget Insight integration') but the actions — 'Manage data, records, and automate workflows' — are minimal and generic rather than concrete capabilities.	2 / 5
Completeness	Explicitly answers both what (integration/manage workflows) and when ('Use when the user wants to interact with Budget Insight data'), though the 'what' is generic and the when could be more specific.	4 / 5
Trigger Term Quality	Includes the relevant keyword 'Budget Insight data' in the trigger clause, but misses common variations or synonyms a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	Names a specific product ('Budget Insight') giving it a clear niche and low conflict risk, though the generic 'manage data/records' phrasing creates minor overlap with related 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/budget-insight/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.