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

vosfactures

Vosfactures integration. Manage data, records, and automate workflows. Use when the user wants to interact with Vosfactures 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/vosfactures/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 actionable and well-structured with concrete CLI commands, but it lacks validation/verification and error-recovery guidance for the destructive data operations, and a few sections (Popular actions, step numbering) are inconsistent or thin.

Suggestions

Add validation and error-recovery for data operations: check the `output`/error fields after `membrane action run` and proxy requests, and confirm before destructive POST/PUT/DELETE calls.

Make the step sequence consistent: label steps 1a/1b/2 explicitly so "skip to Step 2" and "1b" resolve to real headings.

Replace the empty "Popular actions" section with a short list of real common actions (e.g. list invoices, create customer) instead of repeating the discovery command.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable commands with a focused proxy flags table; minor trimmable padding remains ("so you can focus on the integration logic rather than auth plumbing" and the discovery command repeated under "Popular actions").	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure, action run, and proxy requests with a thorough options table; the main gap is the "Popular actions" section, which re-states the discovery command instead of listing concrete popular actions.	4 / 5
Workflow Clarity	Connection setup has explicit state checks and a poll/handle feedback loop, but the destructive data operations (action run, proxy POST/PUT/DELETE) have no validation or error-recovery steps, and step numbering is inconsistent ("skip to Step 2" with no labeled Step 2, "1b" with no 1a).	3 / 5
Progressive Disclosure	No bundle files exist; the single ~140-line file is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with an external docs link, though everything is inline with minor organization gaps.	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 is clearly targeted to a specific app and includes an explicit use-when clause, but its capability list is vague and lacks the concrete invoicing/accounting actions and synonyms that would make triggers more natural.

Suggestions

Replace generic verbs with concrete Vosfactures actions, e.g. "Create and send invoices, track expenses, and generate financial reports in Vosfactures."

Add natural trigger synonyms users actually say, such as invoicing, accounting, expenses, or invoices, to the "Use when..." clause.

Tighten the what/when pairing so both halves are specific, e.g. "Use when the user wants to create invoices, manage customers, or pull financial reports from Vosfactures."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Vosfactures domain but the actions are generic and abstract, with none of the concrete invoicing actions (create/send invoices, track expenses, generate reports) the body actually supports.	2 / 5
Completeness	It states both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Vosfactures data"), though the "what" is generic rather than concrete.	4 / 5
Trigger Term Quality	It includes the natural app-name keyword "Vosfactures" and a "Use when... Vosfactures data" trigger, but misses common synonyms a user would say such as invoices, invoicing, accounting, or expenses.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named SaaS app "Vosfactures" with an app-specific trigger gives it a clear niche and minimal risk of firing for unrelated skills.	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/vosfactures/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.