agentleFS
windsor-aiwindsor-ai/claude-windsor-ai-plugin/skills/hubspot/SKILL.md

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

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.
  • OpenAISkill

    posthog

    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

  • jiulingyunSkill

    discord

    Discord ops via the message tool (channel=discord).

    Also in 3 projects that use this

  • MicrosoftSkill

    jira

    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

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
  1. Very specific:

    Call get_connectors to see which HubSpot accounts are connected (each has an id and, usually, a name).

    line 22
  2. Distinctive:

    If the user names an account, match it to a connected account id.

    line 28
  3. Very specific:

    Call get_fields for hubspot to get valid field ids — contacts, companies, deals, deal stage, pipeline, deal amount/value, close date, …

    line 33
  4. Very specific:

    If the analysis needs segmentation or attribution controls, call get_options to see the connector's options and valid values.

    line 37
  5. Very specific:

    If a tool returns an error (unknown field/connector/account), call the relevant discovery tool (get_fields, get_connectors) and retry with …

    line 60

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, and get_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

  1. Call get_fields for hubspot to 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.
  2. If the analysis needs segmentation or attribution controls, call get_options to see the connector's options and valid values.
  3. Call get_data with:
    • 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 a date_preset (last_7d, last_30d, last_90d, this_month, this_year, last_year; append T to include today).
    • options / filters only 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_source or 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.