Systems Lab

Agent skill

gtm-close

Third stage of the GTM funnel.

slowingSelf-containedInstructions only460 words

Filed under Prospecting and list building.

From ToolMonsters/claude-gtm-skills · 4 skills · 2 · pushed 2026-06-23

What it does when it runs

Third stage of the GTM funnel. Turns a winning Gamma deck into a sales page with a Stripe checkout button baked in, so the prospect reads the pitch and pays on the same link. Trigger phrases include "close", "turn the deck into a sales page", "add Stripe checkout to my deck", and "/gtm-close".

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-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about gtm-close

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
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-close"
mkdir -p ~/.claude/skills/gtm-close
cp -R "/tmp/claude-gtm-skills/skills/gtm-close/." ~/.claude/skills/gtm-close/

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.

Reproduced in full from ToolMonsters/claude-gtm-skills/blob/0f86baa3a7f5f7d45b93c41d4616d448d9f99d89/skills/gtm-close/SKILL.md, which is licensed MIT (repository). 460 words, 10 headings.

GTM Close (Gamma + Stripe)

Overview

Gamma turns the winning deck into a sales page with Stripe checkout baked in. The prospect reads the pitch and pays on the same link, no separate quote or invoice step.

This is funnel stage 3 of 4. The others are gtm-find-and-reach, gtm-meet, gtm-expand.

Stripe note (read first)

There is no Stripe connector in this session, so checkout is wired with a Stripe Payment Link, not a live API call. The user creates the Payment Link once in the Stripe dashboard (Products → Payment Links), and this skill embeds it as the buy button on the page. If a Stripe MCP connector is later added, prefer generating the link programmatically.

Inputs

InputRequiredNotes
deckyesThe winning Gamma deck. Accepts a Gamma file ID or pasted deck content
payment_linkyesA Stripe Payment Link URL for the offer
pricenoHeadline price to show on the page. Pull from the Payment Link context if not given

Workflow

Step 1: Read the winning deck

If deck is a Gamma file ID, call read_gamma to pull its content. If it is pasted content, use that. Identify the core pitch: the prospect's problem, the offer, the proof, and the price.

Step 2: Confirm the Stripe Payment Link

Ask for the Stripe Payment Link if not provided. Validate it is a real Stripe URL (buy.stripe.com or a custom Stripe domain). Do not invent a link and do not proceed to publish without one. Confirm the price shown on the page matches the Payment Link amount.

Step 3: Build the sales page with Gamma

Call Gamma generate with a webpage format. Reshape the deck into a one-page sell:

  1. Headline outcome (what they get)
  2. The problem, named
  3. The offer and what is included
  4. Proof (case study, metric, or testimonial)
  5. Price + the Stripe checkout button using payment_link
  6. A short FAQ / risk reversal
  7. A second checkout button at the bottom

The Stripe Payment Link must be the primary call to action, placed as a clear buy button.

Content rules: direct statements, no em-dashes, no "no X, no Y" phrasing.

Step 4: Hand off

Return the published page link. Tell the user to test the checkout button once before sending, and that the page is editable in the Gamma editor.

Constraints

  • Never publish a checkout page without a validated Stripe Payment Link.
  • The price on the page must match the Payment Link. Flag any mismatch instead of guessing.
  • This skill cannot process payments or read Stripe data; it only embeds the provided link.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what gtm-close 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.