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

bombora

Bombora integration. Manage data, records, and automate workflows. Use when the user wants to interact with Bombora 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/bombora/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 solid, command-heavy integration guide with good actionability and a connection workflow that includes state-based validation checkpoints. Its weaknesses are some unnecessary introductory prose, a vague Overview section, and slightly inconsistent step numbering.

Suggestions

Trim the marketing-style intro paragraph about what Bombora is used for; keep only what Claude needs to act.

Replace the vague 'Bombora Overview' bullet list / 'Use action names and parameters as needed' with concrete example action names or remove it.

Fix the step labeling so '1b' and the 'Step 2' references resolve to clearly numbered headers (e.g. '1. Connect', '2. Discover & run actions').

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven content, but includes unnecessary prose ('Bombora provides B2B intent data, helping sales and marketing teams...') and a vague 'Bombora Overview' bullet list ending in 'Use action names and parameters as needed', so it is mostly efficient with some padding.	3 / 5
Actionability	It provides numerous copy-paste executable commands (npm install, membrane login, connection ensure, action list/run, request) with flags explained, giving mostly executable guidance with only minor gaps.	4 / 5
Workflow Clarity	The connection flow has a clear sequence with validation checkpoints (poll --wait, state checks for READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-poll feedback), but the '1b'/'Step 2' labeling is inconsistent with no matching Step 1/Step 2 headers, leaving a minor gap.	4 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clear sections (Overview, Working with Bombora, Popular actions, Best practices) with appropriate structure; minor gaps like the vague Overview bullets keep it just below a 5.	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 is adequate: it names the niche, includes an explicit 'Use when' trigger, and is reasonably distinct. Its main weakness is generic, non-concrete action language ('manage data, records, automate workflows') rather than specific capabilities.

Suggestions

Replace generic verbs with concrete capabilities, e.g. 'Pull Company Surge reports, look up accounts, and search Bombora topics.'

Add natural trigger variations such as 'B2B intent data', 'Company Surge', or 'account lookup' that a user might actually say.

Tighten the 'what' to list 3-4 specific Bombora actions to lift specificity and completeness toward the top anchors.

Dimension	Reasoning	Score
Specificity	Names the domain (Bombora) and lists a few actions ('Manage data, records, and automate workflows'), but the actions are generic/abstract rather than concrete like the anchor examples, so it sits at the 'names domain and 1-2 actions but not comprehensive' level.	3 / 5
Completeness	It has both a 'what' (Bombora integration; manage data, records, automate workflows) and an explicit 'when' ('Use when the user wants to interact with Bombora data'), but the 'what' is generic so it does not reach the fully concrete anchor 5.	4 / 5
Trigger Term Quality	The relevant natural keyword is 'Bombora' and the phrase 'interact with Bombora data', but it lacks synonyms or variations; for a niche product this is some relevant keyword coverage rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The 'Use when the user wants to interact with Bombora data' clause ties it to a distinct product niche with minimal conflict risk, though the generic 'manage data, records, workflows' actions leave minor overlap potential.	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/bombora/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.