557건 · 관련도순
Build or refine brand positioning with audience, category, differentiators, proof, tone, JTBD signals, and competitive context. Use when marketing, founders, or GTM teams need a positioning canvas, messaging pillars, or campaign foundation. Do not use for isolated ad copy tweaks with no strategy question.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft crisis communication packages including holding statements, stakeholder updates, Q&A documents, and internal briefs. Follows ICS (Incident Command System) communication principles. Use during PR crises, data breaches, product recalls, or any event requiring rapid coordinated messaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a Go-to-Market (GTM) plan for new product launches, market entries, or feature rollouts. Covers market sizing (TAM/SAM/SOM), positioning, messaging, channel strategy, pricing approach, and launch timeline. Use when preparing to bring something new to market. Do not use for ongoing marketing operations or campaign execution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze competitors using Blue Ocean Strategy's ERRC Grid and Strategy Canvas (W. Chan Kim and Renee Mauborgne) to identify uncontested market space, not just who is better on the same axes. Produces an ERRC Grid, Strategy Canvas, positioning matrix, messaging comparison, and differentiation map. Use when the user asks for competitive analysis, competitor research, "how do we compare to X", positioning vs competitors, market landscape, "analyze our competition", "where is the blue ocean", or wants to update competitor docs. Writes to knowledge/markets/competitors.md. For a lightweight competitor summary in the knowledge base, see brand-context. For positioning against them, see positioning-doc. For a product or feature-level comparison outside the marketing knowledge base, see competitive-analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate, score, and shortlist brand names through a guided interview. Use when the user says "name my brand", "help me name", "come up with a name", "naming ideas", "what should I call this", "brand name", "product name", "company name", "rename", "rebrand", or is stuck choosing between names. Self-contained and brand-agnostic: it does not read knowledge/, so it works for naming a brand-new venture, product, service, feature, or rebrand from scratch, before any brand context exists. Runs on Alexandra Watkins' SMILE and SCRATCH tests to generate and filter, Marty Neumeier's 7 criteria to score, and the Lexicon Branding method for sound symbolism and strategy. Asks the user questions before generating. For the positioning the name has to carry, see positioning-doc. For the message architecture built on top of it, see messaging-framework.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing how an Agentforce agent transfers the conversation to a human agent (Omni-Channel), to another bot/agent, or to an alternate workflow — including context package, deflection, escalation triggers, and user messaging. Triggers: 'agent to human handoff', 'agentforce escalate to omni channel', 'agent to agent handoff', 'transfer conversation with context', 'agent deflection fallback'. NOT for topic scope and selector design — use agentforce/agent-topic-design. NOT for the overall Einstein Bot plus Agentforce estate topology — use architect/conversational-ai-architecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when building custom channel integrations with the Agentforce Agent API or BYOC (Bring Your Own Channel) for CCaaS — covering session lifecycle management, webhook handling, externalSessionKey design, sequenceId sequencing, BYOC Interaction API integration, and conversation state management. NOT for standing up a standard channel (Embedded Service, Slack, Experience Cloud, Messaging) — use agentforce/agent-channel-deployment. NOT for writing the Apex actions the agent invokes — use agentforce/custom-agent-actions-apex.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when defining patient engagement portal requirements for Health Cloud: appointment scheduling, secure in-portal messaging, health assessments, patient education, and self-service features. NOT for care team workflows, SDOH barriers and care gaps — use admin/care-coordination-requirements. NOT for patient portal licensing and cloud topology — use architect/health-cloud-multi-cloud-strategy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when configuring the outbound Send Email quick action in Lightning Case Feed — creating the action in Setup on Case (Action Type = Send Email), attaching a default Custom email template, setting predefined To/CC/BCC values, wiring QuickAction.QuickActionDefaultsHandler Apex defaults, respecting the Lightning Experience 10-file / 25 MB attachment limits, and letting agents move an email to a different case. Trigger keywords: Send Email quick action, case email composer, Email action missing from Case Feed, Don't Apply Template Subject, QuickActionDefaultsHandler, SendEmailQuickActionDefaults, move email to another case. NOT for Email-to-Case inbound routing, routing addresses, or thread-ID matching (use admin/email-to-case-configuration), NOT for authoring or migrating the templates themselves (use admin/email-templates-and-alerts and admin/classic-email-template-migration), and NOT for Apex Messaging.SingleEmailMessage sends outside Case Feed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit patient-facing healthcare software for portal feature completeness, secure messaging, health literacy, telehealth readiness, consent management, and HIPAA compliance. Triggers: evaluating a patient portal, checking PHI exposure in notifications, auditing telehealth flows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage persistent coding sessions across Claude Code, Codex, Antigravity (agy), Grok Build, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, exposing the orchestrator's 78 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose, or running as an Agent Client Protocol (ACP) agent that Zed / JetBrains / Neovim / Emacs / VS Code / dsh can drive directly. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "auto research", "switch model", "hand off a session", "session handoff", "switch engine", "continue on codex", "continue on claude", "move this session to another engine", "multi-agent coding", "coding session", "session inbox", "grok session", "grok build", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol", "ultracode", "dynamic workflow", "fanout", "fan-out", "best-of-N", "steer turn", "interrupt turn", "fork thread", "rollback turns", "acp", "agent client protocol", "clawo acp", "zed agent", "jetbrains agent", "external agent", "dsh subagent", "deepseek harness", "clawo runs", "run ledger", "session cost", "coding-agent token usage", "spend cap", "budget limit", "maxBudgetUsd", "durable workflow", "resume a run", "verify a coding run", "acceptance contract", "evidence bundle", "did the agent's tests actually pass", "protected tests", "agent edited the tests", "human gate", "repair loop", "clawo workflow", "clawo verify", "clawo solve", "clawo fanout", "fix and verify", "solve from the terminal".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need Codex to coordinate multiple agents through Agent Relay for peer-to-peer messaging, lead/worker handoffs, or shared status tracking across sub-agents and terminals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms. Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build cross-browser extensions with WXT — the modern framework for Chrome, Firefox, Safari, and Edge extensions. Use when someone asks to "build a browser extension", "Chrome extension with React", "WXT framework", "cross- browser extension", "manifest v3 extension", "build Firefox extension", or "browser extension with TypeScript". Covers content scripts, background workers, popup/options pages, storage, messaging, and publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
@thedotmack's personal landing page design system. Use this skill whenever building landing pages, marketing sites, product pages, or conversion-focused web experiences. Covers visual hierarchy, UX patterns, marketing copy, messaging strategy, and conversion optimization based on proven preferences and successful projects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Graceful HTTP error handling in Web controllers with status-code-specific user messaging
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks and fixes Chinese copywriting with autocorrect-backed workflows for text and single-file Markdown/TXT inputs. Use when user asks to normalize Chinese punctuation, spacing, or full-width/half-width usage. Also triggers for "校对", "检查排版", "中英文空格", "全角半角". Does not rewrite document structure, product claims, or UI messaging.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a crisis communication plan with holding statements, stakeholder messaging, media responses, and internal comms templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete brand building and go-to-market system — from identity foundations through positioning, messaging, visual systems, and launch execution. Works for solopreneurs, startups, and established b...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze ad creatives (images and videos) extracted from competitor research. Use when given a directory of ad images, video files, or transcripts to evaluate ad quality, score visual and messaging effectiveness, assign a scale score for viral/engagement potential, and generate a cross-creative pattern summary. Triggered by requests like "analyze these ads", "score these creatives", "what hooks are competitors using", "evaluate the ad library", "give me a scale score", "analyze the ad folder", or "what's working in these ads".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Manage the MoltBot A2A Hub — register agents, search the registry, relay messages, and stream responses. Use when working with the A2A agent-to-agent protocol hub deployed at a2a-hub.fly.dev.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agent profiles, public channels, and direct messaging between AI agents via the a2achat.top API.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide technical communication for software developers. Covers email structure, team messaging etiquette, meeting agendas, and adapting messages for technical vs non-technical audiences. Use when drafting professional messages, preparing meeting communications, or improving written communication.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.