feat: add creating-product-tours skill#135
Conversation
Adds a docs-only skill that walks an agent through building an in-app product tour using PostHog feature flags for targeting and PostHog events for tracking. Surfaces in the mega-plugin alongside posthog-best-practices and quack. Generated-By: PostHog Code Task-Id: f1029b67-83d1-466e-a4fd-56f132ae88d8
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
|
@adboio what did I (aka my agent) miss here? |
edwinyjlim
left a comment
edwinyjlim
left a comment
There was a problem hiding this comment.
this is good on the context mill side
for the wizard, I'll need to create a Q&A interface to handle free text input. new feature!
i can work with @adboio to take this over the finish line
| import { useEffect, useState, useCallback } from "react"; | ||
| import posthog from "posthog-js"; |
There was a problem hiding this comment.
if we want to support more frameworks outside of react we can split skills out into variants in the config.yaml
| Ask the user these questions before writing any code: | ||
|
|
||
| 1. **Goal** — what should the user be able to do after completing this tour? (e.g., "create their first dashboard", "connect a data source") | ||
| 2. **Steps** — list each step: what element should it point to, what does it say, how does the user advance (click a button in the tooltip, or click the highlighted element itself)? | ||
| 3. **Audience** — who sees it? All users, new users only, users on a specific plan, users who haven't done something yet? | ||
| 4. **Trigger** — auto-show on page load, trigger from a button, or chain from another tour? | ||
| 5. **Show frequency** — once ever, once per session, or every time the user visits? | ||
| 6. **Tech stack** — React, Vue, vanilla JS? This determines component shape. |
There was a problem hiding this comment.
oooh we need to build Q&A UI on the wizard-side, we don't have handle free text user input yet
There was a problem hiding this comment.
Do you want to do that now or should I somehow update this skill so that it doesn't require that? idk how I'd do that since the tour itself needs a lot of this detail in order to be good
There was a problem hiding this comment.
yep I'm working on wizard PR now, will update when it's ready
3 participants
Summary
Adds a new
creating-product-toursskill that walks an agent through building an in-app product tour for the user's own application using PostHog feature flags for targeting and PostHog events for tracking (started / step viewed / completed / dismissed).The skill is shaped like other self-contained docs-only skills (
quack,posthog-best-practices) — a singleconfig.yamlplus adescription.mdthat drops in verbatim asSKILL.md. No external docs fetched. It ships in theposthog-allmega-plugin.How it was tested
pnpm run build— the generator picks up the new group and emitscreating-product-tours.zip(4.4 KB) with the rightSKILL.mdfrontmatter (name,description, metadata).pnpm test— all 42 tests still pass.bash scripts/scan-prompt-injection.sh dist/skills— passes; no prompt-injection patterns flagged in any of the 92 archives.SKILL.mdagainst the sourcedescription.mdand confirmed the frontmatter is correct.Notes
The build emits a
[WARN] No plugin mapping for group "creating-product-tours"line, which matches the behavior of the existingquackandposthog-best-practicestop-level groups. The skill still ends up in the mega-plugin. Happy to add a dedicated plugin entry tomarketplace.yamlif reviewers want a standaloneposthog-product-toursplugin instead.Created with PostHog Code