Name: uk-gov-vehicle-enquiry-api
Rating: 53.6 (1 reviews)
Author: membranedev

uk-gov-vehicle-enquiry-api

UK gov Vehicle Enquiry API integration. Manage data, records, and automate workflows. Use when the user wants to interact with UK gov Vehicle Enquiry API data.

Quality

60%

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/uk-gov-vehicle-enquiry-api/SKILL.md

Quality

Content

63%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 solid, command-heavy integration guide with a well-sequenced connection workflow and explicit state-based validation checkpoints. Its main weaknesses are mild verbosity/redundancy between the 'Searching for actions' and 'Popular actions' sections and the absence of any progressive disclosure — all reference material is inlined rather than split into referenced files.

Suggestions

Merge the 'Popular actions' section into 'Searching for actions' to remove the duplicated `action list --intent=QUERY` guidance.

Trim editorial padding like 'so you can focus on the integration logic rather than auth plumbing' that does not change what Claude executes.

Move the vehicle data-model overview and the proxy flag reference table into a separate REFERENCE.md and link to it from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes unnecessary explanatory padding such as 'so you can focus on the integration logic rather than auth plumbing' and a restated 'Popular actions' section that duplicates the earlier 'Searching for actions' guidance.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands with real flags and a proxy-options table, with only minor gaps such as unresolved placeholders (CONNECTION_ID, actionId) and no example of an actual vehicle-enquiry action invocation with real input.	4 / 5
Workflow Clarity	The connection setup is a clearly sequenced workflow with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-after-action feedback loop, though later sections on searching/running actions are less tightly sequenced.	4 / 5
Progressive Disclosure	The body is well sectioned with headers but everything is inlined in a single ~150-line SKILL.md with no bundle files or one-level-deep references; the API data model and proxy-options reference material that would suit a separate file is kept inline.	3 / 5
	Total	14 / 20 Passed

Description

57%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 clearly identifies the target API and includes an explicit 'Use when' trigger, but its capability language is generic ('manage data, records, and automate workflows') rather than naming the concrete vehicle-enquiry actions the API exposes. Trigger terms lean on the API name and miss natural user phrasing like 'vehicle registration' or 'MOT'.

Suggestions

Replace 'Manage data, records, and automate workflows' with concrete actions the API exposes, e.g. 'Look up vehicle details, MOT status, and tax details by registration number'.

Expand the trigger clause with natural user phrasing: 'Use when the user wants to check vehicle details, MOT, or tax status by registration number'.

Avoid generic verbs like 'manage' and 'automate workflows' that could apply to almost any API integration skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ('UK gov Vehicle Enquiry API integration') but the stated actions ('Manage data, records, and automate workflows') are generic and not tied to concrete vehicle-data operations like retrieving MOT/tax status or vehicle details by registration.	2 / 5
Completeness	It answers both 'what' (API integration managing data, records, workflows) and 'when' ('Use when the user wants to interact with UK gov Vehicle Enquiry API data'), though the 'when' clause is generic and could name concrete triggers.	4 / 5
Trigger Term Quality	It includes the core keyword 'UK gov Vehicle Enquiry API' and 'data', but omits the natural phrases a user would actually say such as 'vehicle registration', 'MOT', 'tax', or 'vehicle details'.	3 / 5
Distinctiveness Conflict Risk	The named government API is a clear niche with minimal conflict risk, but the generic 'interact with ... data' trigger leaves minor overlap risk with other data-integration 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/uk-gov-vehicle-enquiry-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.