exact-online
Exact Online 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. Routes through Apideck with serviceId "exact-online".
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 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 description is concise, uses third-person voice, and would be easily distinguishable from other skills in a large skill library.
| 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' (Exact Online integration via Apideck 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 Exact Online'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Exact Online', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', and 'serviceId exact-online'. These cover the terms a user working with Exact Online accounting would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets 'Exact Online' with serviceId 'exact-online' via Apideck, clearly distinguishing it from other accounting connectors or general accounting skills. The mention that the same methods work across connectors but are switched by serviceId further clarifies its niche. | 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.
A solid connector reference skill with good actionability through executable examples and excellent progressive disclosure via well-organized cross-references. Main weaknesses are moderate verbosity (repeated portability messaging, marketing language) and missing validation/error-handling guidance for financial API operations. The entity mapping table and auth notes are genuinely valuable Exact Online-specific content.
Suggestions
Remove or condense the 'Portable across 34 Accounting connectors' section — the portability point is already made in the intro and the code example could be folded into the minimal example section.
Add a brief error handling or validation step (e.g., checking connection status via Vault, verifying division selection) to help Claude catch common integration issues before making financial API calls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 34 Accounting connectors' section repeats the portability message already stated in the intro, and the marketing-style language ('compounding advantage') adds no actionable value. The entity mapping table and coverage highlights are useful, but the overall content could be tightened by ~30%. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, switching connectors, and using the Proxy API escape hatch with a complete curl command. The entity mapping table gives concrete resource names, and auth notes include specific operational details like division selection and regional variants. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/configuration skill rather than a multi-step workflow, but it lacks any validation or verification steps. For example, there's no guidance on checking connection status, verifying the correct division is selected, or handling errors from API calls — important for an integration that involves financial data. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure 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 regional variants are well-organized and clearly signaled. | 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.