Systems Lab

Agent skill

customer-marketing

When the user wants a PMM-led post-sale motion for onboarding, adoption, value realization, retention, cancellation-reason synthesis, win-back, expansion, advocacy, references, case studies, champion development, or customer launches.

activeSelf-containedInstructions only494 words

Filed under Onboarding, retention and expansion.

From mia-ppp/PMM-Skills · 45 skill entries · 71 · pushed 2026-10-16

What it does when it runs

When the user wants a PMM-led post-sale motion for onboarding, adoption, value realization, retention, cancellation-reason synthesis, win-back, expansion, advocacy, references, case studies, champion development, or customer launches. For billing operations, route to the billing/CS owner; for customer research, see customer-research.

Automated analysis of the skill and the 5 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 customer-marketing

Opens your assistant with this page's recorded context. Check the linked sources before relying on it.

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/mia-ppp/PMM-Skills.git /tmp/PMM-Skills
git -C /tmp/PMM-Skills sparse-checkout set "skills/customer-marketing"
mkdir -p ~/.claude/skills/customer-marketing
cp -R "/tmp/PMM-Skills/skills/customer-marketing/." ~/.claude/skills/customer-marketing/

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 mia-ppp/PMM-Skills/blob/5281aa6e55ca12d2ad5f97c3bf45e8cf49488225/skills/customer-marketing/SKILL.md, which is licensed MIT (repository). 494 words, 8 headings.

Customer Marketing

Orchestrate customer-facing PMM programs across onboarding, adoption, value realization, expansion, and advocacy. This skill owns the objective, audience, message brief, proof plan, coordination, and learning. It does not own Customer Success operations or final channel assets.

Activation and commercial boundaries

product-activation owns first-value definitions and experience briefs; this skill orchestrates post-sale cohort programs with Product/CS. upgrade-conversion owns in-product upgrade eligibility/timing and pricing-strategy owns commercial terms. Expansion campaigns consume those approved decisions.

Retention and win-back mode

Read retention briefs for cancellation-reason synthesis, cohort hypotheses, retained-value measurement and learning loops. Own value realization, respectful retention briefs and win-back triggers. Preserve easy cancellation and consent; never invent save offers, discounts or roadmap promises. Billing retries, payment-provider configuration and access management route to operational owners. PMM may brief truthful payment-recovery communication but does not run billing. Read customer review programs when reviews support advocacy; no coerced or fabricated reviews.

Before planning

Read ../_shared/evidence-gaps.md and ../_shared/ssot-consumption.md. Load the project manifest's relevant approved context and record sources used. Read ../_shared/segment-selection.md only when choosing audiences; inherit accepted segment decisions without redefining canonical ICP.

Workflow

Select the relevant customer role and lifecycle situation. The buyer and the user may differ; preserve that distinction in program and asset briefs.

  1. Choose one primary objective: adoption, retention support, expansion, advocacy, reference creation, or customer evidence collection.
  2. Define eligible customer cohort using evidence such as lifecycle, product usage, account tier, persona, use case, or documented opportunity. Do not infer satisfaction, readiness, or expansion potential.
  3. Identify customer need, desired action, barriers, owner, consent, timing, and appropriate CS/Sales coordination. Keep any unsupported rationale labeled.
  4. Build the canonical message brief and select approved proof. Case study and outcome claims require customer permission and source verification.
  5. Route email to email-sequence, community coordination to community-marketing, reference materials or customer-facing sales proof to sales-enablement, and other assets to their channel owner.
  6. Define cohort-level leading indicators and outcomes with source, owner, and window. Record learning and evidence for reuse.

Required output

Inputs and assumptions; objective and cohort; eligibility/evidence; customer value and intended action; message/proof brief; cross-functional roles; asset handoffs; measurement; consent/readiness gaps; and ranked evidence gaps. Output quality: output-quality-check can verify objective/cohort fit, evidence labels, readiness safety, proof/consent gaps, clear owners, measures, and explicit handoffs.

Boundaries and feedback

  • Retention programs belong here; billing operations, payment retries, provider configuration and access management belong to external billing/CS operations.
  • community-marketing owns community design, member engagement, and community advocate programs. This skill may define a customer-community objective and hand it off.
  • customer-research owns research design and evidence synthesis, including the reusable VoC language bank. Route collected quotes/feedback there.
  • revops owns lifecycle definitions, CRM automation, routing, and revenue process. analytics-tracking owns instrumentation.
  • Route any proposed canon change through ssot-context-loop; do not edit SSOT. Customer campaigns and case studies are market-facing and should pass messaging-consistency-audit after output-quality-check.

Related skills

community-marketing, customer-research, email-sequence, sales-enablement, revops, analytics-tracking, messaging-consistency-audit, ssot-context-loop, output-quality-check.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

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 customer-marketing 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.

Build my GTM engine

Tell us what you want to improve. Fedor reviews the workflow and replies by email when there is a useful fit.

Fedor reviews every request personally. If there is a useful fit, he will reply by email.