Name: voilanorbert
Rating: 58.4 (1 reviews)
Author: membranedev

voilanorbert

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

Quality

68%

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/voilanorbert/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 body is a strong, executable integration guide: concrete CLI commands throughout, a clear connection state machine, and tidy sectioning with no over-deep references. Its main weaknesses are a few padded explanatory passages and the absence of an explicit validation/retry feedback loop after action or proxy execution.

Suggestions

Add an explicit post-action validation/retry step (e.g. check the `output`/`error` field and re-run or fall back to `membrane request` on failure) to close the feedback loop for batch and proxy operations.

Trim inferable context such as the marketing-platform description paragraph and repeated Membrane-auth explanation to improve token efficiency.

Flesh out or remove the empty "Popular actions" section and give the overview Email/Attachment/Contact list clear signals of where each capability's actions live.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and tables, though a few explanatory passages (the marketing-platform intro and Membrane auth boilerplate) state things Claude could infer and could be trimmed.	4 / 5
Actionability	It provides copy-paste ready CLI commands for install, login, connection ensure, polling, action list/run, and proxy requests, plus a flag reference table covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with a state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and polling, but there is no explicit validate-then-fix retry loop after running actions or proxy requests.	4 / 5
Progressive Disclosure	Content is well organized into overview, install, auth, connection, search, actions, proxy, and best-practices sections with no bundle files present and no nested references; minor gaps are the thin "Popular actions" stub and under-signaled overview entity list.	4 / 5
	Total	17 / 20 Passed

Description

53%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 is adequately triggered and distinct thanks to naming VoilaNorbert, but its capability list is generic (manage data, records, automate workflows) rather than reflecting the platform's actual email and contact features. Tightening the action verbs and adding product-specific trigger terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete VoilaNorbert capabilities such as finding email addresses, verifying contacts, and managing lead/contact lists.

Add natural trigger terms users would say, e.g. email lookup, contact search, or email verification, rather than only "interact with VoilaNorbert data".

Keep the third-person voice but make the "Use when..." clause reference specific user intents (e.g. finding someone's email, enriching a contact record).

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the integration and a couple of general actions, but the verbs (manage, automate) are generic and not domain-specific to VoilaNorbert's email/contact capabilities.	3 / 5
Completeness	A clear "Use when the user wants to interact with VoilaNorbert data" clause gives an explicit trigger, but the "what" (Manage data, records, automate workflows) is generic, so it only weakly answers what the skill concretely does.	3 / 5
Trigger Term Quality	It names "VoilaNorbert" and "data, records" but lacks the natural phrases users would say (e.g. email finder, contact verification) and omits synonyms or product-specific terms.	3 / 5
Distinctiveness Conflict Risk	Naming "VoilaNorbert integration" gives it a clear niche with distinct triggers, with only minor overlap risk against other generic data-management skills.	4 / 5
	Total	13 / 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/voilanorbert/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.