myob
MYOB 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 MYOB. Routes through Apideck with serviceId "myob".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 (MYOB via Apideck), lists concrete accounting operations (read, write, reconcile invoices, bills, payments, etc.), 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. It uses proper third-person voice throughout.
| 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' (MYOB integration via Apideck's Accounting unified API for invoices, bills, payments, ledger accounts, journal entries) and 'when' (explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in MYOB'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'MYOB', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', and 'accounting'. These cover the main terms a user working with MYOB accounting would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets MYOB via Apideck with serviceId 'myob'. The combination of MYOB + Apideck + specific serviceId makes it very unlikely to conflict with other accounting or integration skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured connector skill with strong actionability through executable examples and excellent progressive disclosure via clear references to SDK skills and specs. Its main weaknesses are some marketing-style verbosity (portability pitch repeated twice) and missing validation/error-handling guidance for multi-step accounting workflows.
Suggestions
Remove or consolidate the 'Portable across 34 Accounting connectors' section — the portability point is already made in the intro paragraph; the duplicate code example wastes tokens.
Add a brief error handling note or validation step after the create invoice example (e.g., check response status, handle 422 validation errors from MYOB).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 34 Accounting connectors' section repeats the portability pitch already made in the intro, and the 'compounding advantage' paragraph is marketing fluff Claude doesn't need. The 'When to use this skill' section also over-explains. However, the entity mapping table and coverage highlights are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, creating invoices with AU-specific GST handling, and a curl command for proxy access to unsupported endpoints. The serviceId, env vars, and payload structures are all concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks workflow sequencing for multi-step processes like reconciliation. There are no validation checkpoints — e.g., no guidance on checking response status, verifying created invoices, or handling errors from the MYOB API. The coverage highlights with ⚠️/❌ markers partially compensate by guiding when to use Proxy. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. The 'See also' section and inline links to sibling connectors and language SDKs are well-signaled and appropriately organized. Content is split sensibly between this overview and referenced materials. | 3 / 3 |
Total | 10 / 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.