dualentry
Dualentry 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 Dualentry. Routes through Apideck with serviceId "dualentry".
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 accounting system (Dualentry), the integration mechanism (Apideck unified API), concrete actions (read, write, reconcile), and specific data types (invoices, bills, payments, ledger accounts, journal entries). It includes an explicit 'Use when' clause with natural trigger terms and is highly distinctive due to the named connector and serviceId.
| 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, serviceId). | 3 / 3 |
Completeness | Clearly answers both what ('read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Dualentry via Apideck') and when ('Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in Dualentry'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'Dualentry', 'reconcile', plus technical identifiers like 'serviceId "dualentry"' and 'Apideck' for more specific queries. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Dualentry' as the target system and 'serviceId "dualentry"' as the routing identifier. The mention of Apideck's unified API pattern and the specific connector name makes it clearly distinguishable from other accounting integration skills. | 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 code examples and excellent progressive disclosure via clear references to SDK skills and specs. Its main weaknesses are moderate verbosity from repeated portability messaging and missing validation/error-handling guidance for accounting operations that modify financial data.
Suggestions
Remove or consolidate the repeated portability explanations — the intro paragraph, 'Portable across 34 connectors' section, and sibling connectors section all say the same thing. One brief mention plus the sibling list is sufficient.
Add error handling guidance or a validation step after create/update operations (e.g., checking response status, verifying created resource ID) since these are financial data mutations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the repeated explanations of portability across connectors (mentioned in intro, dedicated section, and sibling connectors section) are redundant. The 'When to use this skill' section explains obvious things. However, the entity mapping table and code examples are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices and creating bills, a complete curl command for the proxy escape hatch, and a clear entity mapping table. Code is copy-paste ready with realistic field values. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks validation checkpoints — there's no guidance on verifying that a created bill/invoice was successful, no error handling patterns, and no feedback loops for failed API calls. For API operations that modify accounting data, this is a gap. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview, well-signaled references to SDK skills, OpenAPI specs, best practices, and connector coverage tools. All references are one level deep and clearly labeled with descriptive links. | 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.