CtrlK
BlogDocsLog inGet started
Tessl Logo

zerobounce

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

49

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/zerobounce/SKILL.md
SKILL.md
Quality
Evals
Security

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 well-structured, actionable CLI integration guide with executable commands and a solid connection-readiness validation loop, weakened mainly by minor padding and a broken 'Step 2' cross-reference.

Suggestions

Trim the opening marketing paragraph and the redundant 'Popular actions' section, which repeats the `membrane action list` instruction already given in 'Searching for actions'.

Fix the 'skip to Step 2' reference by adding an explicit 'Step 2: Search for actions' header or rewriting it as 'skip to Searching for actions below'.

Add one fully worked example that substitutes a real CONNECTION_ID and intent so the run/proxy flow is end-to-end copy-pasteable.

DimensionReasoningScore

Conciseness

The body is mostly command-focused and efficient, but includes some padding such as the marketing audience intro, the awkward agent-types sentence, and a 'Popular actions' section that repeats the action-list command already shown above.

3 / 5

Actionability

It provides concrete, copy-pasteable commands throughout (install, login, connection ensure, action run, request) plus a specific flag table, with only minor gaps like unexpanded CONNECTION_ID/QUERY placeholders and no fully worked end-to-end example.

4 / 5

Workflow Clarity

The connection workflow is clearly sequenced with a state-polling validation loop (BUILDING -> READY / CLIENT_ACTION_REQUIRED -> re-poll), though the dangling 'skip to Step 2' reference (with no defined Step 2 header) is a minor navigation gap.

4 / 5

Progressive Disclosure

No bundle files exist and all content lives in a single well-sectioned SKILL.md; structure is good with clear headers, though the inline clientAction spec and proxy flag table could optionally be split into reference files.

4 / 5

Total

15

/

20

Passed

Description

41%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 identifies the named service and includes a 'Use when' trigger, but the capability list is generic and lacks the concrete email-validation actions and natural user phrases that would make it specific and distinctive.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete ZeroBounce actions such as 'Validate email addresses, run bulk validation jobs, and check credits/balance'.

Add natural trigger terms users would actually say, e.g. 'Use when the user wants to validate emails, clean an email list, check bounce risk, or look up ZeroBounce credits'.

Drop the generic 'Manage data, records' phrasing, which adds no specific signal and could overlap with unrelated data skills.

DimensionReasoningScore

Specificity

The description names the domain (ZeroBounce) but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete ZeroBounce-specific capabilities like email validation or bounce checking.

2 / 5

Completeness

Both a 'what' and an explicit 'Use when...' clause are present, but the 'what' is vague ('Manage data, records, and automate workflows') and the 'when' is generic, leaving it between the clear-what/weak-when and both-present anchors.

3 / 5

Trigger Term Quality

Only 'ZeroBounce' is a meaningful keyword; the rest ('data', 'records') is generic and misses the natural phrases users would say such as 'validate emails', 'clean email list', or 'check bounces'.

2 / 5

Distinctiveness Conflict Risk

ZeroBounce is a named third-party service, giving it a clear niche and distinct trigger unlikely to fire for unrelated skills, with only minor overlap risk from the generic word 'data'.

4 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
Reviewed

Table of Contents

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.