banqup
banqUP 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 banqUP. Routes through Apideck with serviceId "banqup".
87
86%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
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 (banqUP via Apideck), lists concrete accounting operations, and provides explicit trigger guidance. The mention of serviceId and the unified API pattern helps Claude understand both when to use this skill and how it relates to other Apideck connectors. The description is concise yet comprehensive.
| 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' (integration with banqUP via Apideck for accounting operations) and 'when' ('Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in banqUP'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'banqUP', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', 'accounting', and the serviceId 'banqup'. Good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific connector name 'banqUP' and serviceId 'banqup'. While it shares the Apideck Accounting unified API pattern with other connectors, the explicit naming of the service makes it clearly distinguishable. | 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 clear progressive disclosure via well-organized references. Its main weaknesses are moderate verbosity from repeated portability messaging and marketing language, plus a lack of explicit validation/error-handling workflows for a beta connector where failures are expected.
Suggestions
Remove or consolidate the 'Portable across 34 Accounting connectors' section — the intro already explains portability, and the code example showing serviceId swaps could be folded into the minimal example section.
Add a brief error handling/validation step after the create invoice example, e.g., checking the response status and handling common beta connector errors like unsupported fields.
| 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 triggers. The marketing-style language ('compounding advantage') wastes tokens. However, the coverage table and examples are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing and creating invoices, a complete curl command for the Proxy API escape hatch, and specific serviceId values. The entity mapping table and coverage highlights give concrete, actionable guidance on what works and what doesn't. | 3 / 3 |
Workflow Clarity | The coverage table clearly signals what's supported vs. not, and the Proxy escape hatch provides a fallback path. However, there's no explicit validation workflow — e.g., no guidance on checking API responses for errors, verifying invoice creation succeeded, or handling partial coverage gaps systematically. For a connector marked beta with known gaps, a verify-then-proceed workflow would be important. | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, quick facts, minimal example up front, then deeper sections. References to SDK skills, OpenAPI specs, best practices, and connector coverage are all one level deep and clearly signaled with links. Content is appropriately split between this file and referenced resources. | 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.