557건 · 관련도순
When the user wants to edit, review, or improve existing marketing copy — 'edit this copy,' 'proofread,' 'polish this,' 'tighten this up,' 'too wordy,' 'sharpen the messaging.' Use when copy exists and needs improving, not rewriting from scratch. For writing new copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Brand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and operate Python Azure IoT Edge modules with robust messaging, deployment manifests, observability, and production readiness checks. Use when writing, deploying, or hardening a Python module for Azure IoT Edge, including telemetry filtering and offline retries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs. Use when preparing investor updates, all-hands presentations, board communications, recruiting narratives, crisis communications, or when user mentions company narrative, messaging consistency, storytelling, all-hands, investor update, or crisis communication.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Package an AI skill, prompt workflow, or internal operating habit into a public-ready release with a catchy hook, safe redaction, useful examples, demo tasks, README copy, and launch messaging. Use when preparing a skill for GitHub, social sharing, marketplace submission, documentation, or community feedback.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run initial NanoClaw setup. Use when user wants to install dependencies, authenticate messaging channels, register their main channel, or start the background services. Triggers on "setup", "install", "configure nanoclaw", or first-time setup requests.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts, and messaging
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turns a campaign idea, its objectives and the supporting notes (audience material, offer facts, budget and dates, channel list) into one DRAFT one-page campaign brief: objectives, audience, one single-minded message with sourced proof points, channels and timeline, success measures with baselines, mandatories, risks and numbered open questions for the campaign owner. Use when the user asks to "write a campaign brief", "draft a creative brief for this launch", "turn this idea into a one-page brief", "tighten this brief to one page" or "build the marketing brief from these notes". Do not use for a message house, messaging pillars or a launch narrative on its own, use message-house-builder instead; for laying the campaign onto dated slots, use content-calendar-planner. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or product plan in character as a Chief Product Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, product and adoption risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CPO review", "pressure-test this product plan", "what would a CPO say about this", "challenge the user evidence" or "check the roadmap opportunity cost". Do not use for positioning, messaging or launch marketing, use cmo-reviewer instead; for internal staff adoption of a rollout, use frontline-skeptic-reviewer; for what a change asks of paying customers, use customer-advocate-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a proposal, business case, deck or plan in character as a Chief Marketing Officer archetype and returns a DRAFT review in the chat with a verdict, findings cited to specific passages, marketing risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CMO review", "pressure-test the positioning", "what would a CMO say about this", "challenge the launch plan" or "check the messaging and audience". Do not use for price economics, margins or payback, use cfo-reviewer instead; for sales pipeline mechanics, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
- Investigate a phone number — E.164 normalisation with libphonenumber, phoneinfoga scanning, carrier and line-type identification, VoIP and burner detection, messaging-app registration checks, and reverse-lookup and caller-ID sources.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging. Use when starting work with a new brand or customer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Recover a fleet whose machines cannot see each other over the file-sync network: establish ground truth at the hub from the live sync API rather than memory or one peer's claim, publish the hub's verified device id over the messaging rail, and walk each disconnected peer through re-pairing. Triggers: "/raise-sync", "sync is down", "machines cannot see each other".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Load for reliable post-commit messaging, domain/integration event delivery, transactional outbox tables, dispatch workers, retries, idempotent consumers, duplicate delivery, or dual-write failure; not for synchronous in-process events with no external side effect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "map what our surfaces say today", "inventory our current messaging", or "find the gap between what we say and what we mean"; produces the narrative baseline — a surface-by-surface inventory of what every owned touchpoint (homepage, pricing, docs, decks, social bios, email footers) claims RIGHT NOW, each line labeled Measured / User-provided / Estimated, plus a per-surface gap read vs the intended message and the drift-baseline snapshot the Evaluate phase measures future drift against. Not for authoring the canon — use message-system-architect; not for scoring the surfaces or running the vetoes — use narrative-quality-auditor. 现状叙事盘点/各触点口径/意图差距/漂移基线
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "test our messaging before we scale it", "design a message-market-fit panel", or "run a 5-second comprehension test on our new tagline"; produces a message-test design spec — hypothesis, panel and recruit criteria, comprehension / 5-second / message-market-fit (Wynter-style) protocols, stimulus set drawn from the canon, success thresholds, and a stop/revise decision rule — for the TALE Evaluate phase so the message is validated before any paid scale. It designs the test; it never runs the experiment or adjudicates a claim. Not for running the panel or A/B experiment — use send-experiment-designer or ad-test-designer; not for analyzing the results — use performance-analyzer; not for authoring the message itself — use message-system-architect. 消息测试/理解度测试/面板设计/五秒测试/消息市场契合
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "map the category narrative", "tear down how competitors tell their story", or "find the language conventions in our market"; produces a category narrative map — the dominant stories and points of view in the category, its language conventions and framing clichés, and a per-competitor narrative teardown (arc, claimed onlyness, proof pattern) plus how each rival's messaging has shifted over time (scraped copy vs archived copy). Not for the positioning canvas itself — use positioning-mapper; not for the beachhead's beliefs and objections — use audience-belief-mapper; not for SERP keyword targeting — use keyword-research; not for claim adjudication — use offer-claims-registry. 品类叙事/竞争叙事拆解/语言惯例/叙事演变
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update a reusable product marketing context document with positioning, audience, ICP, use cases, and messaging. Use at the start of a project to avoid repeating core marketing context across tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Best practices and guidelines for Apache Kafka event streaming and distributed messaging
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.