acumatica
Acumatica 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 Acumatica. Routes through Apideck with serviceId "acumatica".
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 (Acumatica via Apideck), lists concrete accounting operations (invoices, bills, payments, ledger accounts, journal entries), and provides explicit trigger guidance with a 'Use when' clause. The description also helpfully notes the unified API pattern and serviceId switching mechanism, which aids in distinguishing it from sibling connector skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or 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' (Acumatica integration via Apideck for accounting operations) and 'when' with an explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Acumatica.' | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Acumatica', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'accounting'. Also includes technical identifiers like 'serviceId' and 'acumatica' for precise matching. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of 'Acumatica' + 'Apideck' + serviceId 'acumatica'. While it could overlap with other Apideck accounting connectors, the explicit Acumatica naming and serviceId clearly distinguish it from other accounting integrations. | 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 a useful entity mapping table. Its main weaknesses are moderate verbosity (repeated portability messaging, marketing language) and missing error-handling/validation workflows that are important given the beta status of the connector. Progressive disclosure is handled well with clear references to related skills and documentation.
Suggestions
Remove or condense the 'Portable across 34 Accounting connectors' section — the portability point is already made in the intro and the code example adds little beyond what the minimal example shows.
Add a brief error handling/validation section showing how to check API responses and handle partial coverage failures, especially given the beta status warning.
Trim marketing-style language ('compounding advantage', 'powerful custom reports') to save tokens without losing information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 34 Accounting connectors' section repeats the portability concept already stated in the intro, and the 'When to use this skill' section over-explains activation triggers. The entity mapping table and coverage highlights are valuable, but the marketing-style language ('compounding advantage') wastes tokens. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing and creating invoices, a complete curl command for the Proxy API escape hatch, and a concrete entity mapping table. The serviceId, auth type, and SDK references are all specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks explicit validation checkpoints — there's no guidance on verifying API responses, handling errors from the beta connector, or checking coverage before making calls. For a beta connector where 'partial resource coverage and occasional mapping gaps' are expected, missing error-handling workflows is a notable gap. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage tools. The 'See also' section and inline links to sibling connectors and language SDKs are well-signaled and appropriately organized. | 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.