Loading...
Loading...
Found 94 Skills
Searches for and retrieves existing content and media (articles, blogs, news, FAQs, events, products, images, logos, icons, photos, graphics, banners, hero images, audio clips, videos, documents) from Salesforce CMS or other connected sources. Use this skill ANY TIME a user says "find", "search", "get", "fetch", "retrieve", "look up", "locate", "show me", "list", or "I need" followed by content or media words like "blog", "article", "news", "FAQ", "event", "product page", "image", "logo", "icon", "photo", "banner", "audio", "video", "document". Also use for requests that mix both, like "reuse existing assets" for a page. Routes each intent to the correct sub-workflow — structured content search or media search — and can run both in the same request. Does not apply when the request is to generate NEW content or images from scratch, define content type schemas, or apply brand guidelines.
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement. Use when customer-facing teams must be ready before customers hear.
Use when a site looks finished but may still feel unfinished or untrustworthy to visitors: unclear main action, dead buttons, placeholder text, fake or unverifiable claims, missing contact path, weak 404, broken links, or missing loading and error states. It coordinates the trust-related specialists and verifies the fixes. Do not use it to add trust badges, invent testimonials or metrics, or manufacture an FAQ the product does not need.
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict 25-min agenda, Scrum Master rotation, 0–10 pulse check • 1:1 Framework — 9-dimension quantified pulse, 5-group deep question bank, bilateral feedback structure • Diagnostic layer — "stuck-at" detection: info / authority / collaboration / capability / direction • FAQ for 4 common failure modes (dead standups, status-report meetings, "I'm fine" 1:1s, scaling beyond 10 people) 🇨🇳 Your team has high autonomy — but standups are getting vague, weekly meetings turn into status reports, and you can't get honest answers in 1:1s. This three-layer Motivation playbook solves exactly this problem: standups are the information layer, weekly meetings are the alignment layer, and 1:1s are the individual layer. When these three things are done right, motivation isn't managed—it grows naturally. 🇯🇵 Your team has high autonomy, yet standups are vague, weekly meetings turn into progress reports, and you only get "I'm fine" in 1on1s — this playbook solves all three layers at once. 🇰🇷 Your team has high autonomy, but standups are vague, weekly meetings turn into progress reports, and you can't get honest feedback in 1:1s — this playbook solves all three layers simultaneously. Triggers: "team motivation" | "no one writes standups" | "weekly meetings turn into status reports" | "can't get honest answers in 1:1s" | "high-autonomy team management" | "how COOs manage teams" | "team motivation" | "standup best practices" | "1on1 framework" | "weekly meeting template" | "team motivation" | "team motivation" | "AI startup team ops" | "remote team alignment" | "engagement decline"
Use when a page is genuinely an article, product, organization, local business, event, FAQ, or breadcrumb and JSON-LD structured data exists or would truthfully describe visible content. It validates that markup parses and matches what visitors see. Do not use it to invent ratings, reviews, prices, or FAQs, to add schema for its own sake, or to chase rich results the content does not merit.
Use when a site should make its purpose and next step clear and its content should be real: primary call to action, dead-end pages, placeholder or lorem text, fake or unverifiable metrics, testimonials and logos, misleading claims, unfinished UI. It removes or flags fakes and verifies controls work. Do not use it to build an FAQ (use faq-readiness), to invent testimonials, metrics, or customers, to force a giant CTA onto every page, or to write marketing copy the owner has not approved.
FAQ identification from support tickets, step-by-step tutorial creation, screenshot/video script guidance, search optimization, and self-service deflection tracking.
Create effective internal team communications. Drafts newsletters, announcements, and messages that inform and engage team members.
Use this skill when users need to set up customer support systems, create help docs/FAQs, implement ticketing, build self-service resources, or optimize support operations. Activates for "too many support requests," customer support setup, or scaling support without hiring.
Build high-converting landing pages with a simple 6-section framework. Use for landing page guidance.