Loading...
Loading...
Found 94 Skills
Write clear and helpful user guides and tutorials for end users. Use when creating onboarding docs, how-to guides, or FAQ pages. Handles user-focused documentation, screenshots, step-by-step instructions.
Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.
You are a professional Customer Service Specialist and Communication Strategist. Use this skill when the user wants to write customer service scripts, support email templates, feedback responses, FAQ content, or help center articles. Activate when the user mentions "customer service," "support email," "support template," "help center," "knowledge base article," "FAQ for support," "chatbot script," "live chat script," "phone script," "customer feedback response," "review response," "refund email," "cancellation template," "late shipping response," "apology email," "product outage response," "billing email," "customer onboarding message," "troubleshooting guide," "password reset article," "support ticket," "macro," "saved reply," "customer service playbook," "internal support doc," "review reply," "3-star review," "negative review response," "positive review response," "customer loyalty message," "subscription cancellation script," "exchange template," "customer portal content," "chatbot flow," "in-app help copy," "social media response," "support documentation," or "customer service tone." Covers scripts for phone, chat, and messaging; email templates for all support scenarios; feedback and review responses; FAQ sections; and full help center articles with troubleshooting guides.
Generate AEO-optimized content (Answer Engine Optimization) for AI search visibility - ChatGPT, Claude, Gemini, AI Overviews. Use when optimizing websites for AI citations, creating FAQ schemas, evidence panels, or analyzing content for LLM extraction readiness.
Product description writing — keyword integration, benefit-focused copy, FAQ, formatting
When the user wants to create, optimize, or audit FAQ page content. Also use when the user mentions "FAQ page," "frequently asked questions," "help page," "Q&A page," "FAQ schema," "FAQ section," "common questions," "FAQ SEO," or "accordion FAQ."
Answers Riverpod FAQ (ref.refresh vs invalidate, ConsumerWidget vs StatelessWidget, Ref vs WidgetRef, reset all providers, ref after unmount) and do/don't best practices (avoid init in widgets, avoid ephemeral state in providers, avoid side effects in provider init, static providers, riverpod_lint). Use when the user asks Riverpod FAQ, best practices, or do/don't guidelines.
Three-tier Pricing + Feature Comparison Table + FAQ
Create comprehensive troubleshooting guides, FAQ documents, known issues lists, and debug guides. Use when documenting common problems, error messages, or debugging procedures.
Generate a ready-to-send FAQ document that anticipates and answers the most common creator questions about a campaign brief, reducing back-and-forth messages and delays. This skill should be used when creating a campaign brief FAQ, writing answers to common creator questions about a brief, building an FAQ attachment for an influencer brief, reducing back-and-forth with creators after sending a brief, anticipating creator questions before launch, preempting influencer confusion about deliverables or timelines, generating a brief companion FAQ, writing a creator-facing Q&A for a campaign, drafting briefing clarifications for influencers, or creating a FAQ sheet to send alongside a content brief. For writing the campaign brief itself, see campaign-brief-generator. For writing individual content briefs, see content-brief-builder. For chasing creators who have not responded to a brief, see universal-creator-follow-up-chaser.
Answer Enable Banking API FAQs and apply best practices for ASPSP/PSU terminology, pricing and activation expectations, production compliance fields, restricted application account linking, ASPSP identifiers and BICs, beta integrations, user identification, balances, transaction history and continuation keys, PSU headers, rate limits, JWT handling, session validity, expired sessions, language selection, ASPSP_ERROR retries, iframe/WebView/CORS issues, payment statuses, bulk payments, TPP infrastructure, and sandbox credential lookup. Use when Codex needs to explain edge cases, design robust Enable Banking behavior, or troubleshoot recurring API and UX problems.
Write internal communications such as status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports, and project updates using repeatable internal formats.