# In app messaging kit Human Guide

## What This Is For
When to Use Designing nudges, tooltips, and walkthroughs for onboarding or feature launches. It gives the agent a clearer input/output frame for in app messaging kit: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the In app messaging kit agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for in app messaging kit.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the In app messaging kit guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- 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.
- **Trigger Matrix** – event-based, state-based, and contextual triggers.
- **Message Patterns** – tooltip, modal, checklist, banner, coachmark, chat prompt.
- **Targeting Rules** – persona, plan/tier, usage depth, lifecycle stage.
- **Measurement Plan** – success metrics (CTR, completion, conversion) and guardrails.
- **Localization + Accessibility** – copy guidelines, fallback flows, and escalation options.
- Message brief (goal, trigger, variant, CTA, measurement).
- Component library reference with best practices.
- Experiment tracker linking messages to outcomes.
- Keep copy concise; pair visuals or GIFs where possible.

## Decision Points And Nuance
The original skill emphasizes: When to Use, Framework, Templates, Tips.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Schedule “quiet hours” to avoid notification overload.

## Copy-And-Paste Prompt
```text
Use the In app messaging kit human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the gtmagents/gtm-agents skill entry for `in-app-messaging-kit`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# 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.

---