CtrlK
BlogDocsLog inGet started
Tessl Logo

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 key product capabilities, or when an in-product help system is being scoped for the first time.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable playbook that uses progressive disclosure effectively and offers a clear sequenced framework. The main weakness is redundancy: the keystone three-pattern framing is repeated across the intro, body, and closing.

Suggestions

Collapse the restatement of the tooltip-spam / one-and-done / contextual-when-needed framing in the intro and closing so it lives fully in its dedicated section, cutting ~15-20 lines of repetition.

Trim the opening 'A senior product marketing director's playbook...' paragraph, which re-covers scope already stated in the frontmatter description.

Consider merging the standalone 'Common failure modes' rapid-fire list into the relevant pattern sections to reduce a separate diagnostic block that overlaps the failure-reference file.

DimensionReasoningScore

Conciseness

The opinionated playbook is mostly efficient, but the tooltip-spam/one-and-done/contextual-when-needed framing is restated in the intro, a dedicated section, and the closing, and the intro re-covers ground already in the description — it could be tightened.

2 / 3

Actionability

For an instruction-only skill it gives concrete, specific guidance: named trigger types with 'When to use' rules, earn-vs-document decision criteria, per-state re-trigger rules, and a 12-consideration framework, satisfying the actionable-guidance note.

3 / 3

Workflow Clarity

The 12-consideration framework is a clearly sequenced walkthrough of the design/audit process; the destructive/batch-operation validation cap does not apply to this advisory skill.

3 / 3

Progressive Disclosure

A clear overview with nine well-signaled one-level-deep references ('Detail in references/...'), each verified to exist, plus a consolidated Reference files index — content is appropriately split with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete capability areas, provides explicit trigger terms, and clearly answers both what and when. It is concise for the depth it conveys and well-distinguished from neighboring growth-tooling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'Trigger logic, tour architecture, contextual placement, completion tracking' — matching the anchor for multiple specific concrete actions rather than vague language.

3 / 3

Completeness

Explicitly answers what ('Designing in-product tours, tooltips, and contextual help...') and when ('Triggers on...', 'Also triggers when feature adoption is low...'), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

'Triggers on product tour, in-product tooltip, contextual help, walkthrough, feature tour, hint system, in-app guidance, tour platform' gives broad coverage of natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Tour-specific triggers and an explicit niche (in-product contextual help) make it unlikely to fire for sibling skills like onboarding-wizard-design or chatbot-flow-design.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.