netsuite
NetSuite 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 NetSuite. Routes through Apideck with serviceId "netsuite".
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 (NetSuite via Apideck), lists concrete accounting objects and actions, and provides an explicit 'Use when' clause with natural trigger terms. The additional context about serviceId switching and the unified API pattern adds useful disambiguation for skill selection. The description uses proper third-person voice throughout.
| 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 parameter. | 3 / 3 |
Completeness | Clearly answers both 'what' (NetSuite integration via Apideck's Accounting unified API for invoices, bills, payments, ledger accounts, journal entries) and 'when' (explicit 'Use when the user wants to read, write, or reconcile invoices, bills, payments, ledger accounts, and journal entries in NetSuite'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'NetSuite', 'invoices', 'bills', 'payments', 'ledger accounts', 'journal entries', 'reconcile', 'Apideck', and 'Accounting'. These cover the terms a user working with NetSuite accounting would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets NetSuite via Apideck with serviceId 'netsuite'. The mention of the specific connector, serviceId, and unified API pattern makes it clearly distinguishable from generic accounting skills or other ERP integrations. | 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 a clear entity mapping table. Its main weaknesses are some verbosity around the portability message (repeated in multiple sections) and the lack of explicit multi-step workflow guidance with validation checkpoints for common operations like invoice creation or payment reconciliation.
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 marketing language wastes tokens.
Add a brief workflow example for a common multi-step operation (e.g., create invoice → verify creation → handle 403 errors from role restrictions) with explicit validation checkpoints.
| 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 'When to use this skill' section also over-explains. However, the entity mapping table and coverage highlights are efficient. | 2 / 3 |
Actionability | Provides fully executable TypeScript examples for listing invoices, filtering by subsidiary, 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's supported vs. not. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks explicit workflow sequences for multi-step processes like reconciliation or invoice creation with validation. There are no validation checkpoints or error-handling feedback loops for operations that could fail (e.g., 403 on restricted roles is mentioned but no recovery steps are given). | 2 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear sections, and well-signaled one-level-deep references to SDK skills, OpenAPI specs, best practices, and connector coverage. Content is appropriately split between this connector-specific skill 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.