exact-online-nl
Exact Online NL 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 Exact Online NL. Routes through Apideck with serviceId "exact-online-nl".
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 (Exact Online NL 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 switching adds useful context for distinguishing this from other Apideck connectors. Minor improvement could be made by mentioning file formats or specific API endpoints, but overall this is well-crafted.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries'. Also mentions the unified API pattern and serviceId switching mechanism. | 3 / 3 |
Completeness | Clearly answers both what ('integration via Apideck's Accounting unified API' with specific operations) and when ('Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Exact Online NL'). Explicit 'Use when' clause is present. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Exact Online NL', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', 'Accounting'. These cover the domain well and match what users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Exact Online NL' as a specific connector, the serviceId 'exact-online-nl', and routing through Apideck. This clearly distinguishes it from other accounting integrations or generic accounting skills, though it could potentially overlap with a general Apideck Accounting skill — the specific serviceId and product name mitigate this. | 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 with good actionability through executable examples and excellent progressive disclosure via well-organized cross-references. Its main weaknesses are moderate verbosity from repeated portability messaging and marketing language, plus a workflow that could benefit from explicit validation checkpoints when dealing with beta connector coverage gaps.
Suggestions
Remove or condense the 'Portable across 34 Accounting connectors' section — the intro already establishes portability, and the repeated examples add tokens without new information.
Add an explicit workflow sequence: 1. Check coverage → 2. If supported, call unified API → 3. If UnsupportedOperationError, use Proxy → 4. Verify response, with concrete error-handling code for the beta status.
| 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 'When to use this skill' section over-explains activation triggers. The sibling connectors list and marketing-style language ('compounding advantage') add tokens without actionable value. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, filtering by date, verifying coverage via curl, and using the Proxy API escape hatch. The code is copy-paste ready with real SDK imports, environment variables, and correct serviceId values. | 3 / 3 |
Workflow Clarity | The skill covers a clear workflow pattern (verify coverage → use unified API → fall back to Proxy), but lacks explicit validation checkpoints or error-handling feedback loops. The coverage verification step is mentioned but not integrated into a sequenced workflow with clear 'if unsupported, then do X' branching. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview and well-signaled one-level-deep references to SDK skills, connector coverage skill, best practices skill, OpenAPI specs, and the exact-online sibling skill for the full entity mapping table. Navigation is clear and references are consistently formatted. | 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.