reprise-mcp

Reprise MCP — Router

You've landed here because the user wants to do Reprise work. This skill carries no workflow content — its only job is to identify the right surface and hand off to the surface-specific skill. Don't try to do the work yourself from this skill; route correctly and the right skill will load with everything you need.

Step 1 — Confirm Reprise context

You're in scope if:

• The user mentions Reprise, a Reprise preview URL, a Reprise demo, a clone / tour, or any Reprise MCP tool.
• The Reprise MCP is connected and its tools (clone_*, tour_*, injection_*, docs, search_patterns, session_recap, report_friction) are available.

If neither is true, this skill shouldn't have fired — answer the user's actual question without routing.

Step 2 — Identify the surface from cues

Surface	The user is asking for	Cues
Clone	Fix / debug / configure a captured interactive app	clone_id, snippet, clone_api, replay_backend, any clone_* MCP tool, /sw-setup/ URL, "captured app", "the demo white-screens / goes blank / breaks after login", service-worker issues, snippet editing
Product Tour, NEW capture	Record a new tour by capturing screens	tour_capture, pairing_token, deep_link_url, capture_now, a brand-new draft_id, "Reprise Builder HTML extension", "record a tour", "build a tour of X", "capture screens"
Product Tour, EDITING existing	Modify an existing tour (text, attributes, images, guides, translation, re-skin)	tour_edit, tour_screen(action='copy_to'), tour_guide, tour_variable, tour_link, set_custom, "edit this tour", "translate to X", "re-skin for prospect Y", "rebrand the tour", "add a guide / variable"
Product Tour, ID confusion	Resolve a paste of a /launch/<slug>/ URL or a wrong_id_kind error	draft_id, published_id, PublishedReplayLink, /launch/<slug>/, wrong_id_kind, tour_not_found, "what's the draft for this published tour", "I have a launch URL"
Data Injection	Populate charts / tables / dropdowns with custom data by swapping API responses	any injection_* MCP tool, dataset_id, Dataset → Source → Value, "Data Studio", "populate the chart", "fake data on this page", "swap the API response", "inject data into the live app" (primary case)

If exactly one surface matches, go to Step 4.

Step 3 — Ask if ambiguous

If the prompt doesn't clearly indicate which surface (common with vague phrasings like "fix my Reprise demo," "build me a demo for [prospect]," "the page is broken"), ask one clarifying question:

Are you working on:

• Clone — an interactive captured app you're configuring or debugging?
• Product Tour — a linear walkthrough from captured screens? (And: building new, or editing existing?)
• Data Injection — swapping API responses on a live app to populate charts / tables?

Don't guess; don't proceed without the answer. A wrong surface guess wastes far more time than one clarifying turn.

Step 4 — Invoke the surface skill

Call the right skill explicitly. Do this BEFORE any other tool call:

• Clone → Skill(skill="reprise:reprise-clone-config")
• Tour, new capture → Skill(skill="reprise:reprise-tour-capture")
• Tour, editing existing → Skill(skill="reprise:reprise-tour-edit")
• Tour ID confusion → Skill(skill="reprise:reprise-tour-id-model")
• Data Injection → Skill(skill="reprise:reprise-injection")

For Product Tour, the verb is the signal: "build / record / capture / make a tour" → reprise-tour-capture; "edit / translate / re-skin / change / fix / add a guide / rebrand" → reprise-tour-edit. The ID-model skill is a focused side-load when you hit an ID error or a launch-URL paste.

Step 5 — At end of session

Regardless of which surface skill ran, when the user signals end-of-session ("we're good", "that's it", "thanks", topic switch) or when you've completed the task and are composing a final summary, invoke:

Skill(skill="reprise:reprise-session-close")

That skill carries the session_recap and report_friction call shapes.

What this skill is NOT

• It's not a workflow skill. Don't enumerate phases from here.
• It's not the place for gotchas, forcing functions, or method references — those live in the surface skills' bodies and in docs(slug='...').
• It's not a fallback if you forgot which skill to invoke — pick one consciously.