Name: vies-api
Rating: 49.6 (1 reviews)
Author: membranedev

vies-api

VIES API integration. Manage data, records, and automate workflows. Use when the user wants to interact with VIES API 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/vies-api/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 body is a solid, mostly executable guide to the Membrane CLI workflow for VIES, with a clear connection state machine and polling feedback loop. Its weaknesses are some conversational filler, a "Popular actions" section that lists no actions, and minor cross-reference/numbering inconsistencies.

Suggestions

Trim non-essential prose such as the "It's used by businesses and developers..." sentence and "so you can focus on the integration logic rather than auth plumbing" to respect token budget.

Populate the "Popular actions" section with 2-3 concrete example actions (e.g. a validate-VAT call with input/output) instead of only instructing the reader to discover them.

Fix the broken navigation cues: label a clear "Step 2" heading and rename "1b" to match a defined "1a", or restructure into a single numbered sequence.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary filler such as "It's used by businesses and developers who need to ensure the validity of VAT numbers for compliance and tax purposes" and "so you can focus on the integration logic rather than auth plumbing" that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready executable commands (npm install, membrane login, connection ensure, action list/run, request) with minor gaps — the "Popular actions" section tells the reader to discover actions rather than listing any, and examples use placeholders like <id> and CONNECTION_ID.	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-machine checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-then-recheck feedback loop, with only minor gaps such as a "skip to Step 2" reference with no visible Step 2 and a "1b" without a "1a".	4 / 5
Progressive Disclosure	The skill is a single well-organized file with clear section headers and no bundle references (none exist); at ~150 lines the dense clientAction state-machine block and proxy-options table are reasonable inline, giving good structure with minor organization gaps rather than the lean ideal.	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 is dominated by generic boilerplate ("Manage data, records, and automate workflows") and fails to name the skill's real purpose — VAT number validation — relying only on the "VIES API" service name. It includes an explicit use-trigger but the "what" is vague and natural trigger terms like "VAT number" are missing.

Suggestions

Replace "Manage data, records, and automate workflows" with the concrete capability, e.g. "Validate VAT Identification Numbers against the European Commission's VIES database and retrieve company details."

Add natural trigger terms users actually say, e.g. "Use when the user wants to validate a VAT number, check VIES, or verify VAT registration details."

Mention common synonyms/extensions (VAT number, VIES, VAT-ID) to improve trigger-term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ("VIES API integration") but the listed actions — "Manage data, records, and automate workflows" — are generic boilerplate and omit the actual concrete capability (validating VAT numbers), matching the anchor that names a domain with only minimal/generic actions.	2 / 5
Completeness	An explicit "Use when the user wants to interact with VIES API data" trigger is present (so it clears the missing-trigger cap), but the "what" is vague boilerplate that never states the skill validates VAT numbers, landing between the vague-what and both-present anchors.	3 / 5
Trigger Term Quality	The only keywords are the technical service name "VIES API" and "VIES API data"; the natural phrases a user would actually say ("validate VAT number", "check VIES", "VAT validation") are absent, fitting the anchor with one or two jargon keywords missing the natural phrases.	2 / 5
Distinctiveness Conflict Risk	The "VIES API" reference and "interact with VIES API data" trigger carve out a mostly distinct niche with only minor overlap risk, despite the generic "Manage data, records, and automate workflows" phrasing.	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/vies-api/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.