hubspot
Skill1 starsChanged 50 days agoMITView on GitHub
Analyze HubSpot CRM and marketing data through Windsor.ai. Use when the user asks about their HubSpot contacts, companies, deals, pipeline stages, deal value, owners, lead sources, or marketing email and campaign metrics (opens, clicks, conversions, revenue). This connector is read-only — it has no write actions and cannot create or edit records or send emails. Do not use for other CRMs (Salesforce, GoHighLevel), outbound messaging, or ad-platform performance data.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- thensls/nsls-builder-toolkittheir own version, first seen Nov 8, 2026
- Shanksg/clawskillstheir own version, first seen Nov 1, 2026
- HybridAIOne/hybridclawtheir own version, first seen Oct 13, 2026
- jholhewres/devclaw-skillstheir own version, first seen Oct 9, 2026
- apideck-libraries/api-skillstheir own version, first seen Aug 13, 2026
Used with
Projects with it also use posthog, discord and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillposthog
Analyze product data and manage product tooling in PostHog. Use when the user wants product analytics or insights, HogQL/SQL queries, feature flags, experiments and A/B tests, error tracking, session replay, surveys, LLM analytics, dashboards, data warehouse, or PostHog documentation.
Also in 3 projects that use this
jiulingyunSkilldiscord
Discord ops via the message tool (channel=discord).
Also in 3 projects that use this
MicrosoftSkilljira
Jira issue workflows for search, issue updates, transitions, comments, field discovery, and interactive credential setup via the Jira REST API. Use when you need to configure Jira access, search with JQL, inspect an issue, create or update work items, move an issue between statuses, post comments, or discover required fields for issue creation.
Also in 4 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- OpenClaudia/openclaudia-skills★ 731same name
- refly-ai/refly-skills★ 204same name
- HybridAIOne/hybridclaw★ 159same name
- alanalvestech/hitank★ 38same name
- apideck-libraries/api-skills★ 4same name
- jholhewres/devclaw-skills★ 4same name
- promptmetrics/hubspot-claude★ 4same name
- Shanksg/clawskills★ 2same name
- G-HunterAi/openclaw-skills★ 0same name
- oivanfelipe/claude-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- business-dataSkill
- crm-insightsSkill
- crm-manageSkill
- ecommerce-insightsSkill
- ecommerce-manageSkill
- facebook-adsSkill
- facebook-organicSkill
- finance-insightsSkill
- gohighlevelSkill
- google-adsSkill
- google-analytics-4Skill
- google-business-profileSkill
- google-merchant-centerSkill
- google-search-consoleSkill
- instagram-publicSkill
- instagramSkill
- klaviyoSkill
- linkedin-adsSkill
- linkedin-pagesSkill
- microsoft-adsSkill
- social-media-createSkill
- social-media-insightsSkill
- tiktok-adsSkill
- tiktok-organicSkill
- web-analytics-insightsSkill
- windsor-connectSkill
- windsor-createSkill
- windsor-exportSkill
- windsor-get-startedSkill
- windsor-insightsSkill
- windsor-manageSkill
- windsor-optimizeSkill
- youtubeSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Call get_connectors to see which HubSpot accounts are connected (each has an id and, usually, a name).
- Distinctive: line 28
If the user names an account, match it to a connected account id.
- Very specific: line 33
Call get_fields for hubspot to get valid field ids — contacts, companies, deals, deal stage, pipeline, deal amount/value, close date, …
- Very specific: line 37
If the analysis needs segmentation or attribution controls, call get_options to see the connector's options and valid values.
- Very specific: line 60
If a tool returns an error (unknown field/connector/account), call the relevant discovery tool (get_fields, get_connectors) and retry with …
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
HubSpot via Windsor.ai
Windsor.ai exposes live HubSpot CRM and marketing data (read only) through MCP
tools. The connector id is hubspot. Pass hubspot as the connector on every tool call; the Windsor.ai server
serves all connectors, so it is never implied.
Golden rules:
- Never guess field, account, or option names. They come from
get_fields,get_connectors, andget_options. Call those first; do not invent identifiers. - HubSpot is read-only here — there are no write actions. Do not offer to create, edit, or delete records, or to send emails.
- Report the numbers the user asked for, concisely. Don't dump raw rows unless asked.
1. Ground yourself first
Call get_connectors to see which HubSpot accounts are connected (each has an id
and, usually, a name). If none are connected, help the user connect one: call
get_connector_authorization_url (or get_connector_connect_info for the auth
type and steps) and give them the setup link — do not describe manual dashboard
navigation.
If the user names an account, match it to a connected account id. If several are connected and the request is ambiguous, ask which account.
2. Reading CRM and marketing data
- Call
get_fieldsforhubspotto get valid field ids — contacts, companies, deals, deal stage, pipeline, deal amount/value, close date, owner, lead source, and marketing metrics (email opens, clicks, conversions, revenue). Use the exact ids returned, not these examples. - If the analysis needs segmentation or attribution controls, call
get_optionsto see the connector's options and valid values. - Call
get_datawith:fields: the ids you actually need (keep the set small).accounts: the target account id(s); omit for all connected accounts.- A date range:
date_from/date_to("2026-07-01"), or adate_preset(last_7d,last_30d,last_90d,this_month,this_year,last_year; appendTto include today). options/filtersonly if relevant, e.g.[["deal_stage","eq","closedwon"]].
Common requests → recipe:
- Pipeline value: fields
deal_stage+ deal amount; aggregate by stage. - Win analysis: filter to closed-won deals, group by
lead_sourceor owner. - Marketing performance: email/campaign fields (sends, opens, clicks, conversions) over a preset range; compute open and click rates.
Watch out: money fields are in the account currency (state it if known). If a
field the user wants isn't in get_fields, say so rather than substituting a
different metric.
3. Reference the user's data, don't fabricate
If a tool returns an error (unknown field/connector/account), call the relevant
discovery tool (get_fields, get_connectors) and retry with correct ids. Never
fill gaps with made-up numbers, deal names, or contacts.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

