hubspot-automation
Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.
67
51%
Does it follow best practices?
Impact
96%
1.37xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/hubspot-automation/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear niche (HubSpot CRM via Composio) and lists relevant entity types, giving it good distinctiveness. However, it lacks specific action verbs (create, update, search, delete) and entirely omits a 'Use when...' clause, making it incomplete for skill selection purposes. The inclusion of implementation details ('Rube MCP', 'Composio integration') takes up space that could be used for user-facing trigger terms.
Suggestions
Add a 'Use when...' clause with natural trigger phrases like 'Use when the user asks about HubSpot, CRM contacts, sales deals, customer records, or managing a sales pipeline.'
Replace vague 'automate operations' with specific actions such as 'Create, update, search, and delete HubSpot CRM records including contacts, companies, deals, and tickets.'
Consider moving implementation details ('via Rube MCP using Composio integration') out of the description and replacing with user-facing terms like 'sales pipeline', 'lead management', or 'customer data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names the domain (HubSpot CRM) and lists entity types (contacts, companies, deals, tickets, properties) but doesn't describe specific actions beyond the vague 'automate operations'. It doesn't say what operations—create, update, delete, search, etc. | 2 / 3 |
Completeness | It describes what at a high level (automate HubSpot CRM operations) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes good natural keywords like 'HubSpot', 'CRM', 'contacts', 'companies', 'deals', 'tickets' that users would say. However, it also includes technical jargon ('Rube MCP', 'Composio integration') that users wouldn't naturally use, and misses common variations like 'sales pipeline', 'lead management', or 'customer records'. | 2 / 3 |
Distinctiveness Conflict Risk | HubSpot CRM is a very specific niche. The mention of HubSpot, specific entity types, and the Composio/Rube MCP toolchain makes it clearly distinguishable from other skills and unlikely to conflict. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
62%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-organized skill with clear workflow sequences and good labeling of step dependencies (Prerequisite/Required/Optional). Its main weaknesses are the lack of concrete executable examples (no JSON payloads or request/response samples) and significant repetition between per-workflow pitfalls and the consolidated Known Pitfalls section. The document would benefit from being split into a concise overview plus detailed reference files.
Suggestions
Add at least one concrete JSON payload example per core workflow (e.g., an exact HUBSPOT_CREATE_CONTACT call with properties object) to make guidance copy-paste ready.
Consolidate pitfalls into the single 'Known Pitfalls' section and remove per-workflow duplication, or vice versa, to reduce token usage by ~20%.
Split detailed workflow sections into separate reference files (e.g., contacts.md, deals.md) and keep SKILL.md as a concise overview with links, improving progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but has significant repetition — the 'Known Pitfalls' section largely restates pitfalls already listed under each workflow. The quick reference table adds value but the overall document could be tightened by ~30% without losing information. Some explanations (e.g., pagination pattern) are repeated across sections. | 2 / 3 |
Actionability | Provides specific tool names, parameter names, and clear tool sequences, which is good. However, there are no executable code examples or concrete JSON payloads showing exact request/response structures. The guidance is specific but not copy-paste ready — a user would still need to look up exact schemas. | 2 / 3 |
Workflow Clarity | Each workflow has a clearly numbered tool sequence with labeled steps (Prerequisite, Required, Optional, Alternative, Fallback). The setup section includes a verification step before proceeding. Duplicate prevention checks and auth verification serve as validation checkpoints. The sequences are well-ordered with clear dependencies. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's a monolithic document (~180 lines of dense content) with no bundle files to offload detail into. The per-workflow pitfalls and common patterns sections could be separate reference files. For a skill of this complexity, some content splitting would improve navigability. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- 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.