555건 · 관련도순
Unified messaging via three access tiers — MCP (live API), beeper-cli (authenticated CLI), and direct SQLite→DuckDB (full archive). Search, analyze, and act across all networks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or build custom language/messaging from buyer, competitor, community, and CRM evidence. Triggers: pre-research, source discovery, provider strategy, research data sources, ScrapeCreators, X/Twitter data, Reddit comments, public and private datasets, CRM data, workflow data, custom language, messaging language, pain language.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Send and receive messages between AI agents using AI Maestro's messaging system. Use this skill when the user asks to "send a message", "check inbox", "read messages", "notify [agent]", "tell [agent]", or any inter-agent communication.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts a company's visual identity from screenshots (best) or its website (fallback) and writes a DESIGN.md brand file: machine-readable tokens for colours, typography, spacing, corner radius and logo usage, plus short prose explaining how and when to use each, and a list of do's and don'ts. Any later page, deck, carousel or ad can read the tokens instead of guessing. Triggers: "brand kit", "brand guidelines", "extract our brand", "design tokens", "colours and fonts from", "visual identity", "DESIGN.md". Not for tone of voice (use /tov-guidelines) or messaging (use /messaging).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts a company's tone of voice from its own content and turns it into rules a writer or an AI can follow. Phase 1 analyses 15 to 20 pages for sentence, paragraph, word and structure patterns with frequency counts; after the user reviews it, Phase 2 writes the guidelines: tone attributes with before and after examples, a We are / We are not table, tone by context, vocabulary to use and avoid, and open questions. Triggers: "tone of voice", "brand voice", "voice guidelines", "writing style guide", "extract voice from our website", "TOV". Not for visual identity (use /brand-kit) or messaging (use /messaging).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyses sales call transcripts (and churn or renewal calls) to find why deals are won, lost, kept or churned. Reads each call across six dimensions (product, messaging, sales process, pricing, competition, customer context), pulls verbatim quotes with the speaker named, counts how often each pattern appears, and writes findings with recommendations. Works with any recorder export or pasted text. Triggers: "win/loss analysis", "why do we lose", "why do we win", "analyse these sales calls", "lost deals", "churn analysis", "objection patterns". Feeds /positioning and /messaging. Not for general meeting summaries or competitor research (use /competitor-research).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze sales-call transcripts to extract why deals are won and lost across six dimensions — product, messaging, GTM/sales, pricing, competition, and customer context. Produces aggregated patterns with verbatim buyer quotes, frequencies, and recommendations. Writes to marketing/win-loss/win-loss.md as the evidence base under positioning, messaging, and ICP. Triggers - "win loss analysis", "why are we losing deals", "why do we win", "analyze sales calls", "churn analysis", "deal review"
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Maintain the pure-Go SQLite notification outbox, public parser, runtime messaging-provider injection, worker leases, and registration delivery E2E tests. Excludes SMTP transports and registration enrollment state.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when working with Telnyx communication APIs for SMS/MMS messaging, voice calls, phone number management, messaging profiles, webhook integration, two-way SMS conversations, bulk sending, message scheduling, or production deployment of telephony features. v2.0 includes official Telnyx documentation, production patterns from Twilio-Aldea (Ed25519 signature validation, provider-agnostic webhooks, idempotency), and TypeScript code examples.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
"Design push notification and messaging strategies including channel selection, timing optimization, personalization, and fatigue management. Use this skill when the user needs to improve notification engagement, reduce opt-out rates, plan multi-channel messaging, or A/B test notification content — even if they say 'our push open rates are low', 'users are unsubscribing', 'when should we send notifications', or 'which channel to use for alerts'.".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Coordinate agents via messaging: send, receive, and manage inter-agent communication. Use when agents need to collaborate, hand off work, or notify each other.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Product marketing and go-to-market strategy for B2B SaaS launches and positioning. Use this skill when planning a product launch, developing positioning and messaging, analyzing competitive landscape, building customer advocacy programs, designing a customer referral program (who may accept the reward, how the introduction is made), designing a win/loss interview program, working out why we lose deals, designing GTM strategy, creating category positioning, planning analyst briefings, or deciding which country to expand into and how far to localize. Also use it for an early-stage startup where the founder is still doing the selling — running founder-led sales, setting up a design-partner program, judging whether you have product-market fit, deciding what not to do yet, deciding when to hire the first AE or first marketer, and moving upmarket to larger buyers. Also use it when your company has just acquired another (or is about to), to plan the marketing integration: what you may and may not do between signing and close, the first letter to the acquired customers, whether to keep, endorse, fold in or retire the acquired brand, merging the two marketing databases without mailing people who opted out, when to start cross-selling, and announcing a product sunset. Also use it to design a demand-generation campaign and the channel plan it runs on: one campaign with one job, the offer for buyers who are and are not in market, what each channel is for, the kill and scale rules set before launch, the follow-up sales agrees to, the yearly calendar of always-on programs and tentpole campaigns, and which channels to keep, test or stop. Also use it for brand marketing and demand creation — how much to spend on brand versus performance, what to measure when a brand campaign produces no conversion event, and how to answer "we cannot attribute it". Also triggers on: founder-led sales, founder-led GTM, design partners, design partner agreement, first customers, first 10 customers, do we have product-market fit, PMF, Sean Ellis test, very disappointed survey, pre-seed, seed stage, when to hire our first AE, first sales hire, first marketing hire, moving upmarket, going upmarket, enterprise readiness, first enterprise deal, what do enterprise buyers need before they sign, positioning, product launch, beta program, early access program, design partners, private preview, public preview, general availability, GA launch, when can we call it GA, can sales sell a beta feature, selling the roadmap, launch tier, competitive intelligence, messaging, customer advocacy, win/loss analysis, win/loss interviews, why we lose deals, closed-lost analysis, loss reason, close-reason field, competitive displacement, displace an incumbent, rip and replace, competitive takeout, switch from a competitor, win deals from a competitor, incumbent contract, renewal window, auto-renewal notice period, switching costs, EU Data Act, cloud switching rights, why do we lose to no decision, GTM, category design, ideal customer profile, ICP, what is our real ICP, who actually buys from us, refresh our ICP from closed-won deals, ICP refresh before planning, analyst briefing, G2 review, international expansion, market entry, expand into Europe, which country should we launch in next, localization, translate our site, in-country go-to-market, regional GTM, is cold email legal in Germany, brand marketing, brand awareness, brand vs performance, brand versus demand gen, demand creation, demand capture, 95-5 rule, out of market buyers, category entry points, distinctive brand assets, mental availability, brand tracking, brand health, brand lift, share of search, how do we measure brand, justify brand spend, brand budget. Also triggers on public-sector marketing: sell to government, government marketing, public sector go-to-market, federal marketing, state and local government, SLED, FedRAMP, FedRAMP marketing claims, can we say FedRAMP ready, GovRAMP, StateRAMP, VPAT, accessibility confor
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a product positioning document. Use when the user says "write a positioning doc", "positioning statement", "how should we position this product", "positioning for [product]", "we need to differentiate from competitors", "product positioning and messaging", "positioning workshop", "help me define our position in the market", or wants to establish how a product should be perceived relative to competitors. For customer-facing message wording, see messaging-framework. For the competitive research behind it, see competitor-analyst. For storing it in the knowledge base, see brand-context.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create source-grounded paid-ad campaign concepts, messaging, copy, creative briefs, and production plans from a validated brand profile, campaign objective, platform requirements, and optional audit evidence. Triggers on: campaign brief, campaign concepts, create a campaign, ad concepts, ad copy, ad messaging, creative brief, headlines, descriptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inbound email processing in Salesforce via Email Services + the `Messaging.InboundEmailHandler` Apex interface. Covers EmailService configuration (running user, accept-from address, attachment handling, error / failure routing), the EmailServicesAddress per-routing-address pattern, the handler's `Messaging.InboundEmail` payload (text body, HTML body, headers, attachments, in-reply-to threading), and the canonical Email-to-Case alternative for case creation. NOT for outbound email (use admin/email-templates-and-alerts), NOT for Email-to-Case flow customization itself (use admin/email-to-case-configuration). Trigger keywords: EmailServicesFunction, EmailServicesAddress, runAsUser, localPart, EmailDomainName, attachmentOption, overLimitAction, errorRoutingAddress, routing address, inbound email limit.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Custom Notification Types for desktop/mobile push alerts from Flow or Apex: type creation, target channels, Messaging.CustomNotification invocation, recipient limits, bulk notification patterns. NOT for choosing channels, consent, or notification-fatigue policy — use admin/custom-notification-type-design. NOT for email alerts — use admin/email-templates-and-alerts. Trigger keywords: notiftype, notificationtypes directory, customNotifTypeName, customNotificationAction, setNotificationTypeId, targetPageRef, NotificationTypeConfig.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design asynchronous messaging patterns in Azure using Service Bus, Event Hubs, Event Grid, and Storage Queues. Use this skill when users ask for queueing, pub-sub, event streaming, retries, or decoupled system design. Covers delivery semantics, dead-lettering, idempotency, and monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Message queues, pub/sub, event sourcing with Kafka, RabbitMQ, Redis Streams. Activate on: event-driven, message queue, pub/sub, Kafka, RabbitMQ, event bus, async messaging, dead letter queue. NOT for: CQRS projections (use cqrs-event-sourcing-architect), real-time WebSocket (use websocket-realtime-expert), observability (use observability-apm-expert).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-session Claude Code instance messaging via claude-peers-mcp broker
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Envie e receba mensagens criptograficamente assinadas entre agentes de IA usando o Agent Messaging Protocol (AMP). Use quando o usuário pedir para "enviar uma mensagem para um agente", "verificar caixa de entrada do agente", "mensagear outro agente", "responder a uma mensagem", "notificar um agente" ou qualquer tarefa de comunicação entre agentes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cloud design patterns for distributed systems architecture covering 42 industry-standard patterns across reliability, performance, messaging, security, and deployment categories. Use when choosing architecture patterns for reliability, performance, messaging, or security in a distributed cloud system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
agents-bridge — the Lifeboat, auch: Time Capsule. Portable, provider-neutral file bridge for bootstrap surfaces, truth pointers, separate memory silos, messaging, presence, cooperative locks, and reversible host recovery.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create source-grounded paid-ad campaign concepts, messaging, copy, creative briefs, and production plans from a validated brand profile, campaign objective, platform requirements, and optional audit evidence. Triggers on: campaign brief, campaign concepts, create a campaign, ad concepts, ad copy, ad messaging, creative brief, headlines, descriptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.