microsoft-dynamics-365-business-central
Microsoft Dynamics 365 Business Central 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 Microsoft Dynamics 365 Business Central. Routes through Apideck with serviceId "microsoft-dynamics-365-business-central".
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 an excellent skill description that clearly identifies the specific platform (Microsoft Dynamics 365 Business Central), the integration mechanism (Apideck unified API), concrete actions (read, write, reconcile), specific entity types (invoices, bills, payments, ledger accounts, journal entries), and explicit trigger guidance. It uses proper third-person voice and provides enough detail for Claude to confidently select this skill from a large pool of accounting-related 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' (Microsoft Dynamics 365 Business Central integration via Apideck for reading, writing, reconciling accounting entities) and 'when' (explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Microsoft Dynamics 365 Business Central'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'Microsoft Dynamics 365 Business Central', 'reconcile', 'Apideck', and the specific serviceId. Good coverage of both the platform name and accounting domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform name 'Microsoft Dynamics 365 Business Central', the specific serviceId, and the Apideck routing mechanism. Unlikely to conflict with other accounting skills unless there are other Dynamics 365 BC connectors, and even then the serviceId differentiates it. | 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 solid connector-specific skill that excels at actionability with executable code examples and progressive disclosure with well-organized references. Its main weaknesses are moderate verbosity (repeating the full product name excessively, marketing-style prose about portability) and missing validation/error-handling steps in workflows. The entity mapping table and auth notes add genuine value specific to this connector.
Suggestions
Use 'BC' abbreviation after the first full mention of 'Microsoft Dynamics 365 Business Central' to reduce token usage significantly — the full name appears ~20 times.
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 validation/error handling after the create invoice example (e.g., check response status, handle common BC-specific errors like missing VAT posting setup).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the repeated full name 'Microsoft Dynamics 365 Business Central' throughout (could use 'BC' after first mention), the marketing-style paragraph about 'compounding advantage', and the 'When to use this skill' section explaining when to activate it are somewhat redundant. The entity mapping table and coverage highlights are valuable, but the portability section repeats the same point multiple times. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing and creating invoices, a complete curl command for the proxy escape hatch, correct serviceId strings, and a detailed entity mapping table. The code is copy-paste ready with realistic parameters. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks workflow sequencing for multi-step processes like invoice reconciliation. Auth notes mention admin consent caveats but don't provide a clear step-by-step for handling the 'Need admin approval' scenario. No validation checkpoints are provided for operations like invoice creation (e.g., checking response status, verifying the created entity). | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with clear, well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. The 'See also' section is well-organized and the sibling connectors section provides navigation to related skills. | 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.