Workflow

1. 1Pull product context, GTM context, and brand voice via get_workspace_knowledge before any edit.
2. 2Load an existing brand/style Skill, if one exists, as the higher authority on tone.
3. 3Read current step content and confirm the entity tag via get_flow_document before editing.
4. 4Apply the edit with update_step_content. Re-read the flow after any structural change since step indices shift.
5. 5Show a before/after of the copy, not just a confirmation.

Workflow

1. 1Take the feature description or ticket as input and extract what changed.
2. 2Pull demo descriptions and flows via list_projects and get_project.
3. 3Scan each candidate demo's steps and screenshots via get_flow_document for mentions of the old version.
4. 4Flag exact step indices affected, not the whole demo.
5. 5Apply edits via update_step_content on confirmation and re-verify.

Workflow

1. 1Pull the full flow structure via get_flow_document.
2. 2Check for broken navigation, stale CTAs, inconsistent terminology, and orphaned buttons.
3. 3Compile findings into a short pass/fail list of flags, not a rewrite.
4. 4Offer to fix anything fixable via MCP directly; flag anything needing a manual capture.

Workflow

1. 1Pull the last 7 days via list_demo_analytics.
2. 2Sort by engaged sessions, then CTR, and take the top 5.
3. 3Pull views, visitors, engaged sessions, duration, CTA clicks, and CTR for each.
4. 4Format to a fixed template so the report reads the same every week.

Workflow

1. 1Take existing analytics output as input.
2. 2Identify the 2–3 numbers that matter most to a non-analyst leader.
3. 3Write exactly 3 bullets, each one sentence, each ending in a “so what.”
4. 4Offer the full breakdown separately rather than front-loading every metric.

Workflow

1. 1Confirm the comparison baseline: prior period, same period last year, or a saved number.
2. 2Pull current and baseline periods via list_demo_analytics.
3. 3Compute percent change for engaged sessions, CTR, and CTA clicks.
4. 4Flag only moves past a meaningful threshold as notable.

Workflow

1. 1Identify top performers by engaged sessions and CTR via list_demo_analytics.
2. 2Outline each one's structure via get_flow_document: hook, feature order, CTA placement, pacing.
3. 3Synthesize into one reusable pattern, not a copy of any single demo.
4. 4Present the pattern as a short template.

Workflow

1. 1Take the structural pattern and target persona as input.
2. 2Pull persona context: what they care about, objections, and vocabulary.
3. 3Rewrite each section in the persona's language, adjusting feature emphasis.
4. 4Flag any part of the pattern that doesn't fit this persona.

Workflow

1. 1Pull the ticket or changelog content: what to show, audience, context.
2. 2Apply the top-performer pattern for structure.
3. 3Pull brand voice and product facts via get_workspace_knowledge.
4. 4Draft a step-by-step script for a builder to review and refine.

Workflow

1. 1Take use case, persona, and deal stage as input.
2. 2Find matches via search_projects and search_interest_flows.
3. 3Early stage favors the shortest, broadest flow; late stage favors a specific, feature-deep one.
4. 4Recommend 3–5 flows ranked by fit, with a one-line reason each.

Workflow

1. 1Pull the call summary or transcript from a connected call recording tool.
2. 2Extract use cases, features, and objections discussed.
3. 3Match via search_projects / search_interest_flows.
4. 4Recommend the best-fit demo with a reason tied to something specific said on the call.

Workflow

1. 1Find the link via list_launchpad_share_links or get_share_link.
2. 2Check what was opened, how far the visitor got, and what they clicked.
3. 3Draft a specific follow-up if there's engagement, or a lighter nudge if not.
4. 4Keep the draft to 3–4 sentences.

Workflow

1. 1Pull last-published dates via list_projects and get_project.
2. 2Pull traffic on the same set via list_demo_analytics.
3. 3Score each demo: higher traffic and more days since update means higher priority.
4. 4Output a ranked list with the reasoning shown, not just a score.

Workflow

1. 1Take the feature or UI change as input, ideally with a description of the “before” state.
2. 2List demos via list_projects / get_project, prioritizing the affected product area.
3. 3Scan candidates via get_flow_document for references to the old version.
4. 4Output demo, step, what's outdated, and confidence level.

Workflow

1. 1Use the team's stored intent criteria, captured once and kept fixed.
2. 2Pull data via list_visitors and list_accounts with relevant filters.
3. 3Flag an account or visitor only if it meets a defined threshold.
4. 4Ask before updating the standing definition if criteria drift.

Workflow

1. 1Take a flagged visitor or account as input.
2. 2Pull detail via get_visitor or get_account.
3. 3Format into a fixed template: name, role, company, demo, steps, CTAs, suggested next step.
4. 4Post via the Slack connector, or output the formatted text to paste.