메뉴
Análisis y optimización del embudo de ventas de visita a compra. Usar cuando: "embudo de ventas", "funnel analysis", "CRO", "por qué no compran", "dónde pierdo clientes", "optimizar checkout", "signup friction", "onboarding drop-off", "optimizar conversiones".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | market-funnel |
| description | Análisis y optimización del embudo de ventas de visita a compra. Usar cuando: "embudo de ventas", "funnel analysis", "CRO", "por qué no compran", "dónde pierdo clientes", "optimizar checkout", "signup friction", "onboarding drop-off", "optimizar conversiones". |
Map the complete conversion path, identify drop-off points, quantify friction, and deliver optimizations ranked by revenue impact. Write analysis to FUNNEL-ANALYSIS.md.
Run as /market funnel <url>. Fetch the target site and trace every step from landing to conversion.
Full reference table with types, steps, and key metrics: references/funnel-frameworks.md. Main types:
For each page document:
STEP [#]: [Page Name]
URL: [url]
Page Type: [landing/product/pricing/cart/checkout/form/thank-you]
Primary Action: [what user should do]
Next Step: [where user should go]
Exit Points: [where users might leave]
Friction Elements: [anything that slows/confuses]
Trust Elements: [anything that builds confidence]
Estimated Load Time: [fast/moderate/slow]
Create ASCII funnel map with estimated conversion rates at each step. Adjust percentages to match observations or user-provided data.
Score each page on 5 dimensions (0-10 each). Page score = average.
| Dimension | What to Evaluate |
|---|---|
| Clarity | Is page purpose immediately obvious? |
| Continuity | Does it logically continue from previous step? |
| Motivation | Enough reason to take next action? |
| Friction | How easy to complete desired action? (10 = frictionless) |
| Trust | Trust signals appropriate for commitment level? |
Score interpretation: 8-10 optimized; 6-7 functional; 4-5 priority fix; 0-3 critical.
Common drop-off causes, signals, and fixes by stage: references/funnel-frameworks.md. Key stages to analyze:
If funnel includes a lead magnet, score on (0-10 each): Relevance, Specificity, Perceived value, Quick win, Product alignment, Opt-in friction.
Calculate or estimate. Ask user for traffic/revenue if not inferable:
Traffic: Monthly Visitors, Traffic Sources breakdown
Conversion: Visitor->Lead, Lead->MQL, MQL->Opportunity, Opportunity->Customer, Overall
Revenue: AOV, LTV, CAC, LTV:CAC Ratio (target 3:1+), RPV
Benchmarks by funnel type: references/funnel-frameworks.md.
RPV = Monthly Revenue / Monthly Visitors. The master metric for funnel optimization.
Always translate recommendations into RPV and annual revenue impact. Show three scenarios: conservative, base case, aggressive.
Lift estimates for common optimizations: references/funnel-frameworks.md.
| Priority | Impact | Effort | Timeline |
|---|---|---|---|
| P1 — Do Now | >10% lift | <1 day | This week |
| P2 — Plan | >10% lift | 1-5 days | This month |
| P3 — Schedule | 5-10% lift | <1 day | This month |
| P4 — Backlog | 5-10% lift | 5+ days | This quarter |
| P5 — Nice to Have | <5% lift | Any | When resources allow |
Top of Funnel: Headline A/B testing (10-30%), social proof above fold (5-15%), page speed (5-20%), exit-intent popup (2-5% of exiting visitors).
Middle of Funnel: Case studies (10-20%), comparison/"vs" pages (5-15%), interactive demos (15-30%), retargeting emails (10-25%).
Bottom of Funnel: Pricing page redesign (10-25%), checkout friction reduction (5-15% per friction point), risk reversal (10-20%), urgency elements (5-15%), cart abandonment emails (5-15% of carts).
Post-Purchase: Onboarding emails (10-20% churn reduction), upsell on thank-you page (5-15% AOV lift), referral program (5-15% new acquisition), NPS at 30 days.
Use full checklist from references/funnel-frameworks.md. Key elements: value-framing headline, max 3 plans, highlighted "Most Popular", annual pricing first, social proof near pricing, FAQ for top objections, guarantee, action-language CTAs.
Full friction audit: references/funnel-frameworks.md. Core: count fields (3-5 lead gen, 5-8 checkout), count steps (1-3 max), progress indicators, mobile usability, inline validation quality.
For each funnel stage, recommend appropriate email sequence. Complete mapping: references/funnel-frameworks.md.
Match source to entry point based on intent/trust level. Complete table: references/funnel-frameworks.md. Core principle: high-intent branded search -> pricing/signup; cold social -> lead magnet/educational page.
Formato de salida: ver references/output-template.md.
MARKETING-AUDIT.md exists, reference conversion scores already capturedCOPY-SUGGESTIONS.md exists, apply copy improvements to friction pagesEMAIL-SEQUENCES.md exists, verify alignment with funnel stagesCOMPETITOR-REPORT.md exists, compare funnel effectiveness against competitors/market copy for page-specific copy, /market emails for nurture sequences, /market landing for CRO deep dive on specific pageVercel a profundidad — CLI avanzado, CI/CD, env vars y patrones Next.js App Router (Next 16). Reemplaza al plugin oficial de Vercel (43 skills) condensado a lo esencial. Complementa a `deployment` (que cubre el deploy básico). Usar cuando: "vercel link", "monorepo vercel", "vercel build --prebuilt", "vercel promote", "vercel rollback", "CI/CD vercel", "GitHub Actions vercel", "VERCEL_TOKEN", "vercel env pull", "OIDC token", "VERCEL_OIDC_TOKEN", "project.json vs repo.json", "App Router", "server component async", "cookies() headers() params async", "middleware proxy.ts", "revalidateTag", "next/router next/navigation", "getServerSideProps migrar", "next 16 breaking changes". Do NOT use for: deploy básico a Vercel (usar `deployment`), Railway, Express puro, ni AI SDK/Workflow/shadcn del plugin (esos quedaron fuera del recorte — reactivar el plugin oficial si se necesitan).
Autenticación en Next.js: NextAuth v5 (Auth.js), JWT, sesiones, middleware y RBAC. Stack: Next.js App Router + NextAuth v5 / Supabase Auth / JWT custom. Usar cuando: "NextAuth", "Auth.js", "login", "sesión", "JWT", "middleware de auth", "proteger rutas", "RBAC", "roles y permisos", "OAuth", "credentials provider", "useSession", "getServerSession", "auth middleware", "redirect si no autenticado".
Colas de trabajo asíncronas con BullMQ + Redis en Node.js/Express. Reintentos, concurrencia, delays anti-ban, workers y monitoreo. Usar cuando: "cola de mensajes", "job queue", "BullMQ", "tareas en background", "envío masivo", "anti-ban WhatsApp", "rate limiting mensajes", "worker", "reintentar tarea fallida", "procesar en segundo plano", "Bull", "Redis queue", "scheduled jobs", "delayed jobs".
Agrega un chatbot, asistente IA o chat widget a un sitio web o app. Usar cuando: "chatbot", "chat widget", "asistente virtual", "chat flotante", "bot de ventas", "bot de soporte", "FAQ bot", "useChat", "streaming chat", "Vercel AI SDK", "asistente inteligente", "chat con IA", "embedded chat".
Integra un CMS headless a Next.js para que el cliente edite contenido sin código. Stack: Sanity / Contentful / Strapi. Usar cuando: "CMS", "headless CMS", "Sanity", "sitio administrable", "blog con CMS", "el cliente quiere editar", "GROQ", "live preview", "contenido dinámico", "Strapi".
Dashboards y visualización de datos en React/Next.js. Stack: Recharts / Chart.js. Usar cuando: "dashboard", "gráfica", "chart", "KPIs", "métricas", "stat cards", "bar chart", "pie chart", "line chart", "heatmap", "panel de analytics", "reporting dashboard", "admin panel con datos", "visualizar datos".