Name: vetty
Rating: 52.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

vetty

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

Quality

59%

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

Quality

Content

61%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 well-structured, action-oriented CLI guide with a strong connection-state workflow, but it carries minor verbosity and omits validation guidance for destructive proxy requests. Progressive disclosure is good though all content lives inline.

Suggestions

Add a validation/verification step for destructive proxy requests (e.g., inspect the response status and confirm before proceeding on PUT/PATCH/DELETE).

Remove the duplicated 'membrane action list' command and trim opinionated prose like 'so you can focus on the integration logic rather than auth plumbing'.

Consider moving the detailed clientAction state reference and proxy flags table into a separate reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but includes some unnecessary prose ('so you can focus on the integration logic rather than auth plumbing') and repeats the action-list command across sections.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands (install, login, connection ensure, action run, request) plus a flags table, with only minor placeholder gaps (CONNECTION_ID, actionId, QUERY).	4 / 5
Workflow Clarity	The connection setup is a well-sequenced state machine with polling/feedback checkpoints, but destructive proxy operations (PUT/PATCH/DELETE) lack validation or verification steps, capping the score.	3 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references, though at ~140 lines some detail (the clientAction state machine, proxy flags table) is inlined rather than split into reference files.	4 / 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 has an explicit trigger clause and names a distinct niche (Vetty), but its capability statement relies on generic verbs ('manage data, records, automate workflows') rather than concrete actions. It is competent but lacks specificity.

Suggestions

Replace generic verbs with concrete Vetty capabilities (e.g., 'assess vendor risk, manage candidate records and tasks, automate screening workflows').

Add natural trigger synonyms users might say, such as 'vendor risk', 'third-party vendors', or 'screening records'.

Tighten the 'what' so it reads as specific actions rather than 'Manage data, records, and automate workflows'.

Dimension	Reasoning	Score
Specificity	The description names the Vetty domain but the actions ('Manage data, records, and automate workflows') are minimal and generic rather than concrete capabilities.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Vetty data') are present, though the what is somewhat generic.	4 / 5
Trigger Term Quality	'Vetty' and 'interact with Vetty data' are natural terms a user would say, but common variations or synonyms (records, vendor risk) are missing.	3 / 5
Distinctiveness Conflict Risk	Vetty is a named SaaS with a clear niche and a Vetty-specific trigger, giving low conflict risk, though the generic action phrasing leaves minor overlap potential.	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/vetty/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.