CtrlK
BlogDocsLog inGet started
Tessl Logo

findymail

Findymail integration. Manage Persons, Organizations, Leads, Deals, Pipelines, Activities and more. Use when the user wants to interact with Findymail data.

64

Quality

76%

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

Quality

Content

82%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 highly actionable with executable Membrane CLI commands and a well-sequenced connection workflow including validation checkpoints. Minor conciseness and step-numbering gaps keep it just short of exemplary.

DimensionReasoningScore

Conciseness

The body is mostly lean and command-driven, but the opening paragraph explaining what Findymail is and who uses it is mild over-explanation that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready CLI commands for every key operation (login, connection ensure, action list/run, request proxy) with concrete flags and JSON output, covering the common cases.

5 / 5

Workflow Clarity

The connection flow is clearly sequenced with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll loop, but the 'skip to Step 2' / '1b' numbering is slightly inconsistent.

4 / 5

Progressive Disclosure

Content is well-organized into clearly labeled sections (Overview, Working with Findymail, Popular actions, Best practices) with no nested references, though it is a single inlined file beyond the simple-skill threshold.

4 / 5

Total

17

/

20

Passed

Description

71%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 clearly identifies a branded niche and lists concrete entities with an explicit 'Use when' trigger, but its trigger phrasing is generic and action verbs are not differentiated. It is solid but could be sharpened with more natural, task-oriented keywords.

Suggestions

Add task-oriented trigger phrases users would naturally say, e.g. 'Use when the user wants to find or verify email addresses, look up leads, or check Findymail credit balance.'

Replace the generic 'Manage' with one or two concrete verbs (e.g. 'Find, verify, and enrich contacts') to raise action specificity.

Include synonyms or file/URL cues (e.g. 'email lookup, lead enrichment, LinkedIn profile') so the description triggers on varied phrasings.

DimensionReasoningScore

Specificity

Enumerates several concrete entity types ('Persons, Organizations, Leads, Deals, Pipelines, Activities') rather than abstract language, but the single generic verb 'Manage' leaves minor gaps in action specificity.

4 / 5

Completeness

It states both a clear 'what' (manage the listed entities) and an explicit 'when' ('Use when the user wants to interact with Findymail data'), though the 'when' trigger is somewhat generic.

4 / 5

Trigger Term Quality

The trigger relies almost entirely on the brand name 'Findymail data' with no natural synonyms or task-oriented phrases a user would say, missing common variations.

3 / 5

Distinctiveness Conflict Risk

Naming the specific product 'Findymail' carves a clear niche with distinct triggers and minimal risk of conflicting with other skills.

5 / 5

Total

16

/

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.