Loading...
Loading...
Found 320 Skills
Design conversational commerce experiences across messaging platforms including chatbot flows, product cards, and conversion strategies. Use this skill when the user needs to sell through LINE, WhatsApp, Instagram DM, or other messaging channels, design chatbot purchasing flows, or integrate messaging into their sales funnel — even if they say 'sell through LINE', 'build a shopping chatbot', 'customers ask to buy in our DMs', or 'conversational sales strategy'.
Creates positioning, messaging, and brand architecture frameworks for multi-product companies. Use when the user wants to 'position a product suite,' 'multi-product positioning,' 'portfolio positioning,' 'brand architecture,' 'core narrative,' 'house of brands vs branded house,' 'product portfolio messaging,' 'launch a second product,' 'launch a new product into our suite,' 'audit our portfolio messaging,' or 'are our products fighting each other.' Sits above product-positioning and product-messaging in the hierarchy. Forces a brand architecture decision first, then builds the layered framework that single-product skills run inside of.
Develop a competitive positioning strategy for a solopreneur business. Use when deciding how to differentiate from competitors, what market position to own, how to frame your offering against alternatives, and how to communicate that position. Covers positioning frameworks (Jobs-to-be-Done, against/for, category creation), positioning statements, and translating position into messaging. Trigger on "how do I differentiate", "positioning strategy", "how to stand out", "differentiate from competitors", "market positioning", "what makes me different", "competitive positioning", "own a position".
Deploy and configure OpenClaw AI assistant with multi-model support and messaging channel integrations
Write a product positioning document and messaging framework. Use when asked to define product positioning, write a positioning statement, build a messaging framework, or create a messaging hierarchy. Produces a complete positioning doc with category definition, target customer, differentiation, proof points, messaging pillars, and persona-specific messaging.
Build messaging agents and apps with Spectrum — Photon's unified messaging SDK. Write your handler logic once and ship it across iMessage, WhatsApp Business, the terminal, or a custom platform. Spectrum is multi-platform by design and is becoming multi-language; the current SDK is `spectrum-ts` (TypeScript), with additional language SDKs planned. Use this skill for any Spectrum question — quickstart, multi-platform setup, receiving messages, content builders, spaces and users, reactions and replies, platform narrowing, the built-in providers (iMessage cloud/local/dedicated with message effects, Terminal TUI test harness, WhatsApp Business 1:1), custom event streams, graceful shutdown, building your own provider with `definePlatform`, and the production architecture patterns Photon uses internally to ship agents that live natively inside IM apps (five-stage inbound pipeline with debounce → batch flush → mark as read → generate → send, in-flight cancellation with abort signals, drain-in-handler, carry-forward, idempotent retries via stable client GUIDs and a startIndex resume cursor, per-resource memory scope `resourceId` vs `threadId`, durable job-failure audit log). This is the entry point for the skill; consult the topic files in this directory for full reference. Keywords: spectrum, spectrum-ts, photon, unified messaging, multi-platform, multi-language, im agent, messaging agent, imessage, whatsapp, whatsapp business, terminal, tuichat, definePlatform, custom platform, platform provider, platform narrowing, app.messages, Spectrum(), space, send, reply, react, tapback, typing indicator, responding, startTyping, stopTyping, content builder, text, attachment, voice, contact, richlink, poll, group, custom content, message effects, bubble effect, screen effect, line model, dedicated line, shared pool, custom events, app.stop, lifecycle, SIGINT, graceful shutdown, message queue, debounce, batch, in-flight, cancellation, abort controller, carry forward, idempotent retry, client guid, dedup, deduplication, startIndex, resume cursor, working memory, resourceId, threadId, per-resource memory, job failure, audit log, race condition, worker crash, retry, pg-boss, queue worker, conversational agent, chat agent, native messaging, agent architecture, production agent, spectrum patterns, best practices.
Build .NET applications with WolverineFX for messaging, HTTP services, and event sourcing. Use when implementing command handlers, message handlers, HTTP endpoints with WolverineFx.HTTP, transactional outbox patterns, event sourcing with Marten, CQRS architectures, cascading messages, batch message processing, or configuring transports like RabbitMQ, Azure Service Bus, or Amazon SQS.
Foundational context for the Zavu unified messaging API. Always loaded.
Reference and consulting skill for OpenClaw — a messaging gateway that connects AI agents to multiple communication platforms (Telegram, Discord, Slack, WhatsApp, iMessage, and more). Use when working with OpenClaw configuration, channels, Gateway setup, skills, cron jobs, MCP servers, memory, OAuth, or troubleshooting. Also use when the user asks how to implement a use case on their OpenClaw bot (daily morning brief, research workflows, competitive radar, decision playbook), how to add a new channel, or how to connect the CodeAlive context engine. Triggers on requests like "configure openclaw", "add Discord to my bot", "set up morning brief", "gateway not starting", "connect CodeAlive search", "OAuth re-auth", or any close paraphrase. Companion of install-openclaw-to-yc — install both together.
Implements push notifications across iOS, Android, and web using Firebase Cloud Messaging and native services. Use when adding notification capabilities, handling background messages, or setting up notification channels.
SDR outbound writing rules, 8 allowed messaging frameworks, and tone guidelines by offer type. Use when training SDRs, creating messaging guidelines, or standardizing outbound quality.
Strategic framework for mapping pain/persona intersections and messaging angles. Defines the structure for organizing creative strategy, not the tactics for execution. Use this when planning an organizational or systematic approach to creative strategy, or when a user provides a product and wants to define messaging angles, write strategic hooks, or execute ads in visual formats defined by awareness and decision stages.