Agent skill

interactive-product-tour

Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss k

RampStack477★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add rampstackco/claude-skills --skill interactive-product-tour --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 10
SKILL.md size: 17 KB
Bundled scripts: none
Path: skills/interactive-product-tour/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Interactive Product Tour A senior product marketing director's playbook for designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. The discipline of building help systems that surface at moments of need and disappear when not needed. Most product tours fail in one of two ways. They paint every button, link, and feature with "click for tour" hints until the visual noise is so great that users develop blindness to the dots. Or they show a single first-login tour the user skips or skims, after which the same help never re-surfaces when the user actually hits a moment of friction. Help that is invisible at the moment of need is help that does not exist. The tours that work do something different. They trigger when the user is at a moment of friction, not all the time. They surface contextual hints when the user enters a section they have not explored, clicks into a feature requiring setup, or returns after a long absence. The system knows what the user knows and surfaces help at the right moment. The voice is the senior product marketing director

What's inside
Steps it walks through
  1. What this skill covers
  2. The tour decision: when tours earn vs when documentation suffices
  3. Tooltip-spam vs one-and-done vs contextual-when-needed
  4. Trigger logic: event-based vs time-based vs state-based
  5. Tour architecture: single tour vs branched vs library of micro-tours
  6. Contextual placement: where help appears, how it dismisses
  7. Completion tracking and re-trigger logic
  8. Power-user vs new-user differentiation
  9. Common failure modes
  10. The framework: 12 considerations for product tour design
  11. Reference files
  12. Closing: tours earn the user's attention by being absent until needed
Ships with 9 files
  • references/common-tour-failures.md
  • references/completion-tracking-and-re-trigger.md
  • references/contextual-placement-patterns.md
  • references/dismissal-and-non-intrusion-patterns.md
  • references/power-user-vs-new-user-patterns.md
  • references/tour-anti-patterns.md
  • references/tour-architecture-patterns.md
  • references/tour-decision-criteria.md
  • references/trigger-logic-patterns.md
More from claude-skills
All skills →
About this skill
What does the interactive-product-tour skill do?

Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of need), and contextual-when-needed (surfaces help at the moment friction occurs) patterns. Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform. Also triggers when feature adoption is low, when users miss k

How do I install it?

Run `npx skills add rampstackco/claude-skills --skill interactive-product-tour --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going