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

bambora

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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/bambora/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 body is a solid, command-driven integration guide with good sectioning and explicit connection-state feedback loops, but it carries marketing prose and a redundant section, and it omits validation guidance for the destructive/batch payment operations it enables. It is genuinely usable yet would benefit from trimming and safety checks.

Suggestions

Delete the introductory marketing paragraph about what Bambora is and tighten fluff phrases; keep only operational guidance.

Add a validation/verification step around running actions and proxy requests for payment-mutating calls (e.g. confirm the action's inputSchema, check the response status/error fields, and prefer read actions before writes).

Fix the broken "skip to Step 2" cross-reference by labeling the subsequent steps, and remove the redundant "Popular actions" section that repeats the action-list command.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and structured tables, but it includes unnecessary padding: the opening marketing paragraph ("Bambora is a payment processing platform... used by merchants of all sizes looking for a secure and reliable payment gateway"), fluff like "so you can focus on the integration logic rather than auth plumbing", and a redundant "Popular actions" section that restates the action-list command already given under "Searching for actions". This is 'mostly efficient but includes some unnecessary explanation or could be tightened', not severe enough for a 2.	3 / 5
Actionability	Concrete, executable commands are given throughout — install, login, connection ensure, polling, action list/run with JSON input, proxy requests — plus a repeatable flag table. It stops short of 5 because placeholders (<agentType>, <actionId>, CONNECTION_ID) require substitution and no real Bambora-specific action example with a concrete inputSchema is shown, leaving minor gaps.	4 / 5
Workflow Clarity	The connection setup is sequenced with explicit state checkpoints (READY / BUILDING poll / CLIENT_ACTION_REQUIRED re-poll / CONFIGURATION_ERROR), but the skill drives payment operations (potentially destructive or batch) and the "Running actions" and "Proxy requests" sections give no validation or verification guidance before/after such calls. Per the rubric, missing validation for destructive/batch operations caps this at 3; a broken "skip to Step 2" reference with no labeled Step 2 also weakens sequencing.	3 / 5
Progressive Disclosure	No bundle files exist, and the single ~138-line body is organized into clear headed sections (Overview, Working with Bambora, install/auth/connect/search, Popular actions, proxy, Best practices). Because it exceeds the 'under 50 lines' simple-skill threshold and inlines content (clientAction details, the flag reference table) that could live in separate reference files, it is 'good structure; minor organization gaps' rather than the fully split, one-level-deep reference pattern of a 5.	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 pairs a 'what' with an explicit 'Use when...' trigger and leans on a distinctive brand name, but its capabilities are phrased generically and its trigger lacks concrete payment-domain keywords. It is functional but leaves specificity and trigger coverage on the table.

Suggestions

Replace generic verbs with concrete Bambora actions, e.g. "Process payments, manage payment profiles, and generate reports" instead of "Manage data, records, and automate workflows".

Add natural payment trigger terms users would say, e.g. "Use when the user wants to process payments, handle transactions or refunds, or query Bambora reports".

Keep the third-person, action-led voice but tighten to one sentence merging the what and when with specific triggers.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Bambora integration") but its actions — "Manage data, records, and automate workflows" — are generic verbs with no concrete Bambora-specific operations (e.g. process payments, issue refunds, generate reports). It fits the 'names the domain but actions are minimal or generic' anchor better than the 'concrete actions' anchor above, since none of the listed actions are specific.	2 / 5
Completeness	Both halves are present: a 'what' ("Bambora integration. Manage data, records, and automate workflows") and a 'when' ("Use when the user wants to interact with Bambora data"). It is not a 5 because neither the 'what' nor the 'when' uses concrete trigger phrases — the 'when' is generic and could be more specific, matching 'has both what and when; when could be more explicit or specific'.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Bambora data" supplies the natural keyword "Bambora" and an explicit trigger, but it omits common payment-related variations and synonyms (payments, transactions, refunds, payment gateway) that a user would naturally say. This matches 'some relevant keywords but missing common variations or synonyms' rather than the fuller coverage of score 4.	3 / 5
Distinctiveness Conflict Risk	The unique brand name "Bambora" makes this largely distinct and low-conflict, but the generic phrasing "interact with Bambora data" / "Manage data, records, and automate workflows" leaves minor overlap risk with other generic integration skills. It is mostly distinct with minor overlap risk rather than the clear-niche minimal-conflict of score 5.	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/bambora/SKILL.md
Commit: f484c82

Reviewed: ~1 hour 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.