gohighlevel
Skill from windsor-ai/claude-windsor-ai-plugin
Install
npx skills add windsor-ai/claude-windsor-ai-plugin --skill gohighlevel
Runs the open skills CLI and installs the skill for your agent (Claude Code, Codex, Cursor …). Alternatively copy the skill folder into .claude/skills/ or upload it in Claude.ai under Settings → Skills.
As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-official
/plugin install windsor-ai@windsor-ai
This skill is part of the plugin “windsor-ai”. In Claude Code the plugin installs it together with the plugin’s other skills, commands and hooks.
What does the gohighlevel skill do?
Description from the SKILL.md in the source repository.
Questions about gohighlevel
What does the gohighlevel skill do?
Analyze GoHighLevel CRM data through Windsor.ai. Use when the user asks about their GoHighLevel account — contacts, opportunities and pipeline stages, deal value, appointments, campaigns, lead sources, or conversion rates. It can also create or update a contact and create an invoice, always after the user confirms the exact change. It does not send emails or SMS, book or change appointments, or modify pipeline or campaign settings. Do not use for other CRMs (HubSpot, Salesforce), outbound messaging, or ad-platform performance data.
How do I install gohighlevel?
In a terminal: npx skills add windsor-ai/claude-windsor-ai-plugin --skill gohighlevel. The skills CLI asks which agents to install it for. In Claude.ai you can upload the skill folder as a ZIP under Settings → Skills.
Which agents can use gohighlevel?
Skills use the open SKILL.md format, which Claude Code, Claude.ai, the Claude API, OpenAI Codex, Cursor, Gemini CLI and other agents support.
Is gohighlevel safe to use?
Our automatic check found no risky patterns (piped shell scripts, hidden characters, secret access, prompt overrides). It is not a full audit – read the SKILL.md and any scripts before installing.
More skills from windsor-ai/claude-windsor-ai-plugin
Create new items on Instagram, Facebook Pages, TikTok, YouTube, LinkedIn Pages, and Google Business Profile through Windsor.ai - publish image, video, carousel, and story posts and comment on posts on Instagram; publish text and photo posts on Facebook Pages; publish text and image posts on LinkedIn Pages; create posts, reply to reviews, and update photos, hours, and open status on Google Business Profile. Use when the user wants to create, publish, or post something new. Collect inputs, show the full draft, create only after confirmation.
Report, rank, compare, and trend web analytics performance across Google Analytics 4 and Google Search Console through Windsor.ai. Use when the user asks about sessions, users, engagement rate, conversions, and revenue from GA4; clicks, impressions, CTR, and average position from Search Console. Do not use to change anything, to connect an account, or to schedule exports - route those to the sibling skills.
Analyze TikTok account (organic) performance through Windsor.ai. Use when the user asks about their TikTok personal or business account's organic insights — video views, likes, comments, shares, followers, profile views, or audience breakdowns by country, age, gender, or active hour. Do not use for TikTok Ads (those live in the TikTok Ads connector), other platforms, or publishing videos.
Analyze and manage TikTok Ads through Windsor.ai. Use when the user asks about their TikTok Ads performance — pulling live campaign, ad group, or ad metrics (spend, impressions, clicks, conversions, CPA, ROAS), comparing date ranges, or finding top or underperforming campaigns — or when they want to pause or enable a campaign, ad group, or ad, or change a campaign or ad group budget. Do not use for TikTok organic (that's the TikTok Organic connector — no ad or cost data there), or other ad platforms (Meta/Facebook, Google, LinkedIn, Microsoft Ads).
Report, rank, compare, and trend social media performance across Instagram, Facebook Pages, TikTok, YouTube, LinkedIn Pages, and Google Business Profile through Windsor.ai. Use when the user asks about reach, impressions, engagement (likes, comments, shares, saves), follower growth, video views, and watch time. Do not use to change anything, to connect an account, or to schedule exports - route those to the sibling skills.
Analyze LinkedIn company page (organic) performance through Windsor.ai. Use when the user asks about their LinkedIn page's organic insights — follower growth, impressions, reach, clicks, reactions, comments, shares, engagement rate, or visitor demographics by industry, job function, seniority, or company size. It can also publish a text or image post to the company page, always after the user approves the full draft. Do not use for LinkedIn Ads (those live in the LinkedIn Ads connector) or other platforms.
Analyze and manage LinkedIn Ads through Windsor.ai. Use when the user asks about their LinkedIn Ads performance — spend, impressions, clicks, CTR, CPC, conversions, or leads at campaign, campaign-group, or creative level, with member demographic breakdowns — or wants to pause/enable a campaign, campaign group, or creative, or change a campaign or campaign-group budget. Do not use for LinkedIn organic company-page data (that's the LinkedIn Organic connector), other ad platforms, or GA4/web analytics.
Connect, reconnect, or add accounts for any of the 350+ sources Windsor.ai supports - Google Ads, Meta Ads, TikTok Ads, LinkedIn Ads, Microsoft Ads, Amazon Ads, Instagram, Facebook Pages, LinkedIn Pages, YouTube, TikTok, Google Business Profile, GA4, Search Console, HubSpot, Salesforce, Pipedrive, GoHighLevel, Shopify, Amazon Seller Central, Klaviyo, Stripe, QuickBooks, Xero, BigQuery, Snowflake, Google Sheets, and more - and resolve which connected account a request means. Use when the user wants to connect or set up a source, asks what is connected or available, sees no data, or hits a permission or sign-in error. Do not use for analysis or changes.
Related skills in DevOps & Cloud
The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
Salesforce Commerce Cloud (SFCC / Demandware, SFRA storefront) source techniques: how to get a store's public data with no Business Manager or OCAPI access — the files and public storefront endpoints to read, and how to scan the remaining site pages. Use when the source platform is SFCC.
Runs the generated extract/import pipeline and records execution results. Use when setup and codegen are complete and the user has approved the execution plan.
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.