「communication」の検索結果

Android device offensive security, forensic extraction, and mobile app exploitation. Use this whenever the user needs to: break into or bypass the lock screen of an Android phone, extract data from a seized Android device for evidence, analyze or reverse-engineer an APK to find vulnerabilities, intercept communications on an Android device, exploit Android apps via deeplinks, steal crypto wallets or app data, set up rogue WiFi to target a phone, or plan any mobile device investigation or penetration test. Also trigger when the user mentions Android forensics, mobile pentesting, law enforcement phone extraction, device exploitation, WhatsApp or Telegram extraction from a phone, Android app reversing, CVE research for Android, or needing a chain of custody for mobile evidence. Even if the user describes the scenario casually or in another language, if they need to gain access to or pull data from an Android phone, use this skill.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from FAA-HDBK-006D (2020), the FAA's System Reliability, Maintainability, and Availability (RMA) Handbook for National Airspace System (NAS) hardware and software. Use for RMA figures of merit (MTBF, MTBO, MTTR, the availability variants), the bathtub curve and probability distributions, the four-stage RMA lifecycle mapped to the FAA Acquisition Management System (AMS), the six-task RMA technical-management/acquisition process, service-thread criticality and the NAS-RD severity-to-target table, the RMA analysis toolbox (RBD, FMEA/FMECA, FTA, Ishikawa, Monte Carlo, Bayesian, FRACAS, ALT, reliability-growth/recovery tests), software reliability (early prediction + reliability growth), and tailorable example RMA requirements for a Program Requirements Document. Scope limits: it is FAA/NAS-specific guidance (not a requirement, by its own statement), centred on hardware-plus-software availability — it brackets out human/service/facility/communications availability, names but does not reproduce the math derivations or external standards (MIL-STDs, IEEE 1633, RTCA DO-178C/DO-278A, SAE JA1011), is thin on detailed worked numerical examples and on safety-case method, and predates any current revision beyond 006D.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the FAA Human Factors Design Standard (HF-STD-001B, 2016) — the FAA's consolidated human-factors / human-systems-integration design criteria for systems it manages, operates, or maintains. Use for requirement-level design rules on: general human-factors design principles; automation and function allocation; designing equipment for maintenance; displays, controls, and visual indicators; alarms, audio, and voice communications; the computer-human interface (information presentation, coding, interaction styles, windows, dialogue); keyboards, input devices, and workstation/workplace ergonomics; system security, personnel safety, environment, anthropometry, and user documentation; plus intended-use and tailoring guidance. It is a quantified, source-attributed synthesis (heavily citing MIL-STD-1472G, MIL-HDBK-759C, DOD-HFDG-ATCCS, NUREG-0700, NASA-STD-3000, ANSI, OSHA, ISO 9241). Complements nasa-hsi as a parallel HSI tradition from the civil-aviation domain. Scope limits: it is design criteria, NOT an HSI lifecycle/process model (use nasa-hsi, nasa-npr-7123, or dau-se-guidebook for process); it does NOT reproduce the third-party standards it cites; it is FAA-acquisition-oriented (ATC, towers, TRACONs, airway facilities), not a general consumer-UX guide; and it is thin on modern touchscreen/mobile, web, and AI-driven interface patterns and on quantitative human-reliability analysis.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the NASA Schedule Management Handbook (2024 edition, Revision 2). Use for program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication); the Integrated Master Schedule (IMS) and the WBS/OBS/CBS breakdown structures; the Schedule Management Plan (SMP) and Basis of Estimate (BoE); Critical Path Method, logic, durations, float and margin; tiered schedule assessment (Requirements/Health/Basis checks, the Shock Test) and the Dimensions of Schedule Reliability; Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo, correlation, merge bias, and the Joint Confidence Level (JCL); baselining, replan vs. rebaseline, EVM schedule metrics (SPI, BEI, CEI, HMI, Earned Schedule, CPLI), and status/progress/forecast reporting. This is NASA's scheduling doctrine grounded in NPR 7120.5 and the GAO Schedule Assessment Guide. Thin on the underlying mechanics of CPM, statistics, and EVM (it points to companion handbooks); aerospace/space-flight-centric; anchored to the 2024 second edition.

日本語の概要は準備中です。原文の説明を表示しています。

心理面接・カウンセリングコミュニケーションの基礎：アクティブ・リスニング（傾聴）、ミラーリング、パラフレーズ（言い換え）、オープンクエスチョン、ヴァリデーション（妥当化）。

Основы терапевтической коммуникации: активное слушание, эмоциональное отражение, парафразирование, открытые вопросы и валидация.

日本語の概要は準備中です。原文の説明を表示しています。

Fundamentos de la comunicación terapéutica: Escucha activa, reflejo, paráfrasis, preguntas abiertas y validación.

日本語の概要は準備中です。原文の説明を表示しています。

心理咨询与沟通基础：积极倾听、镜像反射、释义复述、开放式提问与情感确认。

日本語の概要は準備中です。原文の説明を表示しています。

Dach-Skill für Cloud-gestützte Kommunikationsprotokolle zwischen Agenten auf unterschiedlichen Maschinen (Ping-Pong, agent-beam, Listener und künftige Protokolle). Nutzen, wenn Arbeit über Maschinen hinweg per gemeinsamem Sync-Ordner oder Message-Yard koordiniert wird.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares a change request pack (description and justification, scope, schedule, implementation plan, risk as stated, rollback, test evidence as provided, communications, approvals route) from an engineer's notes, ticket or pull request description, with UNKNOWN for anything not provided and a question list for the engineer. Never rates risk or marks a change tested or approved. Use when the user asks to "write the change request for this", "fill in the change ticket from my notes", "prepare the CAB submission" or "turn this pull request into an RFC". Do not use for the step-by-step procedure with commands and rollback, use runbook-drafter instead; for release notes describing what shipped, use release-notes-writer. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Pre-tests one message (email, announcement, intranet post, town hall script, customer notice or slide) against two to six role personas the user supplies and returns a DRAFT panel report: each persona's likely first reaction, objections, unanswered questions, misreadings and what they would do next, every point tied to the passage that triggers it, plus suggested edits that add no fact the message does not already hold. Use when the user asks to "pre-test this message", "how will the team read this", "run this past the personas", "what objections will this raise", "find the holes before I send" or "check this lands with managers and field staff". Do not use for an in-character review of a proposal or business case by one executive archetype, use the executive-review family (cfo-reviewer, frontline-skeptic-reviewer and siblings) instead; to write the message in the first place, use announcement-drafter. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Drafts one internal or external announcement (email, intranet post, town hall script, customer notice or press statement) in the organisation's voice from the facts, audience, sender and style guide the user provides, with a fact trace, reader-questions check, pre-send checks and an approvals checklist left blank for the named approvers. Use when the user asks to "announce this change to all staff", "draft the customer notice", "write the town hall script", "prepare a holding statement" or "rewrite this in our voice". Do not use for a digest of several items, use internal-newsletter-drafter instead; to pre-test a drafted message against personas, use communication-pretest-panel. Drafts for human review; never approves, authorises or signs off.

日本語の概要は準備中です。原文の説明を表示しています。

Polish, restructure, or translate academic prose into Nature-leaning English using writing-strategy principles, curated Nature/Nature Communications article patterns, and phrase-level support from Academic Phrasebank. Use whenever the user asks to polish a manuscript paragraph, abstract, introduction, results, discussion, conclusion, title, methods section, or Chinese academic draft for publication-quality English. Also covers LaTeX layout/typesetting (排版) fixes — loose or sparse pages, stranded section headings, figures that don't fill the page or split across pages, "Float too large", multi-panel figure arrangement, and Supplementary Information that looks empty — via references/latex-layout.md. Also trigger on general academic/scientific writing requests even without the word "Nature", including academic writing, scientific writing, SCI/paper writing, English manuscript polishing, language editing, proofreading, and Chinese phrasings such as 学术写作、科研写作、论文润色、写paper、SCI写作、英文论文润色、语言润色、润色、改写、学术英语、英文写作.

日本語の概要は準備中です。原文の説明を表示しています。

Manage AI assistant configurations and peer-to-peer mesh network connections in the NV oOS Pro Toolkit. Covers assistant creation, model configuration, provider setup, peer discovery, mesh networking, and cross-assistant communication. Use when creating or editing AI assistants, configuring model providers, setting up peer connections, managing mesh network topology, or debugging assistant behavior.

日本語の概要は準備中です。原文の説明を表示しています。

Manage AI assistant configurations and peer-to-peer mesh network connections in the NV oOS Pro Toolkit. Covers assistant creation, model configuration, provider setup, peer discovery, mesh networking, cross-assistant communication, and detecting from a coding-agent session (Zed) which NV oOS assistants / MCP servers are enabled. Use when creating or editing AI assistants, configuring model providers, setting up peer connections, managing mesh network topology, debugging assistant behavior, or answering "is agent X available" / "what tools does this MCP have".

日本語の概要は準備中です。原文の説明を表示しています。

Memory management and FreeRTOS context for the Megahub ESP32 project. Use when dealing with heap allocation, stack size, task creation, inter-task communication, semaphores, queues, or any ESP32 memory constraints.

日本語の概要は準備中です。原文の説明を表示しています。

LEGO Powered Up protocol context for the Megahub project. Use when working on LEGO device communication, lpfuart library, UART parsing, motor control, sensor modes, device initialization, or debugging UART noise/corruption issues.

日本語の概要は準備中です。原文の説明を表示しています。

Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.

日本語の概要は準備中です。原文の説明を表示しています。

Expert in building Chrome Extensions using Manifest V3. Covers background scripts, service workers, content scripts, and cross-context communication.

日本語の概要は準備中です。原文の説明を表示しています。

Build real-time voice AI applications using Azure AI Voice Live SDK (azure-ai-voicelive). Use this skill when creating Python applications that need real-time bidirectional audio communication with...

日本語の概要は準備中です。原文の説明を表示しています。

Azure AI Voice Live SDK for JavaScript/TypeScript. Build real-time voice AI applications with bidirectional WebSocket communication.

日本語の概要は準備中です。原文の説明を表示しています。

Azure AI Voice Live SDK for .NET. Build real-time voice AI applications with bidirectional WebSocket communication.

日本語の概要は準備中です。原文の説明を表示しています。

Shape FriendlyBet Pundit content, bilingual product copy, community voice, share-card copy, social moments, video briefs, Hebrew/English wording, and group-chat friendly communication. Use when a task touches copy, Pundit tone, social videos, share text, community loops, or public-facing FriendlyBet voice.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Consul Connect — hashiCorp Consul Connect service mesh management covering service discovery, intentions, sidecar proxies, mesh gateways, ingress/terminating gateways, certificate management, and health checks. Use when managing Consul Connect mesh, configuring service-to-service authorization, debugging proxy connections, or managing mesh gateways for multi-datacenter communication.

日本語の概要は準備中です。原文の説明を表示しています。