CtrlK
BlogDocsLog inGet started
Tessl Logo

verifalia

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

55

Quality

62%

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/verifalia/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 body is a well-structured, highly actionable Membrane/Verifalia CLI guide with clear connection workflows and feedback loops, weakened mainly by light verbosity and the absence of a concrete Verifalia-specific action example.

Suggestions

Trim the marketing prose (e.g. the auth-plumbing line and the Verifalia boilerplate paragraph) to improve token efficiency.

Add at least one concrete Verifalia action example, such as invoking the email-verification action with a sample --input payload and showing the expected output.

Consider moving the proxy flag table and the detailed clientAction state handling into a references file to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The CLI commands are mostly efficient, but the marketing-style intro ("focus on integration logic rather than auth plumbing") and the Verifalia boilerplate paragraph add explanation that could be trimmed.

3 / 5

Actionability

Concrete, copy-paste-ready commands cover login, connection, action discovery, action runs, and proxy requests, but no Verifalia-specific action example (e.g. an actual email verification invocation) is shown.

4 / 5

Workflow Clarity

There is a clear install→authenticate→connect→poll→search→run sequence with state-checking feedback loops for the connection lifecycle, though the actual email-verification workflow itself is left to action discovery.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well organized into labeled sections, though at ~130 lines some material (the proxy flag table, client-action details) could be split into references.

4 / 5

Total

15

/

20

Passed

Description

57%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 product and includes an explicit Use-when trigger, but its capability phrasing is vague and it misses the natural email-verification keywords that would aid discovery and distinctiveness.

Suggestions

Replace generic verbs with concrete Verifalia capabilities, e.g. "Verify email addresses, check deliverability, and manage verification credits."

Add natural trigger terms users would say: "Use when the user wants to verify emails, check email validity/deliverability, or reduce bounce rates with Verifalia."

Tighten the "when" clause from "interact with Verifalia data" to specific email-verification intents to reduce overlap with generic data skills.

DimensionReasoningScore

Specificity

It names the Verifalia domain but the actions ("Manage data, records, and automate workflows") are generic and abstract rather than concrete capabilities like email verification or validation.

2 / 5

Completeness

Both a "what" (Verifalia integration managing data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Verifalia data") are present, though the what is vague and the when could be more specific.

4 / 5

Trigger Term Quality

"Verifalia" is a relevant natural keyword and a "Use when" trigger is present, but it omits common synonyms users actually say such as "verify email", "email validation", "deliverability", or "bounce".

3 / 5

Distinctiveness Conflict Risk

Naming the specific product Verifalia gives it a clear niche with minimal conflict risk, but the single generic trigger ("interact with Verifalia data") leaves minor overlap with broad data-integration skills.

4 / 5

Total

13

/

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.