intuit-enterprise-suite
Intuit Enterprise Suite 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 Intuit Enterprise Suite. Routes through Apideck with serviceId "intuit-enterprise-suite".
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 an excellent skill description that clearly identifies the specific integration target (Intuit Enterprise Suite via Apideck), lists concrete accounting operations (read, write, reconcile invoices, bills, payments, ledger accounts, journal entries), and provides explicit trigger guidance. The mention of the unified API pattern and serviceId switching adds useful context for disambiguation from similar Apideck connector skills.
| 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 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 Intuit Enterprise Suite'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'Intuit Enterprise Suite', 'reconcile', 'Apideck', and the specific serviceId. Good coverage of accounting domain terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific product name 'Intuit Enterprise Suite' and the explicit serviceId 'intuit-enterprise-suite'. While it shares the Apideck Accounting unified API pattern with other connectors, the product-specific naming and serviceId make 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 solid connector reference skill with strong actionability through executable examples and excellent progressive disclosure via well-organized cross-references. Its main weaknesses are moderate verbosity (repeated portability messaging, marketing language) and lack of error handling/validation guidance for API operations. The entity mapping table and proxy escape hatch are particularly valuable additions.
Suggestions
Remove or condense the 'Portable across 34 Accounting connectors' section — the portability point is already made in the intro paragraph; the code example showing serviceId swap could be folded into the minimal example.
Add a brief error handling note (e.g., what to check when a 4xx/5xx comes back, how to verify the connection is active) to improve workflow clarity for integration tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 34 Accounting connectors' section repeats the portability message already stated in the intro, and the marketing-style language ('compounding advantage') adds no actionable value. The entity mapping table and coverage highlights are useful but the surrounding prose could be tighter. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples with proper imports, environment variables, and serviceId usage. The entity mapping table, proxy API curl command, and SDK references give Claude concrete, copy-paste-ready guidance for multiple scenarios. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/configuration skill rather than a multi-step workflow, so explicit validation steps are less critical. However, there's no guidance on error handling, verifying connection status, or validating responses — which matters for API integration tasks. The 'When to use this skill' section provides decent decision logic but lacks a clear operational sequence. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview structure, well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. Content is appropriately split between this connector-specific file and the referenced SDK/best-practices skills. | 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.