Name: invoiced
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

invoiced

Invoiced integration. Manage Organizations. Use when the user wants to interact with Invoiced data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/invoiced/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.

The body is highly actionable with concrete CLI commands and a clear connection workflow, but it carries some over-explanation of platform concepts and inlines a sizable action catalog that would benefit from a separate reference file. Adding validation/verification guidance for create/update operations would tighten the workflow.

Suggestions

Trim the platform-overview paragraph and connection-state prose to the minimum Claude cannot derive from CLI output, to improve conciseness.

Add explicit validation or error-recovery checkpoints for create/update/delete operations (e.g. confirm the returned object state after `action run`) to push workflow_clarity to 5.

Move the large popular-actions table into a separate reference file and link to it from a short summary, improving progressive disclosure toward 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command-driven guidance, but the opening section explains what Invoiced is as a platform and the connection-state walkthrough restates concepts that are largely derivable from CLI output, which could be tightened.	3 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection management, action search/run, and proxying, each with concrete flags and example payloads covering the common cases.	5 / 5
Workflow Clarity	The connection flow is clearly sequenced with state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED) and a polling loop, though destructive/batch operations like updates and creations lack explicit validation or error-recovery checkpoints.	4 / 5
Progressive Disclosure	Content is well-organized into labeled sections with inline examples and a popular-actions table, but there are no separate reference files for the large action catalog, which is inlined rather than split out.	4 / 5
	Total	16 / 20 Passed

Description

62%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 clear and distinct thanks to naming a specific platform, but it is light on concrete capabilities and natural trigger phrases. Adding concrete actions (invoices, payments, customers) and richer user-facing keywords would raise it toward the top anchors.

Suggestions

List several concrete capabilities in the description, e.g. 'create and send invoices, record payments, and manage customers and subscriptions', to improve specificity.

Replace the generic trigger with natural user phrasings, e.g. 'Use when the user asks about invoices, payments, billing, or accounts receivable in Invoiced', to improve trigger term quality.

Use third-person voice consistently and keep the 'Use when...' clause explicit but tied to concrete Invoiced-specific triggers rather than 'interact with Invoiced data'.

Dimension	Reasoning	Score
Specificity	It names the domain ("Invoiced integration") and one concrete action ("Manage Organizations") but lists no other concrete capabilities like invoicing, payments, or subscriptions, leaving coverage non-comprehensive.	3 / 5
Completeness	It states both what it does ("Invoiced integration. Manage Organizations") and when to use it ("Use when the user wants to interact with Invoiced data"), but the "when" is broad and could be more specific.	4 / 5
Trigger Term Quality	The only natural trigger phrase is "Use when the user wants to interact with Invoiced data," which is generic; it omits common synonyms like invoices, payments, billing, or accounts receivable that users would actually say.	3 / 5
Distinctiveness Conflict Risk	It is tied to a specific named platform (Invoiced), making it mostly distinct from other skills, though "interact with Invoiced data" is broad enough to risk minor overlap with a generic data-integration skill.	4 / 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/invoiced/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.