CtrlK
BlogDocsLog inGet started
Tessl Logo

neverbounce

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

48

Quality

51%

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/neverbounce/SKILL.md
SKILL.md
Quality
Evals
Security

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 content is a solid operational guide with executable Membrane CLI commands and a strong connection-state handling flow, but it is held back by a broken sentence, dangling step references, and missing validation for destructive/batch job operations.

Suggestions

Fix the truncated opening ("Neverbounce is an") and remove the dangling "skip to Step 2" reference or add the missing Step 2 section with correct numbering.

Add an explicit validation/verification checkpoint for batch and destructive operations, e.g. confirm job status with `membrane action run get-job-status` before retrieving or deleting results.

Tighten filler such as "Use action names and parameters as needed" and remove the embedded newline inside the `membrane connection ensure` URL code block.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands throughout, but it contains filler ("When to use which actions: Use action names and parameters as needed."), a truncated broken sentence ("Neverbounce is an"), and awkward prose that could be tightened.

3 / 5

Actionability

It provides concrete, mostly copy-paste-ready commands (install, login, connection ensure, action list/run, request) with documented flags and an action table, with only minor gaps such as the broken newline inside the connection-ensure URL block.

4 / 5

Workflow Clarity

The connection-readiness flow has good validation checkpoints (poll, check state, handle CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the sequence numbering is broken ("skip to Step 2" with no Step 2, a "1b" subsection) and batch/destructive job operations (create-verification-job, delete-job) lack validation steps, which caps this score at 3.

3 / 5

Progressive Disclosure

With no bundle files present, the single document is organized into clear, well-signaled sections (Overview, Install, Auth, Connecting, Searching, Popular actions, Running, Proxy, Best practices), though some reference-like detail (proxy flags table, full action list) is inlined rather than split out.

4 / 5

Total

14

/

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 names the target product and includes a Use-when trigger, but its capabilities are described in vague, generic terms and it omits the natural email-verification keywords users would actually invoke. It is distinct yet weak on specificity and trigger quality.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities such as verifying single emails and running bulk email-verification jobs.

Add natural trigger terms users would say, e.g. "Use when the user wants to verify email addresses, run bulk email-verification jobs, or check Neverbounce account credits."

Avoid the circular "interact with Neverbounce data" phrasing and instead tie the trigger to the actual task (email validation).

DimensionReasoningScore

Specificity

The description names the domain (Neverbounce) but the listed actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities like email verification or job creation.

2 / 5

Completeness

It includes both a (vague) "what" and an explicit "Use when" trigger clause, but the "what" is generic and the "when" is circular, so it sits between a clear-what anchor and the both-present-but-weak anchor rather than reaching 4.

3 / 5

Trigger Term Quality

It relies on a single keyword ("Neverbounce") and the circular phrase "interact with Neverbounce data," omitting the natural phrases a user would actually say such as "verify emails," "email validation," or "bulk email verification."

2 / 5

Distinctiveness Conflict Risk

Naming the specific product Neverbounce gives it a clear niche with minimal conflict risk, though the generic "manage data, records, and automate workflows" phrasing leaves minor overlap with general data skills.

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.