Name: bud
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bud

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

Quality

73%

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/bud/SKILL.md

Quality

Content

88%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 highly actionable with copy-paste-ready CLI commands and a well-sequenced, state-validated connection workflow, kept mostly lean with only minor over-explanation and reasonable section organization given the absence of bundle files.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands and short explanations; minor over-explanation appears in the opening paragraph describing what Bud is and asides like "so you can focus on the integration logic rather than auth plumbing", but most tokens earn their place, so it is efficient rather than lean.	4 / 5
Actionability	It provides copy-paste-ready, executable commands for every common case (npm install, membrane login, connection ensure, action list/run, request) with flag tables and JSON examples, matching the 'fully executable, copy-paste ready, covers common cases' anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced (ensure -> poll --wait -> branch on state) with explicit validation via state checks (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (poll again after the user completes the action), matching the explicit-checkpoints anchor.	5 / 5
Progressive Disclosure	Content is organized into clearly signaled sections with no bundle files present so everything is appropriately inline; not a 5 because the body exceeds 50 lines and a few blocks (the proxy options table, best practices) could plausibly live in reference files.	4 / 5
	Total	18 / 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 covers both what and when with an explicit trigger clause and a Bud-specific niche, but its actions are generic rather than concrete and its trigger terms lack the natural synonyms (transactions, budgets, spending) users would actually say.

Suggestions

Replace generic actions with concrete Bud actions, e.g. "Track spending, create budgets, manage transactions, and automate finance workflows."

Expand trigger terms with natural synonyms users say, e.g. "Use when the user wants to track spending, manage budgets, or interact with Bud transactions."

Keep the description in third person (it already is) but ensure the 'Use when' clause lists concrete trigger phrases rather than the generic "interact with Bud data".

Dimension	Reasoning	Score
Specificity	Phrases like "Manage data, records, and automate workflows" name the Bud domain but use generic verbs and nouns rather than concrete Bud-specific actions (e.g. creating budgets, tracking transactions), matching the 'names domain but actions are generic' anchor; not a 3 because no action is concrete.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Bud data"), and the explicit 'Use when' clause avoids the 3-cap; not a 5 because the trigger guidance is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Bud data" supplies relevant keywords (Bud, data, records) but misses natural variations users would say like budgets, transactions, or spending, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Bud-specific trigger ("interact with Bud data") gives it a clear niche with minor overlap risk against generic data/automation skills; not a 5 because the generic action list could still overlap with adjacent 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/bud/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.