moneybird
Moneybird integration via Apideck's Accounting unified API — same methods work across every connector in Accounting, switch by changing `serviceId`. Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Moneybird. Routes through Apideck with serviceId "moneybird".
75
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/moneybird/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies the specific integration (Moneybird via Apideck), lists concrete accounting operations (invoices, bills, payments, ledger accounts, journal entries), and provides an explicit 'Use when' clause with natural trigger terms. The mention of serviceId and the unified API pattern adds helpful technical context for disambiguation from other Apideck connectors.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: read, write, reconcile invoices, bills, payments, ledger accounts, and journal entries. Also specifies the integration mechanism (Apideck's Accounting unified API) and the serviceId parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (Moneybird integration via Apideck's Accounting unified API for invoices, bills, payments, etc.) and 'when' (explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Moneybird'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Moneybird', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', and 'Accounting'. These cover the terms a user working with Moneybird accounting would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Moneybird' and 'serviceId moneybird' via Apideck. While it could potentially overlap with other Apideck accounting connector skills, the Moneybird-specific naming and serviceId make it clearly distinguishable. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with good progressive disclosure and useful entity mapping, but suffers from significant verbosity — marketing language, repeated portability messaging, and explanations of concepts Claude already knows inflate the token count. Actionability is moderate with some executable examples but gaps in the proxy escape hatch and lack of workflow validation steps for multi-step operations like reconciliation.
Suggestions
Cut the 'Portable across 34 Accounting connectors' section entirely — the intro already states portability and the code difference is trivial; this saves ~15 lines of redundant content.
Remove the descriptive paragraph about Moneybird ('popular Dutch SMB accounting platform...') and the 'When to use this skill' section — Claude can infer activation context from the skill description and frontmatter.
Add a concrete proxy example with a real Moneybird endpoint URL (e.g., fetching quotes) instead of the placeholder '<target endpoint on Moneybird>'.
Add a brief workflow for a common multi-step task (e.g., create invoice → verify response → handle errors) with explicit validation checkpoints.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'Portable across 34 Accounting connectors' section repeats the portability concept already stated in the intro. The 'When to use this skill' section explains obvious things. Marketing language like 'compounding advantage' and explanations of what Moneybird is ('popular Dutch SMB accounting platform favored by freelancers') waste tokens on context Claude doesn't need. The sibling connectors list and repeated mentions of '34 connectors' add bulk without actionable value. | 1 / 3 |
Actionability | The TypeScript examples are executable and copy-paste ready, and the entity mapping table is concretely useful. However, the curl proxy example has a placeholder '<target endpoint on Moneybird>' without a real example, and much of the content describes rather than instructs (e.g., coverage highlights are informational rather than actionable). The filter example for overdue invoices is helpful but minimal. | 2 / 3 |
Workflow Clarity | There's no clear multi-step workflow with validation checkpoints. The skill implies a decision flow (check coverage → use unified API or fall back to Proxy) but doesn't sequence it explicitly with validation steps. For operations like creating invoices or reconciling payments, there are no error handling or verification steps described. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections and one-level-deep references to SDK skills, OpenAPI specs, best practices, and coverage checking tools. The 'See also' section and inline links to related skills are well-signaled and appropriately organized. Content is split logically between this overview and referenced materials. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- apideck-libraries/api-skills
- Commit
9e04d86
- Reviewed
Table of Contents
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.