Agent skill
gtm-expand
Fourth stage of the GTM funnel.
Filed under CRM and RevOps.
From ToolMonsters/claude-gtm-skills · 4 skills · 2 · pushed 2026-06-23
What it does when it runs
Fourth stage of the GTM funnel. Pulls an account's history and usage from HubSpot and turns it into a QBR deck via Gamma that proves the value delivered and sets up the upsell. Trigger phrases include "expand", "build a QBR deck", "account review for upsell", and "/gtm-expand".
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/ToolMonsters/claude-gtm-skills.git /tmp/claude-gtm-skills git -C /tmp/claude-gtm-skills sparse-checkout set "skills/gtm-expand" mkdir -p ~/.claude/skills/gtm-expand cp -R "/tmp/claude-gtm-skills/skills/gtm-expand/." ~/.claude/skills/gtm-expand/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from ToolMonsters/claude-gtm-skills/blob/0f86baa3a7f5f7d45b93c41d4616d448d9f99d89/skills/gtm-expand/SKILL.md, which is licensed MIT (repository). 428 words, 10 headings.
GTM Expand (HubSpot + Gamma)
Overview
HubSpot pulls the account's history and usage. Gamma turns it into a QBR deck that proves the value delivered and sets up the upsell. The output is a business-review deck for an existing customer, built to justify renewal and open the next deal.
This is funnel stage 4 of 4. The others are gtm-find-and-reach, gtm-meet, gtm-close.
Inputs
| Input | Required | Notes |
|---|---|---|
account | yes | The customer to review. Accepts a company name or HubSpot company/deal ID |
period | no | Review window. Default: last quarter |
Workflow
Step 1: Resolve the account
Use HubSpot search_crm_objects to find the company by name, or use the ID directly. If more than one company matches, show the candidates and let the user pick. Never review the wrong account on a name collision.
Step 2: Pull the account history (HubSpot)
Use query_crm_data / get_crm_objects to gather, scoped to period:
- Closed and open deals (values, stages, dates)
- Engagement and activity history
- Product or usage signals available on the company/contact properties
- Support tickets or notes if present
Call get_properties first if you are unsure which fields hold usage data. Read only what the QBR needs.
Step 3: Synthesize value and upsell
From the data, build:
- Value delivered: outcomes, milestones, and usage growth over the period, with numbers
- Health signals: adoption, engagement, any risks
- The upsell thesis: the specific next product, tier, or seat expansion that the usage data justifies
Ground every claim in HubSpot data. If a number is not in the CRM, do not assert it.
Step 4: Build the QBR deck with Gamma
Call Gamma generate for a QBR deck (default 8-10 slides):
- Account snapshot and period
- Goals set at the start
- Value delivered (metrics, outcomes)
- Usage and adoption trend
- Wins and milestones
- Health and risks, handled honestly
- The upsell, framed as the next outcome
- Proposed next steps and timeline
Content rules: direct statements, no em-dashes, no "no X, no Y" phrasing.
Step 5: Hand off
Return the deck link plus a 2-3 sentence framing message for the QBR invite. Note the deck is editable in the Gamma editor.
Constraints
- Every metric in the deck must trace to HubSpot data. Flag gaps rather than filling them.
- Confirm the account on any name collision before pulling data.
- Keep risks in the deck honest; a QBR that hides problems loses the renewal.
Need help setting it up?
This page tells you what gtm-expand does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.