Name: realphonevalidation
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

realphonevalidation

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

Quality

61%

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

Quality

Content

70%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 delivers strong, executable CLI guidance with a clearly sequenced connection-state workflow and feedback loops, scoring well on actionability and workflow clarity. It loses points for duplicated action-discovery sections and mild over-explanation on conciseness, and has no separate reference files to offload API detail for progressive disclosure.

Suggestions

Merge the 'Searching for actions' and 'Popular actions' sections, which repeat the same `membrane action list` guidance, into one concise discovery section.

Fix the broken step numbering — it references 'Step 2' and '1b' without a matching 'Step 1'/'Step 2' sequence — so the workflow reads as a coherent ordered list.

Add one worked end-to-end example (e.g. connect → discover a validate action → run it with a sample phone `--input`) so the placeholders CONNECTION_ID and actionId become concrete.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — concrete CLI commands with brief, relevant commentary — but includes some light padding such as explaining that Membrane 'handles authentication and credentials refresh automatically' twice and restating action-list intent in two near-duplicate sections ('Searching for actions' vs 'Popular actions').	4 / 5
Actionability	It provides concrete, executable `membrane` commands for install, login, connection, action discovery, running, and proxying with a clear flag reference table; the only gap is that CONNECTION_ID and actionId placeholders are left abstract without a worked end-to-end example tying them together.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state-checking checkpoints (READY → skip, BUILDING → poll, CLIENT_ACTION_REQUIRED → act then re-poll, CONFIGURATION_ERROR → check error), giving a clear feedback loop; minor gaps are the inconsistent step numbering (jumps to 'Step 2'/'1b' without a labeled Step 2) and no explicit validation for batch action runs.	4 / 5
Progressive Disclosure	No bundle files are present, so the content is a single self-contained file; it is sectioned reasonably, but there are no one-level-deep references for the larger API detail, and the duplicated action-discovery sections suggest content that could be consolidated or split into a reference file.	3 / 5
	Total	15 / 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 correctly identifies the RealPhoneValidation niche and includes both a what and a when clause, but its capability list ('Manage data, records, and automate workflows') is generic rather than naming the concrete phone-validation actions users would want. Adding specific terms like 'validate phone numbers, check account balance' would lift specificity and trigger-term quality.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete actions such as 'Validate phone numbers, check account balance, and automate validation workflows'.

Add natural user-facing trigger terms and synonyms — e.g. 'Use when validating or verifying phone numbers, checking if a number is real/active, or checking RealPhoneValidation account balance'.

Use third-person imperative voice consistently; 'Manage' is correct, but tighten the clause so the capability verbs map directly to the API's actions.

Dimension	Reasoning	Score
Specificity	It names the RealPhoneValidation domain but the actions — 'Manage data, records, and automate workflows' — are generic and minimal rather than concrete capabilities like validate/verify phone numbers.	2 / 5
Completeness	Both 'what' (RealPhoneValidation integration that manages data, records, workflows) and 'when' (Use when the user wants to interact with RealPhoneValidation data) are present and explicit, though the 'what' is somewhat broad and the 'when' trigger could be more specific.	4 / 5
Trigger Term Quality	It includes 'RealPhoneValidation' and 'data' and a natural 'Use when the user wants to interact with RealPhoneValidation data' clause, but lacks common synonyms users would actually say such as 'validate phone numbers', 'verify phone', or 'check if a number is real'.	3 / 5
Distinctiveness Conflict Risk	The RealPhoneValidation name provides a clear niche with a distinct trigger, and the 'Use when' clause scopes it well; minor overlap risk only because 'manage data/records' is generic language shared with many 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/realphonevalidation/SKILL.md
Commit: f484c82

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