Name: invoice-ninja
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

invoice-ninja

Invoice Ninja integration. Manage Organizations. Use when the user wants to interact with Invoice Ninja 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/invoice-ninja/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.

A concrete, executable integration guide with a well-structured connection workflow and feedback loop, weakened by introductory concept padding and a couple of navigation gaps. Trimming the fluff and fixing the dangling 'Step 2' references would tighten it further.

Suggestions

Remove the introductory paragraph explaining what Invoice Ninja is and who uses it; Claude already knows this, and the 'so you can focus on the integration logic' sentence is promotional filler.

Label the section after the connection flow as 'Step 2' (or remove the 'skip to Step 2' phrasing) so the cross-references resolve.

Add a short verification step after create/update actions (e.g. re-fetch the created resource or check the response status) to close the validation gap for write operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient executable commands, but padded with concept explanation Claude already knows ('Invoice Ninja is an open-source invoicing and expense tracking application...') and fluff like 'so you can focus on the integration logic rather than auth plumbing' and the bare 'Use action names and parameters as needed.'	3 / 5
Actionability	Copy-paste-ready commands cover the common cases (install, login, connection ensure, polling, action list/run, proxy) with concrete flags and a populated popular-actions table mapping names to keys.	5 / 5
Workflow Clarity	The connection-setup flow is explicitly sequenced with a state-driven feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/error, poll-and-retry), but the 'skip to Step 2' references point to an unlabeled section and post-create validation is absent.	4 / 5
Progressive Disclosure	Single-file skill is well-organized with clear section headers and no nested references, but the inlined 20-row popular-actions table is borderline reference material that could live in a separate file.	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.

A concise, third-person description that pairs a clear product niche with an explicit 'Use when' trigger. Its main weakness is thin capability coverage — it lists only 'Manage Organizations' rather than the breadth of actions the skill actually supports.

Suggestions

Replace the single generic 'Manage Organizations' action with two or three concrete ones that reflect the skill's actual capabilities (e.g. 'Create and list invoices, manage clients and payments').

Add natural synonyms a user might say (invoicing, billing, expenses, clients) to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Invoice Ninja integration') and one concrete action ('Manage Organizations'), but coverage is minimal and not comprehensive — the rest ('interact with Invoice Ninja data') is generic.	3 / 5
Completeness	Explicitly answers both — 'what' via 'Invoice Ninja integration. Manage Organizations.' and 'when' via the 'Use when the user wants to interact with Invoice Ninja data' clause — though the 'what' could be more specific and comprehensive.	4 / 5
Trigger Term Quality	'Invoice Ninja' is the natural keyword a user would say, and 'interact with Invoice Ninja data' is a reasonable phrase, but synonyms and variations (invoicing, billing, clients, expenses) are missing.	3 / 5
Distinctiveness Conflict Risk	Names a specific third-party product (Invoice Ninja), giving it a clear niche with distinct triggers and minimal overlap risk with other skills.	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/invoice-ninja/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.