hubspot
HubSpot integration via Apideck's CRM unified API — same methods work across every connector in CRM, switch by changing `serviceId`. Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in HubSpot. Routes through Apideck with serviceId "hubspot".
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 platform (HubSpot via Apideck), lists concrete actions and entities, and includes an explicit 'Use when' clause with natural trigger terms. The description is concise yet comprehensive, uses third person voice correctly, and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions ('read, write, or search') and specific entities ('contacts, companies, leads, opportunities, activities, and pipelines'). Also mentions the technical mechanism (Apideck unified API, serviceId). | 3 / 3 |
Completeness | Clearly answers both 'what' (HubSpot integration via Apideck's CRM unified API for reading, writing, searching CRM entities) and 'when' ('Use when the user wants to read, write, or search contacts, companies, leads, opportunities, activities, and pipelines in HubSpot'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'HubSpot', 'contacts', 'companies', 'leads', 'opportunities', 'activities', 'pipelines', 'CRM', 'Apideck'. These cover the main terms a user would naturally use when requesting HubSpot CRM operations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets HubSpot via Apideck with serviceId 'hubspot'. The mention of the specific connector, API platform, and serviceId makes it clearly distinguishable from other CRM skills or other Apideck connectors. | 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-specific skill with strong actionability through executable examples and excellent progressive disclosure via well-organized references. Its main weaknesses are moderate verbosity from repeated marketing messaging about portability and missing validation/error-handling guidance for write operations. Trimming promotional content and adding a brief error-handling checkpoint would elevate it significantly.
Suggestions
Remove or consolidate the 'Portable across 21 CRM connectors' section — the portability point is already made in the intro and the sibling connectors section; the repeated marketing pitch wastes tokens.
Add a brief validation/error-handling note for write operations (e.g., check response status, handle 429 rate limits, verify associations were created), especially since the skill covers create operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity — the 'Portable across 21 CRM connectors' section repeats the marketing pitch about portability that's already stated in the intro, and phrases like 'This is the compounding advantage of using Apideck over integrating HubSpot directly' are promotional rather than instructional. The entity mapping table and coverage highlights are useful, but the 'When to use this skill' section over-explains when activation is obvious from context. | 2 / 3 |
Actionability | The skill provides fully executable TypeScript examples for listing contacts, creating contacts with associations, listing open deals with filters, 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. what requires the Proxy. | 3 / 3 |
Workflow Clarity | The skill covers individual operations well but lacks explicit workflow sequencing for multi-step processes like setting up a connection, validating auth, then performing operations. There are no validation checkpoints — e.g., no guidance on checking connection status before making calls, or verifying that a created contact was successfully associated. For a CRM integration skill involving writes, some error handling/validation guidance would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure — the skill provides a concise overview with clear, well-signaled one-level-deep references to SDK skills, OpenAPI specs, API Explorer, best practices, and connector coverage tools. The 'See also' section and inline links to sibling connectors and language SDK skills are well-organized for navigation. | 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.