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

neetoinvoice

Neetoinvoice integration. Manage Invoices, Clients, Users, Payments. Use when the user wants to interact with Neetoinvoice 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/neetoinvoice/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 highly actionable, full of concrete executable Membrane CLI commands and a solid connection-state feedback loop. Its weak spots are an unnecessary marketing intro, a dangling "Step 2" reference, and missing validation guidance before destructive action/proxy calls.

Suggestions

Delete or compress the opening product-description paragraph; Claude does not need to be told what invoicing software is or who its users are.

Fix the dangling "skip to Step 2" references by labeling the next section ("Searching for actions") as Step 2 or rewriting the jumps to point to a named section.

Add a validation checkpoint before running actions or proxy requests, especially for POST/PUT/DELETE (e.g., confirm the actionId/input against its inputSchema, or dry-run before mutating calls).

Dimension	Reasoning	Score
Conciseness	Most of the body is concrete commands, but the opening paragraph ("Neetoinvoice is an invoicing and accounting software designed for small businesses and freelancers...") is product/marketing description Claude does not need and could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, proxy) plus a full flags table, but "Popular actions" only repeats the search command with placeholder "QUERY" and no concrete example actions.	4 / 5
Workflow Clarity	The connection flow has a real validate-retry checkpoint (poll state, handle CLIENT_ACTION_REQUIRED, re-poll until READY), but "skip to Step 2" references a non-existent labeled Step 2, and there is no validation checkpoint before running potentially destructive actions or proxy requests.	3 / 5
Progressive Disclosure	The single file is well-organized into clear sections with no nested references and no broken external links (no bundle files exist), but at ~158 lines with no external reference structure it is a monolith rather than an overview pointing to one-level-deep references.	4 / 5
	Total	14 / 20 Passed

Description

70%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 cleanly states what the skill does and when to use it, with good natural trigger keywords tied to a specific app. Its main weakness is a single generic action verb and a somewhat vague trigger clause ("interact with Neetoinvoice data").

Suggestions

Replace the single generic verb "Manage" with several distinct concrete actions (e.g., "Create and send invoices, manage clients and payments, track expenses") to improve specificity.

Make the trigger clause more concrete with phrases users actually say, e.g., "Use when the user wants to create or send invoices, record payments, or manage clients in Neetoinvoice."

Drop the generic term "Users" from the capability list or scope it (e.g., "team members") to reduce overlap with unrelated admin skills.

Dimension	Reasoning	Score
Specificity	It names the domain and lists four concrete entities ("Manage Invoices, Clients, Users, Payments"), but the action is a single generic verb applied to a list of nouns rather than several distinct concrete actions.	3 / 5
Completeness	Both "what" ("Neetoinvoice integration. Manage Invoices, Clients, Users, Payments.") and "when" ("Use when the user wants to interact with Neetoinvoice data.") are present, but the trigger clause is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	Natural terms a user would say are present ("Invoices, Clients, Users, Payments") alongside the app name, giving good keyword coverage, though "interact with Neetoinvoice data" is generic and synonyms/extensions are missing.	4 / 5
Distinctiveness Conflict Risk	Naming the specific app Neetoinvoice gives it a clear niche with mostly distinct triggers, but the generic entity list (especially "Users") carries minor overlap risk with other accounting/admin skills.	4 / 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/neetoinvoice/SKILL.md
Commit: f484c82

Reviewed: 5 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.