Name: vindicia
Rating: 56.8 (1 reviews)
Author: membranedev

vindicia

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

Quality

65%

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

Quality

Content

68%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 highly actionable with executable CLI commands and a sensible connection workflow, and it is well-structured for a single-file skill. Its weaknesses are mild verbosity, a missing validation checkpoint before running destructive billing actions, and a dangling step reference.

Suggestions

Trim the intro paragraph explaining what Vindicia is and the "auth plumbing" phrase, and remove the duplicated `action list` command in the "Popular actions" section.

Add a validation/verification checkpoint before running actions on billing data — e.g. review the action's inputSchema and confirm with the user before executing transactions or other destructive operations.

Resolve the dangling "skip to Step 2" reference by labeling the workflow steps (Step 1, Step 2) or rewriting it to point at a concrete section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but it includes an unnecessary intro paragraph explaining what Vindicia is, a padding phrase ("so you can focus on the integration logic rather than auth plumbing"), and a duplicated `action list` command in "Popular actions". This matches anchor 3 (mostly efficient with some unnecessary explanation).	3 / 5
Actionability	It provides copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, request proxy) plus a concrete flag table. Placeholders like <actionId> are expected for a CLI reference and do not reduce executability.	5 / 5
Workflow Clarity	A clear sequence with a polling feedback loop for connection state exists, but there is no validation/verification checkpoint before running actions on billing data (a destructive context, which caps this dimension at 3), and the "skip to Step 2" reference is dangling with no labeled Step 2.	3 / 5
Progressive Disclosure	The single-file skill is organized into clear, well-signaled sections with no nested references, giving good structure and easy navigation. It does not reach 5 because the body exceeds the simple-skill line threshold and some inline content (e.g. the detailed clientAction state machine) could live in a reference file.	4 / 5
	Total	15 / 20 Passed

Description

61%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 includes a third-person capability statement and an explicit Use-when clause, and is safely distinct via the product name. Its main weakness is generic, non-concrete action language and thin trigger terms that miss the natural subscription/billing vocabulary.

Suggestions

Replace the generic actions ("Manage data, records, and automate workflows") with concrete Vindicia capabilities such as "manage subscriptions, billing schedules, transactions, payment methods, and reports".

Add natural trigger terms users would actually say — e.g. "subscriptions", "recurring billing", "churn", "Vindicia transactions" — rather than relying on only "Vindicia data".

Dimension	Reasoning	Score
Specificity	The description names the Vindicia domain but its actions ("Manage data, records, and automate workflows") are generic and applicable to almost any integration rather than concrete Vindicia capabilities. It does not reach anchor 3 because the actions listed are not concrete, Vindicia-specific operations.	2 / 5
Completeness	Both a "what" ("Vindicia integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Vindicia data") are present. It falls short of anchor 5 because both the what and the when are generic/narrow rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	It surfaces the product name "Vindicia" and the phrase "interact with Vindicia data", but omits the natural domain terms users would actually say (subscriptions, billing, recurring revenue, churn). This matches anchor 3 ("Some relevant keywords but missing common variations or synonyms").	3 / 5
Distinctiveness Conflict Risk	The skill is keyed to the specific named product "Vindicia" with a trigger of "Vindicia data", giving it a clear niche and minimal risk of triggering for the wrong skill.	5 / 5
	Total	14 / 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/vindicia/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.