Skip to content

■ SKILLS // SKILL SPECS

product-led-growth

Self-serve onboarding, PQL routing, and in-app experiment governance

■ [!] ON THIS PAGE ▼
■ INSTALL // npx @self.md/cli install product-led-growth
AuthorGTM Agents
Namespace@gtmagents/gtm-agents
Category#business
Version1.0.0
Stars★ 64
Downloads↓ 3
Verification[ ✓ ] self.md verified

Self-serve onboarding, PQL routing, and in-app experiment governance

Installation

npx claude-plugins install @gtmagents/gtm-agents/product-led-growth

Contents

Folders: agents, commands, skills

Included Skills

This plugin includes 4 skill definitions:

in-app-messaging-kit

Library of in-product message patterns, triggers, and targeting rules.

View skill definition

In-App Messaging Kit Skill

When to Use

  • Designing nudges, tooltips, and walkthroughs for onboarding or feature launches.
  • Coordinating lifecycle messaging across in-app surfaces, chat, and email.
  • Testing personalization ideas tied to usage milestones or cohorts.

Framework

  1. Trigger Matrix – event-based, state-based, and contextual triggers.
  2. Message Patterns – tooltip, modal, checklist, banner, coachmark, chat prompt.
  3. Targeting Rules – persona, plan/tier, usage depth, lifecycle stage.
  4. Measurement Plan – success metrics (CTR, completion, conversion) and guardrails.
  5. Localization + Accessibility – copy guidelines, fallback flows, and escalation options.

Templates

  • Message brief (goal, trigger, variant, CTA, measurement).
  • Component library reference with best practices.
  • Experiment tracker linking messages to outcomes.

Tips

  • Keep copy concise; pair visuals or GIFs where possible.
  • Schedule “quiet hours” to avoid notification overload.
  • Tie each message to a single next-best-action to reduce decision fatigue.

onboarding-blueprint

Template for designing onboarding journeys, milestones, and measurement

View skill definition

Onboarding Blueprint Skill

When to Use

  • Creating persona-based onboarding for new tiers or product lines.
  • Refreshing onboarding journeys after major product changes.
  • Aligning product, CS, and marketing on activation milestones.

Framework

  1. Persona Canvas – goals, motivations, blockers, success definition.
  2. Milestone Ladder – aha moment, activation, stickiness, expansion triggers.
  3. Channel Mix – in-app, email, docs, community, human assist with triggers.
  4. Instrumentation – required events, metrics, and guardrails.
  5. Experiment Hooks – backlog of tests tied to each milestone.

Templates

  • Journey table (step, trigger, message, owner, metric).
  • Metric dashboard layout for activation + retention.
  • Experiment backlog sheet linked to milestones.

Tips

  • Keep journeys lightweight; aim for 3-5 key milestones per persona.
  • Combine qualitative inputs (surveys, interviews) with telemetry for context.
  • Pair with design-onboarding-journey to auto-generate tailored blueprints.

pql-framework

Methodology for defining product-qualified lead (PQL) signals, scoring,

View skill definition

PQL Framework Skill

When to Use

  • Standing up or recalibrating PQL/PQA programs.
  • Aligning product, growth, and sales on what constitutes a high-intent product user.
  • Auditing the health of existing PQL scoring + routing logic.

Framework

  1. Signal Library – catalog feature usage, plan limits, collaboration signals, intent, firmographics.
  2. Scoring Model – weight signals, set decay rules, and define negative indicators.
  3. Tiering – map PQL tiers (A/B/C) to follow-up motions and SLAs.
  4. Routing Rules – specify owners, cues, channels (CRM tasks, Slack alerts, CS queue).
  5. Measurement Loop – track conversion, ARR impact, and feedback for model tuning.

Templates

  • Signal inventory worksheet with data source + freshness.
  • Scoring matrix with weights, thresholds, and decay logic.
  • Routing decision tree linking tiers to plays.

Tips

  • Start with simple tiering, iterate once telemetry + feedback improve.
  • Include “disqualifier” signals (expired trials, churn risk) to avoid noise.
  • Pair with operationalize-pql-routing to push models into automation.

usage-health-scorecard

Framework for monitoring activation, engagement, and monetization guardrails.

View skill definition

Usage Health Scorecard Skill

When to Use

  • Tracking activation/retention metrics for self-serve and hybrid customer cohorts.
  • Monitoring the impact of PLG experiments on core product health.
  • Sharing health snapshots with product, growth, and CS leads.

Framework

  1. Metric Groups – activation, engagement, collaboration, monetization, support load.
  2. Segmentation – persona, plan, cohort, region, product area.
  3. Thresholds – traffic light ranges for each metric with warning/critical bands.
  4. Alerting – notification rules for drops, anomalies, or experiment impacts.
  5. Action Registry – log remediation steps, owners, due dates, and results.

Templates

  • Scorecard layout (metric, current, target, delta, owner).
  • Dashboard wireframe with spark lines + annotations.
  • Action tracker for follow-up tasks linked to health changes.

Tips

  • Pair with launch-in-app-experiments to watch guardrails post-launch.
  • Include qualitative signals (support tags, NPS) to contextualize telemetry.
  • Archive snapshots to tell longitudinal stories in QBRs.

Source

View on GitHub