digits
Digits 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 Digits. Routes through Apideck with serviceId "digits".
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 (Digits via Apideck), lists concrete accounting operations (invoices, bills, payments, ledger accounts, journal entries), and provides explicit trigger guidance with a 'Use when' clause. The mention of serviceId switching and the specific service name 'digits' make it highly distinguishable from similar Apideck accounting connector 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 pattern. | 3 / 3 |
Completeness | Clearly answers both 'what' (Digits integration via Apideck's Accounting unified API for invoices, bills, payments, etc.) and 'when' (explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Digits'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Digits', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', 'Accounting'. These cover common variations of accounting-related requests targeting Digits specifically. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific mention of 'Digits' as the target service, the serviceId 'digits', and the Apideck routing mechanism. This clearly differentiates it from other accounting connector skills that would use different serviceIds. | 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 well-structured connector skill with strong actionability through executable examples and excellent progressive disclosure via clear references to SDK skills and specs. Its main weaknesses are moderate verbosity from repeated portability messaging and marketing language, plus missing validation/error-handling guidance for a beta connector where partial coverage and mapping gaps are explicitly acknowledged.
Suggestions
Remove or consolidate the 'Portable across 34 Accounting connectors' section — the portability point is already made in the intro and the sibling connectors section; the repeated examples and marketing copy waste tokens.
Add a brief validation step or error-handling pattern for dealing with the beta connector's partial coverage (e.g., check response status, handle 'not supported' errors gracefully) to improve workflow clarity.
| 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 context. The marketing-style language ('compounding advantage') adds no actionable value. However, the entity mapping table and coverage highlights are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, fetching P&L, and using the Proxy API escape hatch with a complete curl command. The entity mapping table and coverage highlights give concrete, specific guidance on what works and what doesn't with Digits. | 3 / 3 |
Workflow Clarity | The skill clearly explains what's supported vs. not and provides an escape hatch workflow, but lacks explicit validation steps. For instance, there's no guidance on checking API responses for errors, verifying coverage programmatically before making calls, or handling the beta connector's 'occasional mapping gaps' mentioned in the callout. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in the skill itself and well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, connector coverage tools, and official docs. The 'See also' section is clean and navigable. | 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.