exact-online-uk
Exact Online UK 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 UK. Routes through Apideck with serviceId "exact-online-uk".
75
71%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./connectors/exact-online-uk/SKILL.mdQuality
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 UK 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 and the unified API pattern adds helpful context for disambiguation from other Apideck accounting connectors.
| 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 listed) and when ('Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Exact Online UK'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Exact Online UK', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', 'Accounting'. These cover the terms a user working with this specific integration would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Exact Online UK' as a specific connector, the serviceId 'exact-online-uk', and the Apideck routing context. This clearly distinguishes it from other accounting integrations or generic accounting skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has excellent progressive disclosure with well-organized references to related skills and resources, but suffers from significant verbosity — marketing language, repeated portability messaging, and explanations of unified API concepts that Claude doesn't need. Actionability is moderate: code examples exist but key ones are misleading (the '30 days' example) and critical details are deferred elsewhere. The workflow for handling unsupported operations could be more explicit.
Suggestions
Remove the 'Portable across 34 Accounting connectors' section entirely — the intro already establishes portability, and the sibling connectors section reinforces it. This would save ~15 lines of redundant content.
Fix the misleading 'list customers with invoices due in 30 days' example — either implement actual date filtering or rename the section to match what the code does ('list open invoices').
Add an explicit workflow sequence: 1. Check coverage → 2. Call unified API → 3. Handle UnsupportedOperationError → 4. Fall back to Proxy API, with a concrete error-handling code snippet.
Trim the 'When to use this skill' section to just the serviceId and SDK cross-references — Claude doesn't need instructions on when to activate itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Significant verbosity throughout. The 'Portable across 34 Accounting connectors' section repeats what's already stated in the intro. Marketing-style language ('compounding advantage') and explanations of concepts Claude already knows (what a unified API is, why portability matters) waste tokens. The 'When to use this skill' section over-explains activation criteria. | 1 / 3 |
Actionability | Provides executable TypeScript examples and curl commands, but key details are deferred to other skills (exact-online for entity mapping, SDK skills for parameters/pagination). The 'list customers with invoices due in 30 days' example doesn't actually filter by due date despite its heading. Coverage verification and proxy examples are concrete and useful. | 2 / 3 |
Workflow Clarity | There's an implicit workflow: check coverage → use unified API → fall back to proxy if unsupported. However, there's no explicit validation/error handling sequence. The coverage check and proxy fallback are mentioned but not tied together into a clear decision flow with checkpoints. Missing feedback loops for handling UnsupportedOperationError. | 2 / 3 |
Progressive Disclosure | Well-structured with clear one-level-deep references to SDK skills, connector coverage skill, best practices skill, and the exact-online sibling for entity mapping. Navigation is easy with clearly signaled links. Content is appropriately split between this overview and referenced materials. | 3 / 3 |
Total | 8 / 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.