Name: wiza
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wiza

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

Quality

70%

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

Quality

Content

76%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 CLI commands and a reasonable connection-state workflow, but lacks validation/verification checkpoints around running actions and proxy calls, and has minor sequencing inconsistencies.

Suggestions

Add explicit validation steps before running actions or proxy requests — e.g. confirm the connection is READY and verify the output/error fields after each action run.

Fix the inconsistent step numbering (references to 'Step 2' and '1b' without a matching Step 1) so the connection workflow sequence is unambiguous.

Trim the opening 'Wiza is a prospecting tool...' paragraph, which re-explains a concept Claude can infer from the docs link.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI-command-oriented content with little concept over-explanation, though the opening paragraph re-explains what Wiza is and a couple of sections mildly restate flag details.	4 / 5
Actionability	Fully executable copy-paste-ready commands throughout — install, login, connection ensure, action list/run, request, with concrete flag tables covering the common cases.	5 / 5
Workflow Clarity	The connection setup flow is sequenced with state polling, but destructive/batch actions (running actions, proxy requests) lack validation or verification checkpoints; numbering is inconsistent (jumps to 'Step 2' and '1b' without a Step 1/2 enumeration).	3 / 5
Progressive Disclosure	Well-organized into clear sections (Install, Auth, Connecting, Actions, Proxy, Best practices); no bundle files are present so all content is inline, which is appropriate at this length but the API action reference could be split out as the skill grows.	4 / 5
	Total	16 / 20 Passed

Description

63%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 answers both what and when with an explicit 'Use when' clause, but relies on generic verbs ('manage', 'automate workflows') and omits the natural prospecting-specific terms users would actually say.

Suggestions

Replace generic verbs with Wiza-specific actions, e.g. 'Find email addresses and contact info from LinkedIn profiles, search and manage leads and contacts'.

Add natural trigger terms users say, such as 'leads, contacts, prospecting, email finding, LinkedIn enrichment'.

Tighten the 'Use when' clause to Wiza-specific scenarios rather than the generic 'interact with Wiza data'.

Dimension	Reasoning	Score
Specificity	Names the domain (Wiza) and three concrete action areas — 'Manage data, records, and automate workflows' — but these are fairly generic verbs rather than a comprehensive list of specific operations.	4 / 5
Completeness	Has a clear 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Wiza data'), though the 'when' trigger is somewhat generic.	4 / 5
Trigger Term Quality	Includes 'Wiza', 'data', 'records', and 'workflows' but lacks the natural synonyms users say (e.g., leads, contacts, prospecting, email finding); 'interact with Wiza data' is generic rather than natural user phrasing.	3 / 5
Distinctiveness Conflict Risk	Tied to the distinct Wiza brand, but 'Manage data, records, and automate workflows' is broad phrasing that could overlap with other integration/CRM skills; the trigger lacks specific Wiza-only language.	3 / 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/wiza/SKILL.md
Commit: f484c82

Reviewed: 3 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.