share
$
npx mdskill add openai/role-specific-plugins/shareDeploy the user's runnable prototype so they can share it with others.
SKILL.md
.github/skills/shareView on GitHub ↗
--- name: share description: "Share a runnable prototype using the user's preferred deployment tool." --- # Share Deploy the user's runnable prototype so they can share it with others. ## Critical Overrides - Refer to the Plugin router [$index](../index/SKILL.md) before proceeding. - Follow [$critical-overrides](../../references/critical-overrides.md). ## User Context Before starting, load [$user-context](../user-context/SKILL.md) and run its preflight script when local shell access is available. Use saved product URLs, Figma files, screenshots, reference images, codebase paths, Storybook, tokens, design systems, brand assets, component refs, browser preferences, and share targets as grounding material when relevant. Do not inspect every saved reference. Inspect only what the current task needs. ## Workflow 1. Confirm the prototype directory and the user's preferred deployment target. 2. If the user invokes Product Design with @Sites, @Vercel, or another deployment tool, treat that as the selected hosting target. 3. If the user did not choose a target, ask one question: > Where should I deploy this: @Sites, @Vercel, or another target? 4. Use the selected deployment tool when it is available. 5. If the selected tool is not available, say that clearly and ask whether to use another target. 6. Run the deployment when possible. Do not give setup instructions if you can complete the deployment directly. 7. Return the shareable URL. 8. State any misses or manual follow-up the user still needs to do. ## Rules - Do not deploy before the user chooses or confirms the target. - Do not claim the prototype is shared until you have a working URL. - If the selected tool is not available, say that clearly and ask whether to use another target.
More from openai/role-specific-plugins
- analyze-account-signalsAnalyze fresh signals for a named account, owner portfolio, or watchlist and turn them into evidence-backed account intelligence using active Sales source categories and user-provided context.
- analyze-data-qualityAssess whether tables, query results, files, or dataframes are trustworthy enough for analysis, modeling, dashboards, experiments, or pipelines. Use for grain, freshness, nulls, duplicates, schema drift, broken joins, referential integrity, distribution shifts, leakage, backfills, source mismatches, automated quality checks, and data-quality regressions.
- auditAudit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, placing them in Figma or a local folder, then reporting UX, design, and accessibility findings from that evidence. Use when the user asks to audit, critique, review, inspect, assess, or evaluate a product experience.
- build-business-caseBuild customer-led business cases, ROI narratives, value models, executive summaries, and customer-ready value stories from uneven customer context, metrics, transcripts, notes, and public evidence.
- build-competitive-briefBuild a multi-competitor build-competitive-brief report, comparison matrix, and battlecard-style objection package using user-provided materials, optional connector-assisted research, and public evidence.
- build-dashboardBuild source-backed analytical dashboards that help teams monitor performance, explore drivers, and act on product or business metrics. Use when the user needs a dashboard, scorecard, monitoring view, BI dashboard, MCP artifact dashboard, or Streamlit dashboard with clear metrics, filters, validation, and handoff.
- build-reportBuild polished analytical reports for executive, product, business, and technical audiences, and act as the completion contract for Data Analytics report runs. Use when the final artifact needs an answer-first narrative, evidence-backed findings, charts/tables, caveats, source metadata, and either an MCP app report or an HTML report with Seaborn-generated charts.
- catalyst-calendarUse when building public-equity-investing catalyst calendars. Do not use for full event underwriting; use event-driven-analyzer.
- company-tearsheetUse when creating source-backed public issuer tearsheets. Do not use for private diligence, fund diligence, vendors, or market maps.
- comps-valuationProduce Public Equity Investing comparable-company valuation in report or workbook mode. Use for peer selection, multiple analysis, valuation read-throughs, implied prices, comps dashboards, Excel or Sheets comps, refreshable peer tables, model updates, and comps workbook QA. Do not use for DCF-only, credit-security, or generic market commentary requests.