Total 34,556 skills
Showing 12 of 34556 skills
When the user wants to build or improve a sales bot's ability to send brochures, videos, floorplans, or other media contextually during conversations. Also use when the user mentions "sending attachments," "media sharing," "document delivery," "sending brochures," or "content delivery."
When the user wants to build or improve a sales bot's ability to recover prospects who stopped responding mid-conversation. Also use when the user mentions "ghost recovery," "unresponsive prospects," "conversation dropoff," "re-engagement sequences," or "dead conversation revival."
When the user wants to improve their ability to create genuine connection and trust quickly with prospects. Also use when the user mentions "connecting with prospects," "building trust," "relationship selling," "warming up cold leads," "getting prospects to open up," or "first impressions."
When the user wants to build or improve a sales bot's ability to reply fast enough to feel real-time but not unnaturally instant. Also use when the user mentions "response speed," "reply timing," "bot response delay," "natural pacing," or "message timing."
When the user wants to build or improve a sales bot's ability to test individual message variants. Also use when the user mentions "message testing," "A/B testing messages," "variant testing," "message optimization," or "reply testing."
Author ZenML pipelines: @step/@pipeline decorators, type hints, multi-output steps, dynamic vs static pipelines, artifact data flow, ExternalArtifact, YAML configuration, DockerSettings for remote execution, custom materializers, metadata logging, secrets management, and custom visualizations. Use this skill whenever asked to write a ZenML pipeline, create ZenML steps, make a pipeline work on Kubernetes/Vertex/SageMaker, add Docker settings, write a materializer, create a custom visualization, handle "works locally but fails on cloud" issues, or configure pipeline YAML files. Even if the user doesn't explicitly mention "pipeline authoring", use this skill when they ask to build an ML workflow, data pipeline, or training pipeline with ZenML.
Use when working with ANY calendar event, reminder, EventKit permission, or EventKitUI controller. Covers access tiers (no-access, write-only, full), permission migration from pre-iOS 17, store lifecycle, reminder patterns, EventKitUI controller selection, Siri Event Suggestions, virtual conference extensions.
When the user wants to build or improve a sales bot's ability to confirm meetings and reduce no-shows. Also use when the user mentions "meeting confirmation," "calendar reminders," "no-show reduction," "appointment reminders," or "meeting attendance."
When the user wants to improve their persistent but respectful outreach that keeps deals moving. Also use when the user mentions "following up," "staying on top of deals," "persistent outreach," "keeping deals alive," "not letting deals fall through," or "consistent follow-up."
Expert guidance on building, debugging, and testing multiplatform iOS/Android apps and frameworks with Skip (skip.dev). Use when developers mention: (1) Skip, Skip.dev, skip-tools, or SkipStack, (2) building a multiplatform iOS+Android app from Swift/SwiftUI, (3) Skip Fuse (native) or Skip Lite (transpiled) modes, (4) transpiling Swift to Kotlin, (5) SwiftUI to Jetpack Compose bridging, (6) skip.yml configuration, (7) debugging Android builds from Xcode, (8) Skip CLI commands (skip create/init/test/export), (9) conditional compilation with #if SKIP or #if os(Android), (10) Skip Comments (SKIP INSERT/REPLACE/DECLARE/NOWARN), (11) bridging Swift and Kotlin code, (12) Skip module dependencies or Android Gradle configuration.
Generate a complete, ready-to-send creator campaign brief from a few inputs — product, platforms, deliverables, messaging, and audience. This skill should be used when writing a campaign brief, building an influencer brief, drafting a creator brief, generating a partnership brief, creating a brief for a product launch, putting together a campaign brief for a new launch, starting a new creator campaign, planning deliverables and content direction, or preparing any document that goes out to creators — even if the user does not call it a "brief." If the user needs brand context first, see brand-context. If the user needs content concepts after the brief, see creator-content-concept-generator. If the user needs outreach messages, see creator-outreach-sequence-generator. If the user needs to check content against the brief, see content-to-brief-compliance-checker.
When the user wants to build or improve a sales bot's ability to seamlessly connect prospects to live reps with full context passed along. Also use when the user mentions "warm handoff," "transfer to human," "live rep handoff," "context handover," or "seamless transfer."