Hubspot Setup

Organization

LeadMagic

hubspot-setup

Set up HubSpot for B2B SaaS GTM — CRM configuration, deal pipelines, lifecycle stages, marketing automation, sequences, reporting dashboards, and enrichment integration. Use when configuring HubSpot for sales, marketing, or revops. Triggers on: "HubSpot setup", "configure HubSpot", "HubSpot CRM", "HubSpot pipeline", "HubSpot marketing", or any HubSpot configuration request.

Overview

Publisher	LeadMagic
Repository	`gtm-skills`
Skill name	`hubspot-setup`
Stars	72
Forks	18
Bundled files	3
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by LeadMagic on GitHub. Read the source before you install it.

Installation

Install the Hubspot Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/LeadMagic/gtm-skills/tree/main/skills/automation/hubspot-setup
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/LeadMagic/gtm-skills.git /tmp/gtm-skills
mkdir -p .claude/skills
cp -r /tmp/gtm-skills/skills/automation/hubspot-setup .claude/skills/hubspot-setup

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Hubspot Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Hubspot Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Hubspot Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

HubSpot Setup

Overview

HubSpot is the most popular CRM for SMB and mid-market B2B SaaS. Its strength is the unified platform: CRM, marketing, sales, and service in one system. Its weakness is that it's easy to configure poorly and hard to fix later. This skill covers setup for GTM teams: deal pipelines, lifecycle stages, marketing automation, reporting, and enrichment integration.

Authoritative Foundations

HubSpot Knowledge Base — Lifecycle stages — Define entry criteria for each lifecycle stage and let stages move forward only, so funnel reporting stays trustworthy.
HubSpot Academy — CRM setup — Configure objects, associations, properties, and pipelines before importing data or building workflows.
Winning by Design — Revenue Architecture — Bowtie lifecycle model — align sales, marketing, and CS on stage-based outcomes.

When to Use

"Set up HubSpot for our sales team"
"Configure HubSpot deal pipelines"
"Set up HubSpot marketing automation"
"Build HubSpot reports and dashboards"
"Integrate enrichment with HubSpot"

Step-by-Step Process

Load crm-toolkit first — confirm HubSpot fit (crm-selection), contacts-vs-leads (HubSpot uses Contacts only — lifecycle stages replace Salesforce Leads), and hubspot-blueprint (field and workflow catalog).

Phase 1: CRM Foundation

Contacts vs leads: HubSpot has no Lead object. Inbound records are Contacts with lifecycle stage = Lead until qualified. Do not duplicate records. See crm-toolkit → contacts-vs-leads reference.

Lifecycle stages: Subscriber → Lead → MQL → SQL → Opportunity → Customer → Evangelist. Define clear criteria for stage advancement. Never use "Other."

Deal pipeline stages: Customize per sales motion. Standard: New → Contact Made → Discovery → Demo → Proposal → Negotiation → Closed Won / Closed Lost. Each stage: required fields (Amount, Close Date, Next Step).

Contact/Company properties: Standardize naming. Add custom properties: ICP fit score, enrichment status (pending/enriched/verified), lead source detail, MEDDICC dimensions for enterprise.

Phase 2: Marketing Hub

Email marketing: Lists by lifecycle stage. Sequences for nurture. Templates with brand consistency. A/B testing on subject lines.

Forms: Embedded on website, pop-ups, landing pages. Map form fields to contact properties. Auto-enrich on form fill via webhook to enrichment provider.

Lead scoring: HubSpot score based on fit (company properties) + engagement (Page views, email clicks, form fills). Threshold: score >X triggers MQL.

Phase 3: Sales Hub

Sequences: Automated email follow-up sequences. Personalization tokens. Task creation for calls and LinkedIn touches. Unenroll on reply.

Meeting scheduler: HubSpot meetings integration. Round-robin or rep-specific. Embed on website and in email signatures.

Playbooks: Guided selling for reps. Discovery questions, objection handling, competitive positioning. Triggered by deal stage.

Phase 4: Reporting

Dashboards: Sales (pipeline, forecast, rep activity), Marketing (traffic, conversions, MQLs), RevOps (pipeline velocity, conversion rates, data health).

Key reports: Pipeline generation by source, MQL→SQL conversion rate, average deal velocity by stage, win rate by source and rep, forecast accuracy.

Phase 5: Enrichment Integration

Clay → HubSpot: One-direction push. Clay enriches, pushes to HubSpot. Use clay_status property to gate: only verified records enter sequences. Never two-way sync.

LeadMagic integration: Verify emails on form fill. Enrich companies on contact create. Automate via webhook: webhook fires enrichment, results write back to HubSpot properties.

Output Format

HubSpot configuration document with: lifecycle stage definitions, deal pipeline map, required fields per stage, marketing automation flows, dashboard specs, and enrichment integration setup.

Quality Check

Lifecycle stages defined with clear advancement criteria
Deal pipelines configured with required fields per stage
Lead scoring model active (fit + engagement)
Enrichment integration: one-direction push from Clay to HubSpot
Dashboards built for all three functions (sales, marketing, revops)
Data quality: no duplicate contacts, no missing required fields

Common Pitfalls

No stage criteria. "We think they're an MQL" creates chaos. Define hard criteria: "ICP fit confirmed + demo requested = SQL."
Too many required fields. Reps skip CRM updates when every field is mandatory. Required: Amount, Close Date, Next Step. Everything else optional.
Two-way sync with enrichment. Clay-enriched data should flow to HubSpot, not back. Two-way sync creates data conflicts.
Default HubSpot lifecycle stages. Customize stages to your business. "Subscriber" and "Other" don't map to any real process.
No data hygiene cadence. Quarterly: deduplicate contacts, re-verify emails >90 days old, audit required fields completion.

Execution Artifacts

references/framework-notes.md — named frameworks, citation anchors, and operating assumptions
templates/output-template.md — copy-paste deliverable structure for the user
scripts/check-output.py — local checklist validator for required sections This skill includes lightweight artifacts the agent can load on demand: Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

Related Skills

crm-toolkit: Selection, contacts-vs-leads, hubspot-blueprint, partners
crm-integration: CRM configuration principles
pipeline-management: Deal stage design
salesforce-setup: Salesforce alternative (Lead object model)
attio-setup: Attio alternative (lists + status)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Hubspot Setup AI skill do?

Why use Hubspot Setup on TypingMind?

Because you install it once and use it with any model. Hubspot Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Hubspot Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/LeadMagic/gtm-skills/tree/main/skills/automation/hubspot-setup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Hubspot Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Hubspot Setup?

As many as you like. As long as a model supports skills, you can use Hubspot Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Hubspot Setup AI skill free?

Yes. It is published on GitHub by LeadMagic under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Landing Report

garrytan

CommunityPopular

Read-only queue dashboard for workspace-aware ship. (gstack)

Gstack Openclaw Ceo Review

garrytan

CommunityPopular

Use when asked to review a plan, challenge a proposal, run a CEO review, poke holes in an approach, think bigger about scope, or decide whether to expand or reduce the plan.

Caveman Stats

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

HubSpot Setup

Overview

Authoritative Foundations

When to Use

Step-by-Step Process

Phase 1: CRM Foundation

Phase 2: Marketing Hub

Phase 3: Sales Hub

Phase 4: Reporting

Phase 5: Enrichment Integration

Output Format

Quality Check

Common Pitfalls

Execution Artifacts

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now