766 件 ・ 関連度順
概要と使いどころ
当用户问怎么真诚沟通/拒绝别人/给反馈/不想说场面话、或发现自己在隐瞒时调用。 核心理念: 撒谎会先骗到自己(费曼: 你最容易愚弄的人是你); 彻底诚实=所想与所说一致; 具体表扬、一般批评; 秘密越少快乐越多。 不适用于: 需要外交辞令的谈判策略(可以诚实但不必全说)。 Triggers: 诚实/沟通/拒绝/批评/表扬/秘密/场面话/honesty/communication/feedback
日本語の概要は準備中です。原文の説明を表示しています。
Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining legacy code.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
日本語の概要は準備中です。原文の説明を表示しています。
Create child communication safety experiences using PermissionKit to request parental permission for children. Use when building apps that involve child-to-contact communication, need to check communication limits, request parent/guardian approval, or handle permission responses for minors.
日本語の概要は準備中です。原文の説明を表示しています。
Stakeholder mapping, communication plan design, reporting hierarchy, and mid-matter comms updates. Use when setting up a new matter and needing to identify who needs what information, designing the communication rhythm, building reporting structures for multi-jurisdiction programmes, or updating the comms plan when the stakeholder landscape changes. Trigger on: 'stakeholder map', 'who needs to be kept informed', 'communication plan', 'reporting structure', 'who do we report to', 'how often do we meet', 'client wants more updates', 'new contact on the client side', 'build the comms plan', 'reporting hierarchy', 'HQ vs regions', 'who is the decision maker', 'comms rhythm', 'meeting cadence', 'status call schedule'.
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Communication Services development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when building ACS calling, chat, SMS, email, Teams interop, or PSTN/Direct Routing solutions, and other Azure Communication Services related development tasks. Not for Azure Notification Hubs (use azure-notification-hubs), Azure SignalR Service (use azure-signalr-service), Azure Web PubSub (use azure-web-pubsub), Azure AI Bot Service (use azure-bot-service).
日本語の概要は準備中です。原文の説明を表示しています。
Use ManagedCode.Communication when a .NET application needs explicit result objects, structured errors, and predictable service or API boundaries instead of exception-driven control flow. USE FOR: integrating ManagedCode.Communication into services or APIs; replacing exception-driven result handling with explicit results; reviewing service boundaries that return. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.
日本語の概要は準備中です。原文の説明を表示しています。
Infer and visualize intercellular communication from scRNA-seq with CellChat (R). Build CellChat from Seurat/counts → subset CellChatDB ligand-receptor pairs → over-expressed genes per group → communication probabilities → pathway signaling → network centrality (senders/receivers/influencers) → chord/heatmap/bubble plots → cross-condition compare. Human, mouse. Use liana for pure-Python.
日本語の概要は準備中です。原文の説明を表示しています。
Manages direct communication to affected data subjects following a personal data breach under GDPR Article 34 when the breach is likely to result in a high risk to their rights and freedoms. Covers the high risk threshold, required notification content per Art. 34(2), exemptions under Art. 34(3), and breach notification letter templates for five scenarios. Keywords: data subject notification, Article 34, high risk, breach communication, GDPR.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert Communications Engineer. Use when a task calls for Communications Engineer judgment. Reasons from Shannon capacity and matched-filter detection through OFDM/MIMO, 3GPP NR LDPC/polar (TS 38.212), TR 38.901 link budgets, Keysight 89600 VSA EVM, ns-3 SLS, and berconfint Monte Carlo while treating CFO/IQ/phase-noise coupling, pre- vs post-FEC BER, and AWGN-only optimism as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
The craft of communicating technical concepts clearly to developers. Developer communications isn't marketing—it's about building trust through transparency, accuracy, and genuine utility. The best devrel content helps developers solve real problems. This skill covers technical documentation, developer tutorials, API references, changelog writing, developer blog posts, and developer community engagement. Great developer communications treats developers as peers, not leads to convert. Use when "documentation, docs, tutorial, getting started, API reference, changelog, release notes, developer guide, devrel, developer relations, code examples, SDK docs, README, documentation, devrel, tutorials, api-docs, developer-experience, technical-writing, getting-started, changelogs" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
The craft of producing creative assets that communicate brand, product, and message effectively. Creative communications bridges strategy and execution—translating brand positioning and marketing goals into visual, audio, and interactive experiences that resonate with audiences. This skill covers creative briefing, creative production workflows, asset creation, creative feedback, and cross-channel creative adaptation. Great creative communications amplifies strategy; it doesn't replace it. Use when "creative, creative brief, assets, video, motion, animation, creative production, photoshoot, visual content, creative review, ad creative, creative feedback, creative, production, video, motion, assets, briefs, feedback, visual-content" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
CEO (Chief Executive Officer) — 一家公司「最高操作员」的工艺, 与泛泛「领导力 / 管理学」不同: (a) 设定战略与凝结愿景 (Drucker 的「企业的经营理论」+ Porter 论定位 + Hamilton Helmer 的「七力」+ Andy Grove 的「战略转折点」+ Roger Martin 《Playing to Win》); (b) 资本配置是 CEO 单一最高杠杆的工作 (Buffett/Munger Berkshire 致股东信 + William Thorndike 《The Outsiders 商界局外人》论 8 位非常规 CEO + Michael Mauboussin 论 hurdle rate + Bezos 年度致股东信「invariants vs bets」+ Mark Leonard Constellation Software); (c) 组建与领导高管班子 (Patrick Lencioni 《团队的五大障碍》+ Ben Horowitz 《艰难的事》+ Reed Hastings 《No Rules Rules》人才密度 + Andy Grove HOP《高产出管理》+ Lou Gerstner IBM 转型 + Marshall Goldsmith); (d) 董事会与投资人关系 (Larcker & Tayan 《公司治理重要》+ Bill George 《True North》+ 正式 CEO-董事长 / CEO-独立董事 protocol + 维权投资人 playbook + 资本市场沟通); (e) 企业文化与价值观作为操作系统 (Netflix 文化手册 + Amazon Leadership Principles + Bridgewater 《Principles》Ray Dalio + Schein 论组织文化 + 任正非 灰度 + 张瑞敏 人单合一 + 稻盛和夫 阿米巴); (f) 高不确定下的高风险决策 (Bezos Type 1/Type 2 决策 + premortem Klein + Kahneman 论 executive bias + RAPID/DACI + base rates + 情景规划 + 反思 premortem); (g) 对内对外沟通 (创始人 / CEO 致股东信作为机构构建工具: Bezos / Buffett / Reed Hastings 备忘录 / 任正非 内部讲话 + Town Hall + 危机沟通 Tylenol/Boeing/Wells Fargo + 应对维权投资人); (h) 跨阶段规模化 (创业 0→1 / 扩张 1→100 / 成熟期掌舵 / 危机转型): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde + Lou Gerstner 转型; (i) 创始人 CEO vs 职业经理人 CEO 的差异 (Paul Graham 「Founder Mode」2024 + Brian Chesky + Reed Hastings (创始人→职业过渡) + BCG/McKinsey 的「manager mode」+ 两者各自代价 + 什么时候切换)。诚实处理: 幸存者偏差 (单个 CEO 的打法 ≠ 普适规律, 学术研究显示 CEO 个人方差约 ⅓, 约 70% 来自行业 / 时代 / 运气 / 资本结构), 创始人崇拜, 区分可复制工艺与不可移植个人魅力, 治理与利益相关者责任 (员工 / 股东 / 社会), 反对 CEO 神话与 Welch 退休金扭曲 / Theranos / WeWork / FTX / Uber-Kalanick 时代 / Musk 80h+ / 996 工时崇拜。覆盖 founder-CEO (Bezos/Hastings/黄仁勋/Chesky/Brin/任正非) 与职业 CEO (Nadella/Gerstner/Pichai/Mulally/Lafley)。不含: 泛泛管理理论 (商业书已覆盖, 本 skill 专谈 C-suite 这个具体岗位), 不含: 「领导力」作为个人成长自助 (Robbins/Tracy/Maxwell 励志体裁), 不含: 「如何创业」早期战术 — 一旦有员工 / 董事会 / 资本, CEO 的工艺才开始。 (CEO (Chief Executive Officer) — the craft of being the top operator of a company, distinct from generic 'leadership/management': (a) setting the strategy and crystallizing the vision (Drucker's 'theory of the business' + Porter on positioning + Hamilton Helmer's 7 powers + Andy Grove's strategic inflection points + Roger Martin Playing to Win); (b) capital allocation as the CEO's single highest-leverage job (Buffett/Munger Berkshire letters + William Thorndike 'The Outsiders' on 8 unconventional CEOs + Michael Mauboussin on hurdle rates + Bezos's annual shareholder letter approach to invariants vs bets + Mark Leonard Constellation Software); (c) building and leading the executive team (Patrick Lencioni 'Five Dysfunctions' + Ben Horowitz 'Hard Things About Hard Things' + Reed Hastings 'No Rules Rules' on talent density + Andy Grove HOP + Lou Gerstner IBM turnaround + Marshall Goldsmith); (d) board and investor relations (Larcker & Tayan 'Corporate Governance Matters' + Bill George 'True North' + the formal CEO-Chair / CEO-Lead Director protocols + activist investor playbooks + capital markets communication); (e) culture and values as operating system (Netflix culture deck + Amazon Leadership Principles + Bridgewater 'Principles' Ray Dalio + Schein on org culture + 任正非 Ren Zhengfei 灰度 + 张瑞敏 Zhang Ruimin 人单合一 + 稻盛和夫 阿米巴); (f) high-stakes decision-making under uncertainty (Bezos Type 1 vs Type 2 + premortem Klein + Kahneman 'Thinking Fast and Slow' for executive bias + RAPID/DACI + base rates + scenario planning + premortem); (g) internal and external communication (founder/CEO letters as institution-builders: Bezos shareholder letters / Buffett letters / Reed Hastings memos / 任正非 内部讲话 + Town Halls + crisis communication Tylenol/Boeing/Wells Fargo + activist responses); (h) cross-stage scaling (founder-CEO of 0→1 / scaling 1→100 / mature-stage stewardship / turnaround): Steve Blank + Brian Chesky founder-mode + Marc Andreessen + Pierre Lassonde mining vs steady-state + Lou Gerstner turnaround; (i) the founder-CEO vs professional-manager-CEO distinction (Paul Graham 'Founder Mod
日本語の概要は準備中です。原文の説明を表示しています。
Pragmatics and communicative competence across languages -- speech acts (Austin/Searle), Grice's conversational maxims and implicature, politeness theory (Brown & Levinson), face-threatening acts, discourse structure, turn-taking, repair strategies, register and formality, cross-cultural communication, communicative strategies (circumlocution, approximation, appeal for assistance), and the gap between grammatical competence and communicative performance. Use when teaching communication skills, analyzing cross-cultural misunderstandings, building conversational fluency, or understanding why grammatically correct sentences can be pragmatically inappropriate.
日本語の概要は準備中です。原文の説明を表示しています。
Specialized prompt-building methodology for content and communications tasks. Provides 11 tested approaches (3 identity, 4 reasoning, 4 output) for writing, editing, content strategy, copywriting, audience analysis, editorial evaluation, cross-channel adaptation, and persuasion design. Use when building a Claude prompt or system prompt for content creation, editorial workflows, or communications tasks. Trigger on: "build a prompt for writing," "prompt for content strategy," "prompt for copywriting," "prompt for blog posts," "prompt for email sequences," "system prompt for editorial," "prompt for messaging framework," "content brief prompt," "prompt for audience analysis," "prompt that produces better content." Do NOT use for writing content directly — this Skill builds prompts that produce better content. Do NOT use for evaluating or scoring existing prompts — use rootnode-prompt-validation if available. Do NOT use for general prompt compilation — use rootnode-prompt-compilation if available.
日本語の概要は準備中です。原文の説明を表示しています。
Guide a person in developing active listening skills. AI coaches receptive mindset preparation, full-presence attending, reflective paraphrasing, clarifying questioning, synthesis of understanding, and integration of insights into communication practice. Use when a person wants to improve communication, when someone keeps misunderstanding others or feels misunderstood, when preparing for a difficult conversation such as a feedback session or conflict resolution, or when a person notices they talk more than they listen.
日本語の概要は準備中です。原文の説明を表示しています。
AI relational calibration — reading and adapting to the specific person you are working with. Goes beyond user-intent alignment (solving the right problem) to genuine attunement (meeting the person where they are). Maps communication style, expertise depth, emotional register, and implicit preferences from conversational evidence. Use at the start of a new session, when communication feels mismatched, after receiving unexpected feedback, or when transitioning between very different users or contexts.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Public relations, corporate communications, and analyst relations for B2B SaaS. Use this skill for earned media and press strategy, announcements and press releases, executive and crisis communications, media relationships and briefings, and the Gartner/Forrester/IDC analyst program including Magic Quadrant and Wave evaluation submissions. Also triggers on: PR, public relations, press release, earned media, media relations, journalist, embargo, announcement, crisis comms, corporate communications, analyst relations, AR, Gartner, Forrester, IDC, Magic Quadrant, Forrester Wave, analyst briefing, inquiry, newsjacking, rapid response, should we comment on this news story, expert commentary, reactive comment, source request, Qwoted, is this newsworthy.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a task needs the judgment of a Communications Teacher, Postsecondary — designing or norming a multi-section basic public-speaking course, resolving a cross-rater grading discrepancy on a speech rubric, screening for and accommodating communication apprehension, or choosing a rhetorical-criticism method for a media-analysis assignment.
日本語の概要は準備中です。原文の説明を表示しています。
Configure Communications Cloud for the first time: org setup sequence, permission sets, Enterprise Product Catalog (EPC) service catalog, TM Forum-aligned order decomposition setup, Account record-type segmentation, contract lifecycle activation. NOT for designing the commercial-to-technical order process itself - use admin/industries-process-design. NOT for calling TM Forum Open APIs (TMF622, TMF679) - use omnistudio/industries-api-extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level communications engineering covering modulation, channel capacity, error correction, wireless systems, OFDM, MIMO, and 5G technologies.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
日本語の概要は準備中です。原文の説明を表示しています。