2,224 件 ・ 関連度順
概要と使いどころ
Analyze email threads to extract current status, pending actions, timeline of events, and identify stale/outdated information. Use when asked to summarize email conversations, find outstanding action items in email chains, or detect when a thread summary is out of date.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when creating executive-level briefing materials, board reports, management meeting presentations, or investor briefings. This skill provides the "So What? / Why Now? / What Next?" framework, data visualization guidelines optimized for executives, and professional templates for rapid document creation. Triggers include "create board report", "executive summary", "management meeting materials", "investor presentation", "one-page summary", or requests to communicate complex information to senior leadership.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, testing, or updating active-recall flashcards grounded in session concepts to reinforce retention.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, implementing, or validating UI/UX and frontend experiences for web, mobile, responsive apps, design systems, Figma-to-code handoff, frontend stack/library selection, personas, UX mapping, information architecture, UI patterns, accessibility, interaction design, UX research, usability testing, theme/token application, or XR/spatial interfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
日本語の概要は準備中です。原文の説明を表示しています。
Load when asked to create, update, re-baseline, or continue a repository-grounded implementation/technical/refactor plan and its `dev/active/<task>` plan/context/tasks files; not for a product PRD, informal advice, or reviewing an already-written plan.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NIST SP 800-171 Rev. 3 (Protecting CUI in Nonfederal Systems). Use for CUI confidentiality requirements on contractors and other nonfederal organizations, the 17 requirement families, ODPs, SSPs, POA&Ms, and tailoring from SP 800-53. Covers 800-171r3 only; does not replace SP 800-171A assessment procedures, full SP 800-53 baselines, CMMC scoring mechanics, or classified-information controls.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NIST SP 800-37 Revision 2, the Risk Management Framework (RMF) for information systems and organizations. Use for the seven RMF steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) and their tasks; the three-tier organization-wide risk model; authorization boundaries; the requirements-to-controls relationship; security categorization (FIPS 199/200 high-water mark) and control selection/tailoring (SP 800-53/53B baselines); assessment, the authorization decision and risk acceptance, continuous monitoring and ongoing authorization; the security/privacy distinction; and supply chain risk management. This is the security-and-privacy-risk-governance edge of systems engineering — it governs how much protection and whether to accept residual risk, complementing the disciplines that decide how protection is built. Does NOT reproduce the SP 800-53 control catalog or its baselines, the FIPS impact tables, or the ISO/IEC/IEEE 15288 process text; it names and routes to them rather than restating them.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NASA System Safety Handbook Volume 2 (NASA/SP-2014-612). Use for risk-informed safety cases (RISC), integrated safety analysis (ISA), adequate safety concepts, safety objectives and requirements, acquirer/provider roles, graded safety analysis, claims-evidence-argument structure, SSMP development, and RISC evaluation. Does not cover nuclear or chemical safety domains, occupational health regulations, or NASA-specific programmatic requirements beyond system safety.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from DoD Architecture Framework (DoDAF) 2.02 — Volume II: Architectural Data and Models. Use for DoDAF viewpoints, DM2 meta-model, capability modeling, operational architecture, systems architecture, services architecture, data/information modeling, standards compliance, project/portfolio integration, and fit-for-purpose model selection. Does not cover DoDAF Volume I (policy/governance) or Volume III (enterprise-level guidance); also does not substitute for the live DISR or DARS registries.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NASA Risk Management Handbook (NASA/SP-2011-3422). Use for risk-informed decision making, continuous risk management, performance commitments, risk scenario diagrams, risk disposition types, risk burn-down schedules, objectives hierarchies, deliberation and alternative selection, risk driver identification, and RM planning for space and safety-critical programmes. Does not cover domain-specific PRA methods (fault trees, event trees) in procedural depth — see NASA PRA Procedures Guide for those.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from MIL-STD-40051-2C (15 Dec 2015), Preparation of Digital Technical Information for Page-Based Technical Manuals. Use for TM/TDP structure, work packages, front/back matter, style/format, warnings/HAZMAT, change packages, content selection matrices, and plate exemplars. Primary Training & Documentation pack (cluster 25) with Ops & Maintenance procedure use—page-based (-2C) only, not IETM 40051-1.
日本語の概要は準備中です。原文の説明を表示しています。
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 DOE Order on Program and Project Management for the Acquisition of Capital Assets (DOE O 413.3 series). Use for Critical Decisions CD-0–CD-4, performance baselines, acquisition strategy and IPTs, cost/schedule/EVMS/PARS controls, risk-informed governance, reviews, and contractor requirements. Built from O 413.3C (2026-08-05), which cancels O 413.3B Chg 7 (2023-06-21); does not replace site-specific procedures, nuclear safety rules detail, or full estimating standards.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems — the avionics/medical slant — via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from NASA-STD-7009B (Standard for Models and Simulations) with implementation depth from NASA-HDBK-7009B. Use for M&S criticality and programmatics, development evidence and capability assessment, verification/validation domains, uncertainty and sensitivity, use-phase results assessment, risk-informed decision reporting, and handbook life-cycle products. Covers STD-7009B (2024-03-05) + HDBK-7009B (2026-02-03) synthesized notes only; does not replace program-specific TA direction, NPR 7150.2 software requirements detail, or full PRA methodology.
日本語の概要は準備中です。原文の説明を表示しています。
Knowledge base from the DoD M&S VV&A Recommended Practices Guide (RPG web edition). Use for verification, validation, and accreditation of models and simulations — role responsibilities (user, developer, M&S PM, V&V agent, accreditation agent), fidelity, validation fundamentals, data V&V, risk-informed accreditation, T&E/V&V integration, referent development, and conceptual-model validation. Complements nasa-ms-7009 and T&E packs; does not replace DoDI 5000.61 or Service VV&A policies.
日本語の概要は準備中です。原文の説明を表示しています。
Análisis de requisitos de documentos: Analiza los documentos de concepto y requisitos en la carpeta docs/, verifica los requisitos con el código actual y crea un informe de diferencias consolidado.
日本語の概要は準備中です。原文の説明を表示しています。
Erkennt Nutzeraufträge der Form "hole aus einem Ordner immer bestimmte Dateien und sammle sie an einem Ziel" und richtet dafür das Modul file-collect-sort-action (CLI fcsa) ein — ein konfigurationsgetriebener Agent, der Ordner scannt, Dateien per Schablone kategorisiert und gestufte Aktionen anwendet (move/copy/duplicate-check/delete/OCR/place-information). Nutze diesen Skill bei Sätzen wie "hole aus <Ordner> immer <Dateiart> und sammle sie in <Ziel>", "sortiere den Ordner X automatisch nach ...", "sammle eingehende Dateien aus ... in ...", "räume diesen Ordner regelbasiert auf" oder "verschiebe alle <Dateiart> aus <Ordner> automatisch". Richtet IMMER zuerst einen Dry-Run ein und schaltet erst nach ausdrücklichem Nutzer-Go scharf; Löschen bleibt grundsätzlich im _trash-Modus.
日本語の概要は準備中です。原文の説明を表示しています。
Protocolo sistemático de depuración en 6 fases. Enfoque estructurado ante errores con verificaciones rápidas, pruebas aisladas, regla de los 20 minutos y plantilla de informe de errores.
日本語の概要は準備中です。原文の説明を表示しています。
Metakognitive Injektoren und Selbstgesprächs-Strategien (Self-Talk, Metacognitive Auditing, Evaluator Hooks, Pre-Flight Checklists, State Persistence & Personas). Integriert Aktive Informationssuche (Systemgedächtnis Gardener & USMC), Rehearsal (Aktives Abrufen & Wiedergeben), Baddeleys Arbeitsgedächtnis (State + Hooks), Miyake Exekutivfunktionen sowie CBT/ACT therapeutische Strategien.
日本語の概要は準備中です。原文の説明を表示しています。
Ordnet freiwillig bereitgestellte Gesundheitsinformationen und bereitet Fragen für Fachpersonen vor.
日本語の概要は準備中です。原文の説明を表示しています。
Turns plain-language requests (emails, chat messages, form submissions, meeting asks, voicemail or call notes) into one intake record per request (what is asked, who asks and for whom, urgency as evidenced, category, suggested owner, missing information with draft clarifying questions) and a triage table sorted for the operations lead to act on. Use when the user asks to "log these requests", "triage this pile of asks", "turn this message into an intake record", "who should own this request", "what is missing before we can start" or "build today's intake list". Do not use for customer support tickets, use ticket-triage-pack instead; for clearing a personal mailbox by reply bucket, use inbox-triage. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Prepares a DRAFT management-of-change intake record from a change description (email, meeting note, marked-up drawing or request form): what changes from what to what and where, the identifiers named, the candidate affected documents matched against the register, the disciplines to consult with the reason for each, and the numbered questions reviewers must answer, with UNKNOWN wherever the description is silent. Prepares the record only: never approves, classifies the change, decides replacement in kind or makes any hazard or safety judgement. Use when the user asks to "raise an MoC for this", "prepare the change request intake", "which documents does this change touch", "who needs to review this change" or "draft the MoC form from this email". Do not use for tracking who owes information to whom across disciplines, use interface-register-builder instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。