Skip to content
Agentmart
Submit a tool

gtm-customer-success

Create a customer success plan that links adoption to an agreed customer outcome.

Skill by teopaleface

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/teopaleface-gtm-customer-success

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Create a customer success plan that links adoption to an agreed customer outcome.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/gtm-customer-success

What's inside

Skill name
gtm-customer-success
Description
Create a customer success plan that links adoption to an agreed customer outcome.
License
MIT
Instructions
19 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • openai.yaml · agents/

SKILL.md (first lines)

# Customer success

Start from the customer's desired outcome and the evidence that shows progress.

## Steps

1. Define the customer outcome, stakeholders, timeline, current adoption, and success criteria.
2. Map milestones, risks, dependencies, enablement, and the next value event.
3. Separate measured progress from account assumptions and public signals.
4. Create a review cadence and escalation path for adoption or value gaps.
5. Identify an expansion hypothesis only after the core outcome is credible.

Use `../../references/evidence-policy.md`, `../../references/ticket-schema.md`, and `../../references/artifact-contract.md`.

## Completion

The plan has an agreed outcome, observable milestones, an owner, a review path, and a respectful expansion boundary.

From teopaleface/gtm-os, MIT.

More from teopaleface/gtm-os

Signals

Stars
0
Forks
0
Open issues
1
Last commit (this folder)
Aug 27, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from teopaleface

Cite this page

gtm-customer-success skill. Agent Mart. https://agentmart.dev/skills/teopaleface-gtm-customer-success (last updated 2026-10-24)