pipeline-pulse

Quick book-of-business snapshot for a HubSpot Solutions Partner — total clients, total MRR, which clients need attention (churn signals, declining usage, near-term renewals, renewal dates to verify, managed relationships about to lapse) and which carry an ML-detected revenue signal. The fast entry point: it gives the overview, then points you to the specialised partner skills for the deep work. Read-only: never creates or edits records or deals, and never contacts anyone. ALWAYS use this skill for any portfolio-level request — "how's my book of business", "show me my clients", "client overview", "portfolio summary", "book of business", "client snapshot", "which clients need attention", "how's my portfolio doing", "partner overview", "review my clients" — and for "tell me about [client]". This skill is a lightweight pulse only — it hands off to the other skills for detail.

Read-only expansion reporting for a HubSpot Solutions Partner: surface which of the partner's clients are worth an upsell or cross-sell — including clients maxed out on seats, credits, or contacts, sitting on unactivated tools, or simply thriving with room to grow — ranked by value, plus (on request) the reasoning for a fit and suggested outreach copy. Use for viewing, prioritizing, or drilling into a partner's expansion, upsell, or cross-sell opportunities — e.g. "which clients can I sell more to", "who's maxed out on seats", "best Sales Hub opportunities", or "which clients should I approach about AI agents, and why". Do not use for creating or editing deals, updating records, or sending outreach or contacting customers — it drafts copy but only reads and reports. The deep-dive companion to book-pulse.

Read-only renewal reporting for a HubSpot Solutions Partner: surface which of the partner's clients have HubSpot subscription renewals coming up, ranked by urgency, with per-Hub renewal dates and the Contract Manager to coordinate with. Also flags renewal dates in the past that need verifying. Use for viewing, prioritizing, or drilling into upcoming or per-Hub client renewals — e.g. "walk me through my upcoming renewals", "who's renewing in the next 90 days", or "renewal dates for [client]". Do not use for creating or editing renewal deals, updating records, or contacting Contract Managers or customers — those are write workflows, and this skill only reads and reports. The deep-dive renewals companion to book-pulse.

Prepares a focused brief before a sales call or meeting. Pulls CRM history, open deals, recent notes, email threads, and company news. Falls back to calendar and email if the contact isn't in HubSpot yet. ALWAYS use this skill before a call or meeting — "prep me for my call with X", "I have a meeting with [company]", "brief me on [name]", "what do I know about X before my call", "research X", "who am I meeting with today", "prepping for X", or just a name paired with "call" or "meeting". Trigger proactively when the user seems about to get on a call and hasn't run prep.

Pulls a full view of a contact from HubSpot — deal status, lifecycle stage, last interaction, notes, tasks, and associated company. Returns a clean summary in chat. ALWAYS use this skill when the user asks about a specific person by name — "pull up X", "show me X's record", "what's happening with X", "check X", "who is X", "tell me about X", "what's X's status", "when did we last contact X", "look up X". Also trigger when the user pastes a contact email address wanting context on that person.

Generates a prioritised daily brief from HubSpot data plus any connected apps (calendar, email, Slack, meeting notes). Shows today's meetings, surfaces GTM tasks with effort-aware scheduling, deduplicates suggestions against existing HubSpot tasks, and outputs as readable markdown. ALWAYS use this skill when the user wants their day laid out — "good morning", "daily brief", "morning brief", "what do I need to do today", "what's on my plate", "what should I focus on", "catch me up", "today's priorities", "what's urgent", "what's due today", "show me my day", or any morning planning request. Trigger proactively when a user opens Claude first thing with no specific ask.

Drafts a personalised follow-up or outreach email for a named contact, grounded in HubSpot deal context, recent notes, and email history. Opens HubSpot with the email pre-populated so the rep can review and send with full tracking. If deal-related, updates the next step or deal stage as applicable. ALWAYS use this skill when the user wants to write or send outbound communication to a specific contact — "follow up with X", "draft an email to X", "send something to X", "check in with X", "reach out to X", "ping X", "touch base with X", "I need to reply to X", "draft a follow-up for [deal]", "write to X". Trigger on any request to compose outbound communication tied to a contact or deal.

Main HubSpot assistant and entry point for all CRM tasks. Handles direct lookups, stats, quick field updates, and how-to questions — and routes to specialized skills (call-prep, daily-brief, follow-up, log-call, pipeline-pulse, import-contacts) when a specific workflow is needed. ALWAYS use this skill as the primary entry point for any HubSpot-related request — "show me [contact]", "open deals", "pipeline value", "create a task", "update [deal]", "how many contacts", "what can you do", or anything touching contacts, companies, deals, or tasks. Even when another skill might match, use this one — it routes appropriately. Trigger on "/hubspot", "hey HubSpot", or any CRM question without a more specific skill clearly in scope.

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