Loading...
Loading...
Found 143 Skills
When the user wants to design, optimize, or improve lead qualification forms and processes. Also use when the user mentions "lead scoring," "qualification criteria," "BANT," "discovery questions," "intake form," "lead routing," "MQL," "SQL," or "qualification framework." This skill covers capturing the right information to qualify and prioritize sales leads effectively.
Must invoke for any request to create, edit, evaluate, understand, or improve a RevenueCat Paywall in the dashboard — including questions about a specific paywall or general paywall design recommendations. Not for presenting a paywall in app code (use revenuecat-paywall).
Audita um perfil de Instagram e reescreve a bio. Use quando a pessoa pedir análise de perfil, revisão de bio, "meu perfil não converte", "o que melhorar no meu Instagram", ou colar bio, nome, link, destaques ou posts (ou um print) pedindo opinião. Dá nota de 0 a 10 em sete critérios, reescreve a bio em 3 versões de até 150 caracteres e lista as 3 mudanças de maior impacto, em ordem.
Use when creating or improving persuasive copy, launch offers, fundraising appeals, onboarding prompts, sales pages, calls to action, or behavior-change messages where the goal is effective persuasion without deception, coercion, fake proof, fake scarcity, or overstated authority.
[Sales Diagnosis] Private Domain Sales Diagnosis — from the customer adding WeChat and showing intent, to quoting, closing, repeat purchases, upselling, and complaints, checking each step of why sales get stuck: Is the pacing right? Is there an anchor? How to set up first/second/third conversions? Is follow-up segmented? Have you fallen into the traps of low-to-high conversion / 9.9 yuan lead courses / routine promotions? Triggered when users say "customer doesn't reply me", "chatted but didn't order", "how to quote", "how to close", "repeat purchases not increasing", "customer says expensive", "customer deleted me", "help me review my sales script". | By Xiaoye
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
Use when a site needs an FAQ or help section, or when visitors predictably have questions about pricing, billing, cancellation, data, delivery, or how the product works that the site does not answer at the point of decision. It works out the real questions from the product, its support traffic, and its own policies, writes answers only from facts it can verify, and builds the FAQ in the project's existing design. Do not use it to invent questions or answers, to pad a self-explanatory site with a generic FAQ, or to write legal, refund, or privacy wording the owner has not published.
When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.
visant-killer sub-skill: frontend decision system where every interface choice names the business variable it moves; the required deliverable is the route classification table. Use on "redesign this screen", "critique this UI", "visual hierarchy", "redesenhar tela", "criticar interface", "hierarquia visual", "cortar excesso", "empty state".