hubspot

Use only when a focused Sales workflow has selected a connected HubSpot CRM, or the user explicitly asks for HubSpot guidance, reads, drafts, notes, or reviewed record changes. Do not use when another CRM is authoritative.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

88%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.

Excellent operational content: concrete connector-tool boundaries, specific batch and search limits, an unambiguous read/draft/approved-write workflow with validation checkpoints, and per-mode output templates. Remaining issues are minor — a malformed anchor link, a struck-through bullet, and a few trimmable filler sentences.

Dimension	Reasoning	Score
Conciseness	The body is dense and prescriptive with no explanations of concepts Claude already knows, but a few sentences could be trimmed ('use your best judgment to potentially include other data sources to improve quality', 'These are particularly important for this workflow') and one bullet is struck through rather than removed.	4 / 5
Actionability	Fully concrete guidance: exact tool names (get_user_details, search_properties, get_crm_objects, manage_crm_objects), specific limits ('at most five focused keywords', 'Batch at most 10 objects'), and copy-paste output format templates for each of the three modes.	5 / 5
Workflow Clarity	Clear three-phase sequence with explicit checkpoints for batch/destructive operations: an approval gate ('Write only after the user explicitly approves the exact reviewed change'), post-write verification ('Inspect the write response and verify with a narrow read'), ambiguity handling, and fallback behavior for unsupported surfaces.	5 / 5
Progressive Disclosure	A well-organized single-file skill that appropriately delegates shared sections to one-level-deep ../index/SKILL.md anchors, but the first cross-reference is malformed ('index/SKILL.md## Cross-Skill Best Practices' is missing a '#' anchor) and the three full output-format templates are all inlined.	4 / 5
	Total	18 / 20 Passed

Description

87%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.

A strong description: explicit trigger conditions, concrete action categories, third-person voice, and an explicit negative trigger that resolves conflict with sibling CRM skills. The only gap is missing natural object-level synonyms (deal, contact, company, ticket) that users commonly say.

Dimension	Reasoning	Score
Specificity	The description names several concrete action categories ('HubSpot guidance, reads, drafts, notes, or reviewed record changes') rather than generic language, but coverage is not comprehensive — it never mentions the core CRM objects (deals, contacts, companies, tickets) it actually handles per the body.	4 / 5
Completeness	It explicitly answers both 'when' ('Use only when a focused Sales workflow has selected a connected HubSpot CRM, or the user explicitly asks for...') and 'what' (guidance, reads, drafts, notes, reviewed record changes) with concrete trigger phrases, plus an explicit do-not-use condition.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('HubSpot', 'CRM', 'reads', 'drafts', 'notes', 'Sales workflow'), but common variations users would actually say — deal, contact, company, ticket — are missing.	4 / 5
Distinctiveness Conflict Risk	Clear vendor-specific niche (HubSpot CRM) gated to a parent Sales workflow, with an explicit disambiguation clause ('Do not use when another CRM is authoritative') that actively prevents wrong-skill triggering.	5 / 5
	Total	18 / 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
relative_links	Relative link issues: 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: XiaomiMiMo/MiMo-Code
Path: packages/opencode/src/skill/builtin/.bundle/sales/workflows/hubspot/SKILL.md
Commit: f0293bf

Reviewed: 2 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.