Name: xero
Rating: 64.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

xero

Xero integration. Manage accounting data, records, and workflows. Use when the user wants to interact with Xero data.

Quality

78%

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/xero/SKILL.md

Quality

Content

82%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 well-structured, highly actionable CLI integration guide with copy-paste commands and a strong, validated connection workflow. The main weaknesses are minor verbosity in the intro, a missing verification step for write operations, and a dangling 'Step 2' reference.

Suggestions

Add a verification checkpoint after write actions, e.g. 'After create-invoice, run get-invoice to confirm it was created'.

Resolve the dangling 'Step 2' reference by adding a matching 'Step 2: Search and run actions' heading or rewording the skip pointer.

Trim the opening descriptive paragraph about what Xero is, since Claude already knows the product.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, executable commands and tables, with only minor over-explanation (the opening 'Xero is a cloud-based accounting software platform...' paragraph and the 'so you can focus on integration logic rather than auth plumbing' aside) that could be trimmed; not a 5 because of those padded spots.	4 / 5
Actionability	Commands are copy-paste ready and cover the common cases end-to-end (install, login, connection ensure, action list, action run with JSON input, request proxy with a full flag table), and the popular-actions table supplies concrete action keys.	5 / 5
Workflow Clarity	The connection flow is sequenced with explicit checkpoints and a feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, inspect error states), but a post-run verification step for create/update actions is missing and the dangling 'Step 2' reference has no matching heading, keeping it below 5.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested/multi-level references, but at ~178 lines the large popular-actions table and detailed connection state machine are inlined rather than split into one-level-deep reference files, so it does not reach the ideal 5.	4 / 5
	Total	17 / 20 Passed

Description

73%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 solid, third-person description that clearly signals its Xero-specific niche and includes an explicit 'Use when' trigger. It is held back from the top band by a generic 'Manage' verb and a narrow trigger clause that omit concrete accounting actions like invoicing or contacts.

Suggestions

Replace the generic 'Manage accounting data, records, and workflows' with concrete actions, e.g. 'Create and retrieve invoices, contacts, and bank transactions in Xero'.

Broaden the trigger clause to name natural synonyms: 'Use when the user wants to work with Xero invoices, contacts, bank transactions, or accounting data'.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates several objects ('accounting data, records, and workflows') but uses only one generic verb ('Manage'), so it sits between the minimal-actions anchor (2) and the 1-2 concrete actions anchor (3), leaning up because multiple object types are listed.	3 / 5
Completeness	Both 'what' ('Manage accounting data, records, and workflows') and 'when' ('Use when the user wants to interact with Xero data') are present and explicit, but the 'when' clause is narrow and the 'what' is generic, so it does not reach the comprehensive trigger-phrase level of 5.	4 / 5
Trigger Term Quality	'Xero' and 'accounting' are natural terms a user would say, giving good keyword coverage; it stops short of 5 because natural synonyms like 'invoices', 'bookkeeping', or 'bills' are absent from the description.	4 / 5
Distinctiveness Conflict Risk	'Xero integration' plus 'interact with Xero data' carves out a clear, product-specific niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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/xero/SKILL.md
Commit: f484c82

Reviewed: ~22 hours 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.