Name: tomba
Rating: 48.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

tomba

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

Quality

52%

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/tomba/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 delivers executable Membrane CLI commands and a clearly sequenced, state-aware connection workflow with feedback loops. Its main weaknesses are mild verbosity and a redundant actions section rather than structural problems.

Suggestions

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated `action list` command and reduce token overhead.

Trim explanatory prose about what Membrane does automatically (e.g. 'handles authentication and credentials refresh automatically') to only what affects command choice.

Convert the bulleted Tomba capability list at the top into a tighter reference, since it currently restates action names without actionable guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes some unnecessary explanation of Membrane's behavior and a redundant 'Popular actions' section that repeats the `action list` command, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-pasteable `membrane` commands with flags for login, connection ensure, polling, action list/run, and proxy requests, with only minor gaps (placeholders like CONNECTION_ID and <actionId> are clearly marked), matching 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	The connect-to-Tomba flow is clearly sequenced (install → login → ensure → poll → search → run) with explicit state checks (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, giving clear checkpoints with only minor gaps; the destructive/batch cap does not apply since no destructive workflow is instructed.	4 / 5
Progressive Disclosure	The content is well-organized into clearheaded sections (Overview, Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no bundle files to split out, giving good structure and easy navigation with only minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

37%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 short and includes a 'Use when' trigger tied to the Tomba brand, but its actions are generic and it omits Tomba's actual prospecting/email-finding capabilities and natural user keywords. It is borderline adequate rather than strong.

Suggestions

Replace generic verbs with Tomba-specific actions, e.g. 'Find email addresses, search domains, verify emails, and enrich leads via Tomba.'

Expand the trigger with natural phrasing users actually say, e.g. 'Use when the user wants to find emails, search a company domain, verify an email address, or enrich leads with Tomba.'

Mention the core artifacts (email addresses, company/domain data, leads) so the skill is distinguishable from generic data-management skills.

Dimension	Reasoning	Score
Specificity	The description names the domain (Tomba) but its actions are generic — 'Manage data, records, and automate workflows' — without mentioning Tomba's actual concrete capabilities (email finding, prospecting, lead generation), matching the 'names domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states a 'what' and an explicit 'Use when' trigger, but both are vague — 'Manage data, records, and automate workflows' and 'interact with Tomba data' — so it lands at the 'clear what but when is weakly implied/generic' level rather than the crisp anchor 4.	3 / 5
Trigger Term Quality	The only trigger phrase is 'interact with Tomba data', which is generic and omits the natural terms users would actually say (find emails, lead generation, email verifier); this fits 'one or two generic keywords; missing the natural phrases users say'.	2 / 5
Distinctiveness Conflict Risk	Tying triggers to the Tomba brand gives it a niche, but 'manage data, records, and automate workflows' is generic CRM-style language that could overlap with other data-management skills, matching 'somewhat specific but could still overlap'.	3 / 5
	Total	10 / 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/tomba/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.