Name: snov
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

snov

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

Quality

71%

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/snov/SKILL.md

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 content is a well-structured, actionable CLI integration guide with concrete copy-paste commands and a clear connection workflow that includes state-based validation checkpoints. Weaknesses are minor: some marketing-fluff phrasing and a broken step-numbering scheme (references to an unlabeled 'Step 2' and an orphaned '1b').

Suggestions

Fix the step numbering: label the connection section 'Step 1' with a '1a' before '1b', and explicitly label the action-search/run section as 'Step 2' so 'skip to Step 2' resolves.

Trim marketing-style phrasing like 'so you can focus on the integration logic rather than auth plumbing' to keep the guide purely instructional.

Consider moving the proxy flag reference table and detailed clientAction state handling into a separate reference file to reduce inline length.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and lean, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and the opening sentence about what Snov.io is, fitting the efficient-with-minor-trim anchor.	4 / 5
Actionability	Copy-paste-ready commands are provided throughout (install, login, connection ensure/get, action list/run, request) with concrete flag examples and a proxy options table, fully covering the common cases.	5 / 5
Workflow Clarity	The install→authenticate→connect→wait→search→run sequence is clear with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop, but the step numbering is broken ('skip to Step 2' with no labeled Step 2, a '1b' with no '1a'), a minor gap.	4 / 5
Progressive Disclosure	The single-file body is well-organized into clear sections (Overview, Working with Snov, Install, Auth, Connecting, Searching, Popular actions, Proxy, Best practices) with no nested references, though it is longer than 50 lines and the proxy/action reference material is inlined rather than split into separate files.	4 / 5
	Total	17 / 20 Passed

Description

61%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 uses third person and includes an explicit 'Use when' trigger tied to a distinctive brand name, but the capability statement is generic ('manage data, records, and automate workflows') and lacks concrete actions. Trigger coverage is limited to the single brand term without synonyms.

Suggestions

Replace generic verbs with concrete Snov capabilities, e.g. 'Find leads, verify email addresses, run email campaigns, and manage prospect lists'.

Expand the trigger phrase to include natural terms users say, such as 'leads', 'email verification', 'outreach', or 'Snov.io'.

Make the 'when' clause more specific by naming the tasks that should invoke the skill rather than 'interact with Snov data'.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Snov domain but the actions are generic and minimal rather than concrete capabilities, matching the anchor for naming a domain with minimal/generic actions.	2 / 5
Completeness	Both a 'what' (manage data, records, automate workflows) and an explicit 'when' ("Use when the user wants to interact with Snov data") are present, though both could be more specific, fitting the anchor where both exist but the 'when' could be more explicit.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Snov data" surfaces the relevant brand keyword a user would say, but misses common variations or synonyms like leads, email verifier, or outreach.	3 / 5
Distinctiveness Conflict Risk	"Snov" is a specific named platform giving the skill a clear niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	14 / 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/snov/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.