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

moneybird

Moneybird integration. Manage Contacts, LedgerAccounts, FinancialMutations. Use when the user wants to interact with Moneybird 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/moneybird/SKILL.md

Quality

Content

67%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 delivers executable, well-sequenced guidance for connecting to Moneybird and running actions, with good structural organization and explicit state-handling checkpoints. It is slightly held back by marketing-style padding and some content that over-explains what Claude already knows.

Suggestions

Remove the marketing-style overview paragraph ('Moneybird is an online accounting software designed for small business owners...') and the bare resource-type list, which explain concepts Claude does not need.

Tighten the connection-state guidance so each state branch is stated once rather than restated across sections, reducing repeated content.

Move the full popular-actions table into a separate references file (with a few key examples inline) to improve token efficiency and lift the progressive-disclosure score.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with command examples and tables, but it pads areas Claude already knows (a marketing-style paragraph on what Moneybird is, an overview of resource types with no instruction) and repeats connection-state guidance that could be trimmed.	3 / 5
Actionability	It provides concrete, executable commands for installing the CLI, authenticating, ensuring a connection, listing and running actions, and proxying requests, with most gaps being minor (e.g., the popular-actions table keys but no full input example for each).	4 / 5
Workflow Clarity	The connect-to-Moneybird sequence is clearly ordered with polling steps and explicit state branches (READY, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a feedback loop (poll again after the user acts), which are strong checkpoints; only minor sequencing gaps remain before action execution.	4 / 5
Progressive Disclosure	Content is organized into well-labeled sections (Install, Authentication, Connecting, Searching actions, Popular actions, Proxy, Best practices) with no bundle files to split out; structure is clear and one-level-deep, though the long popular-actions table could be a candidate for a separate reference.	4 / 5
	Total	15 / 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 specific to the Moneybird product and includes an explicit 'Use when' trigger, satisfying both the what and when requirements. It is somewhat generic on action coverage and lacks natural synonyms, but is clearly distinct from other skills.

Suggestions

Expand the action coverage beyond 'Manage' to mention concrete operations like creating/sending invoices, recording expenses, or filing VAT returns for a higher specificity score.

Add natural user-facing trigger terms and synonyms such as 'accounting', 'invoices', 'expenses', or 'VAT returns' that users might actually say when they need this skill.

Broaden the trigger clause beyond 'interact with Moneybird data' to include specific scenarios (e.g., when the user wants to send invoices or reconcile transactions) to lift completeness toward 5.

Dimension	Reasoning	Score
Specificity	The description names the domain (Moneybird integration) and three concrete resource types (Contacts, LedgerAccounts, FinancialMutations), but lists only a narrow subset of actions ('Manage') rather than comprehensive coverage of the platform's capabilities.	3 / 5
Completeness	It clearly states both what (Moneybird integration managing Contacts, LedgerAccounts, FinancialMutations) and when ('Use when the user wants to interact with Moneybird data'), satisfying the anchor for both 'what' and 'when' even though the 'when' clause is fairly generic.	4 / 5
Trigger Term Quality	It mentions the natural product name 'Moneybird' and a reasonable trigger phrase ('when the user wants to interact with Moneybird data'), but lacks synonyms or common phrasings users might say such as 'accounting', 'invoices', or 'expenses'.	3 / 5
Distinctiveness Conflict Risk	Naming a specific named product (Moneybird) gives it a clear niche and low conflict risk with generic accounting skills, with only minor overlap risk against other accounting integrations.	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/moneybird/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.