OpenParable
Skip to content
← Back to skills

In App Messaging Kit

Design
in-app-messaging-kit

In App Messaging Kit is an Agent Skill for design published in the gtmagents/gtm-agents repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/gtmagents/gtm-agents/blob/HEAD/plugins/product-led-growth/skills/in-app-messaging-kit/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/in-app-messaging-kit, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.