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

Blog Docs Log in Get started

woovi

Woovi integration. Manage data, records, and automate workflows. Use when the user wants to interact with Woovi 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/woovi/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 skill is a solid, actionable CLI-wrapper guide with concrete commands and a well-structured connection workflow, but it has a broken "Step 2" navigation reference, lacks verification steps for potentially destructive action runs, and carries minor over-explanation. Fixing the workflow navigation and trimming padding would raise the lower dimensions.

Suggestions

Fix the broken cross-reference: "skip to Step 2" points to no labeled Step 2 — relabel the subsequent sections (e.g., Step 2: Search for actions) so the flow is navigable.

Add a verification/check step after running actions, especially for write or payment operations (e.g., re-fetch the charge to confirm it was created).

Trim the opening product description and filler phrases like "so you can focus on the integration logic rather than auth plumbing" to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes unnecessary padding such as the opening product pitch ("allows merchants to create shareable links... without needing a full e-commerce setup") and filler like "so you can focus on the integration logic rather than auth plumbing", fitting the mostly-efficient-but-could-be-tightened anchor.	3 / 5
Actionability	It provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request) plus a flag table, matching the mostly-executable-with-minor-gaps anchor; not a 5 because examples rely on placeholders (CONNECTION_ID, QUERY) and the request example uses a generic /path/to/endpoint.	4 / 5
Workflow Clarity	The connection flow is sequenced with checkpoints (poll until READY, handle CLIENT_ACTION_REQUIRED, re-poll), but the text references a non-existent "Step 2" and running actions — which can be destructive (charges/payments) — has no verification step, so per the destructive-operation cap it cannot exceed 3.	3 / 5
Progressive Disclosure	The content is well-organized into clear logical sections with no nested or buried references, and keeping CLI detail inline is reasonable for this kind of skill; it sits at good-structure rather than 5 because the detailed clientAction state machine and proxy flag table could be split into a reference file.	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 correctly includes an explicit "Use when" trigger and names a specific, distinct niche (Woovi), but its action list is generic rather than concrete and it omits the natural domain terms (payment links, charges, checkout) users would actually say. Strengthening the action specificity and trigger vocabulary would lift the weakest dimensions.

Suggestions

Replace the generic actions with concrete Woovi operations, e.g. "Create payment links, fetch charges, and manage customers."

Expand the trigger phrase to include natural domain terms users say, e.g. "Use when the user wants to create Woovi payment links, check charges, or manage customers."

Keep the explicit "Use when" clause but pair it with the concrete actions so both what and when are specific.

Dimension	Reasoning	Score
Specificity	The description names the domain (Woovi) but the actions — "Manage data, records, and automate workflows" — are generic and not concrete Woovi-specific operations (e.g., create payment links, fetch charges), matching the anchor for minimal/generic actions rather than the 1-2 concrete-actions anchor.	2 / 5
Completeness	It states both a what ("Woovi integration. Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Woovi data"), matching the both-present-but-could-be-more-specific anchor; not a 5 because the what is generic rather than concrete.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Woovi data" provides the natural keyword "Woovi", but it lacks common variations and domain synonyms a user might say (payment links, charges, checkout, customers), fitting the some-keywords-but-missing-variations anchor.	3 / 5
Distinctiveness Conflict Risk	"Woovi" is a specific named payment service giving it a clear niche and distinct trigger, but the generic action phrasing ("Manage data, records, and automate workflows") leaves minor overlap risk, so it sits at mostly-distinct rather than the fully-distinct anchor.	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/woovi/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.