clearbooks-uk
Clear Books 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 Clear Books. Routes through Apideck with serviceId "clearbooks-uk".
84
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
92%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 well-structured description that clearly states what the skill does and when to use it, with good trigger terms covering both the product name and common accounting concepts. Its main weakness is the inherent overlap with other Apideck accounting connector skills, as the description itself acknowledges the methods are shared across connectors. The explicit 'Use when' clause and specific entity types make it functional for skill selection.
Suggestions
Consider emphasizing what makes Clear Books unique compared to other Apideck accounting connectors (e.g., UK-specific accounting features) to reduce conflict risk with sibling 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. | 3 / 3 |
Completeness | Clearly answers both 'what' (Clear Books integration for reading, writing, reconciling accounting objects via Apideck) and 'when' ('Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Clear Books'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'Clear Books', 'reconcile', 'Apideck', and 'clearbooks-uk'. Good coverage of accounting domain terms and the specific product name. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Clear Books' and 'clearbooks-uk' are distinctive, the description explicitly notes 'same methods work across every connector in Accounting, switch by changing serviceId,' which suggests high overlap with other Apideck accounting connector skills. The accounting actions listed (invoices, bills, payments) would be identical across many similar skills. | 2 / 3 |
Total | 11 / 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 good actionability through executable examples and excellent progressive disclosure via clear references to SDK skills and related resources. Its main weaknesses are moderate verbosity from marketing-style content about portability advantages and missing validation guidance for a beta connector where coverage gaps are explicitly acknowledged.
Suggestions
Remove or significantly trim the 'Portable across 34 Accounting connectors' section — the portability concept is already stated in the intro and the code example is redundant with the minimal example.
Add a concrete example of how to verify coverage before making a call (e.g., using the apideck-connector-coverage skill or a specific API call), since the beta status makes this critical.
Trim the 'When to use this skill' section to 1-2 lines — Claude doesn't need detailed activation instructions when the skill title and quick facts already convey the purpose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary verbosity — the 'Portable across 34 Accounting connectors' section is marketing-style explanation that Claude doesn't need, and the 'When to use this skill' section over-explains activation context. The entity mapping table and coverage highlights are valuable, but the promotional language about 'compounding advantage' wastes tokens. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, listing unpaid bills, and using the Proxy API escape hatch with a complete curl command. The serviceId, auth setup, and filter parameters are all concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The skill covers a connector integration rather than a multi-step destructive process, so deep workflow isn't strictly required. However, there's no validation/verification guidance — e.g., how to check if a resource is actually supported before calling it, or how to handle errors when hitting beta coverage gaps. The beta caveat mentions 'verify coverage' but doesn't show how. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick facts, minimal examples inline, and clear one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage tools. Navigation is well-signaled with links and the 'See also' section. | 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.