Name: veriphone
Rating: 49.6 (1 reviews)
Author: membranedev

veriphone

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

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/veriphone/SKILL.md

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 content is a well-structured, actionable guide built around concrete Membrane CLI commands, with clear connection-state handling and polling feedback loops. It is slightly held back by an over-explanatory intro and the absence of any Veriphone-specific action examples beyond generic discovery commands.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tight CLI commands, but the intro ("Veriphone is a phone number validation and verification service... This helps prevent fraud and improve communication deliverability") and phrases like "so you can focus on the integration logic rather than auth plumbing" are unnecessary explanation that could be trimmed.	3 / 5
Actionability	Concrete, copy-pasteable commands with real flags appear throughout (login, connection ensure, action run with --input JSON, a proxy flag table); the main gap is that no actual Veriphone-specific action examples are shown, only generic membrane discovery/run commands.	4 / 5
Workflow Clarity	The install → login → ensure connection → poll for ready → search → run sequence is clear, with explicit state handling and a polling feedback loop for CLIENT_ACTION_REQUIRED/BUILDING; minor gaps include a referenced but unlabelled "Step 2" and no validation step before running actions.	4 / 5
Progressive Disclosure	No bundle files exist and none are needed; the single SKILL.md is well-sectioned with clear headers and no nested references, giving good structure with only minor organization gaps (the thin "Popular actions" section and inlined state-machine detail).	4 / 5
	Total	15 / 20 Passed

Description

41%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 Veriphone niche and includes an explicit trigger clause, but its capability wording is generic and it omits the natural phone-validation terms users would say. Strengthening the concrete actions and trigger vocabulary would lift the weakest dimensions.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete capabilities, e.g. "Validate and verify phone numbers, retrieve carrier, location, and line-type details, and build phone number reports."

Add natural trigger phrases users actually say, e.g. "Use when the user wants to validate a phone number, check whether a number is active or reachable, or look up carrier and location details."

Keep the explicit "Use when..." clause but tie it to phone-number-specific scenarios rather than the generic "interact with Veriphone data".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Veriphone domain but the actions are generic abstractions rather than concrete capabilities like validating phone numbers or retrieving carrier details, matching the anchor that names a domain with minimal/generic actions.	2 / 5
Completeness	It states a (vague) what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Veriphone data"), but the what does not clearly convey the skill's real capability, landing between a clear-what and the both-what-and-when anchors.	3 / 5
Trigger Term Quality	The only trigger keyword is the brand "Veriphone" plus generic "data"; the natural phrases users would actually say ("validate phone number", "verify a number", "carrier lookup") are absent, fitting the anchor with one or two generic keywords missing natural phrases.	2 / 5
Distinctiveness Conflict Risk	The "Veriphone" proper noun and brand-specific trigger create a clear niche with only minor overlap risk against other data-integration skills, matching the mostly-distinct anchor.	4 / 5
	Total	11 / 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/veriphone/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.