Name: validis
Rating: 60 (1 reviews)
Author: membranedev

validis

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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 highly actionable with concrete CLI commands and a solid connection state-machine including feedback loops, but it carries some avoidable verbosity and a dangling step reference. No bundle files exist, so structure rests entirely on the in-body sectioning.

Suggestions

Tighten the opening paragraph: drop the explanation of what Validis is and who uses it, keeping only what Claude needs to drive the integration.

Remove the duplicated action-discovery command — consolidate "Searching for actions" and "Popular actions" into a single section to avoid restating `membrane action list --intent`.

Fix the dangling "Step 2" reference by labeling the action-search/run section as Step 2, or rephrase to "proceed to searching for actions".

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Validis is and who uses it, plus the duplicated action-list command ("Searching for actions" vs "Popular actions") and padded phrasing like "so you can focus on the integration logic rather than auth plumbing", mark it as mostly efficient but with unnecessary explanation that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready CLI commands for every common case (install, login, connection ensure, poll with --wait, action list/run with JSON input, request proxy) with flags and a JSON parameter example, fully covering the integration's common operations.	5 / 5
Workflow Clarity	The connection flow has a clear state-machine with a poll loop and explicit feedback for READY / CLIENT_ACTION_REQUIRED / error states, but it references a "Step 2" that is never labeled, leaving a minor sequencing gap that keeps it below 5.	4 / 5
Progressive Disclosure	With no bundle files present, the body is organized into clear headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content appropriately inline; minor redundancy between the two action-list sections and the inline proxy flag table keep it from a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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 Validis niche with an explicit use-trigger, but its capability verbs are generic and it offers only a thin single trigger phrase. Strengthening it with more concrete financial-data actions and varied trigger terms would raise specificity and trigger quality.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Validis operations such as extracting financial statements, standardizing charts of accounts, or running due-diligence workflows.

Expand the trigger clause with natural variations users would say, e.g. "Use when the user wants to query Validis financial data, run due diligence, or automate Validis workflows."

Add a mention of the financial-data context (lenders, accountants, risk assessment) to the trigger so it matches real user phrasing.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Validis domain plus a couple of actions, but the verbs are generic ("manage", "automate") rather than concrete operations, matching the anchor that lists domain + 1-2 actions without comprehensive coverage.	3 / 5
Completeness	It states both a "what" (manage data, records, automate workflows) and an explicit "Use when…" trigger clause; the when is somewhat circular and could be more specific, so it sits at the "has both what and when, when could be more explicit" anchor rather than a 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Validis data" surfaces the key term "Validis" but offers only a single trigger phrase with no common variations or synonyms (e.g. financial data, due diligence, Validis API), aligning with the "some relevant keywords but missing variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"Validis" is a unique named platform, giving the skill a clear niche with a distinct brand trigger and minimal risk of firing for an unrelated skill.	5 / 5
	Total	15 / 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/validis/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.