Name: hubspot
Rating: 59.2 (1 reviews)
Author: membranedev

hubspot

HubSpot integration. Manage crm and marketing automation data, records, and workflows. Use when the user wants to interact with HubSpot data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/hubspot/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable, anchored in copy-paste-ready Membrane CLI commands and a useful actions table, with a clear connect-and-poll workflow. It loses conciseness to introductory filler explaining HubSpot and Membrane's value, and could offload the action catalog to a reference file.

Suggestions

Trim the opening 'HubSpot is a CRM...' paragraph and the 'so you can focus on the integration logic rather than auth plumbing' filler; assume Claude knows what HubSpot is.

Move the popular-actions table into a references file (e.g. actions.md) and link to it from the body to improve progressive disclosure.

Add a brief validation/confirmation step after create/update actions (e.g. re-fetch the record or check the response status) to strengthen workflow checkpoints for mutating operations.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explains what HubSpot is and adds fluff like 'so you can focus on the integration logic rather than auth plumbing' that Claude does not need, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean 4.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure, action list/run, request) plus a concrete popular-actions table covering common cases, matching the top anchor for fully executable guidance.	5 / 5
Workflow Clarity	The install -> authenticate -> connect -> poll-for-ready -> search -> run sequence is clear with explicit state-checkpoints and feedback loops for connection readiness, but action-result validation for create/update operations is absent, fitting the 'clear sequence with most checkpoints, minor validation gaps' anchor.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested references, but the large popular-actions table is inlined rather than split into a reference file and no external references exist, matching the 'good structure, minor organization gaps' anchor rather than the cleanly split 5.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 clearly identifies HubSpot as the target and includes an explicit 'Use when' trigger, covering both what and when. It is held back by generic 'manage' phrasing and the absence of concrete entity terms (contacts, deals, companies, tickets) that users would naturally mention.

Suggestions

Replace the generic verb 'Manage' with concrete verbs tied to HubSpot entities, e.g. 'Create, update, and list contacts, companies, deals, and tickets'.

Expand the trigger clause with natural user phrases: 'Use when the user wants to work with HubSpot contacts, deals, companies, tickets, or CRM/marketing workflows'.

Capitalize 'CRM' and add the entity synonyms users actually say to improve trigger term coverage and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain ("crm and marketing automation") and a few actions ("Manage ... data, records, and workflows"), but "manage" is generic and coverage is not comprehensive, matching the anchor for naming a domain with 1-2 concrete actions.	3 / 5
Completeness	States both what ("Manage crm and marketing automation data, records, and workflows") and when ("Use when the user wants to interact with HubSpot data"), but the trigger clause is somewhat generic, matching the anchor where both are present but 'when' could be more specific rather than the fully concrete 5 anchor.	4 / 5
Trigger Term Quality	Includes relevant terms like "HubSpot", "crm", "marketing automation", and "HubSpot data", but misses common entity-specific natural terms users would say (contacts, deals, companies, tickets), fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named product "HubSpot" gives a clear, distinct niche with minimal conflict risk, but the broader "crm and marketing automation" framing leaves minor overlap risk with other CRM/marketing skills, so it sits just below the minimal-conflict 5 anchor.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/hubspot/SKILL.md
Commit: f484c82

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.