Design incident response for AI system failures. TRIGGERS - Use when user needs help with ai-incident-response related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
4,136 件 ・ 関連度順
概要と使いどころ
Design incident response for AI system failures. TRIGGERS - Use when user needs help with ai-incident-response related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Sistema completo de due diligence para transacciones M&A en España. Abarca análisis jurídico (mercantil, regulatorio, compliance), fiscal (CIT, IVA, retenciones, facturación electrónica) y medioambiental (licencias, pasivos, responsabilidad). Incluye matrices de riesgo cuantitativas, workflows de ejecución, templates de informes y referencias normativas BOE/UE/ISO actualizadas. Úsalo cuando el usuario solicite due diligence en España, análisis de riesgos transaccionales, evaluación pre-adquisición o auditoría de cumplimiento normativo para share deals o asset deals.
日本語の概要は準備中です。原文の説明を表示しています。
Run the PageSpeed performance audit — 80/20 analysis of Core Web Vitals using the PageSpeed Insights API.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Boyd's OODA loop to navigate fast-moving, uncertain, or competitive situations — Observe what is actually happening, Orient through mental models and context, Decide on the clearest path, Act quickly, then loop again. Load when the situation is changing faster than the current plan, when a competitive response is needed, when the user is stuck in analysis paralysis in a dynamic environment, when shipping under uncertainty, or when deep-thinking diagnoses a fast-moving / competitive frame. Triggers on "what should we do right now", "the situation is changing", "how do we respond to this", "competitive response", "we need to move fast", or "we're stuck deciding". Based on John Boyd's OODA loop — Observe, Orient, Decide, Act — adapted for product and business contexts (OODA Canvas 2026).
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier (asset-based, brokerage, or 3PL) asks how to respond to a shipper RFP / RFQ — bid packaging, lane analysis, rate strategy, SOPs/SOWs, qualifications response, insurance compliance, EDI requirements, and how to win competitive bids without leaving margin on the table.
日本語の概要は準備中です。原文の説明を表示しています。
Generates ADR Responder classes for PHP 8.5. Creates HTTP response builders with PSR-7/PSR-17 support. Includes unit tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when importing Excel, CSV, or pasted rows with nuxt-ui-tools as a package consumer. Covers defineSpreadsheetSchema (typed context, chained text/number/date/boolean/select columns, columns depending on the columns above (options, defaults, rules per row), groups and dynamic groups built from the context, exact matching, option sources shared with forms, unknown-value policies, rules and levels, validate, row identity with duplicates and stored records, output), useSpreadsheetImport (headless models, onSubmit with batches and rejections), the UiSpreadsheetImport* parts, useSpreadsheetSteps with custom steps, and the ready-made UiSpreadsheetImport wizard.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze prompts and offer depth / token-budget options BEFORE answering. Use this skill when the user wants to control token usage, tune response depth, choose between short and long answers, or optimize their prompt. Triggers on: "tokens", "token budget", "depth", "consumption", "short vs long answer", "how many tokens", "save tokens", "answer at 50%", "give me the short version", "I want to control how much you use", "tune your response", "presupuesto de tokens", "profundidad", "responde al 50%", "dame la versión corta", or any equivalent phrasing in English or Spanish. If the user wants to control length, detail or depth -- even without mentioning tokens explicitly -- this skill applies.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a structured SOC incident response playbook for ransomware attacks covering detection, containment, eradication, and recovery phases with specific SIEM queries, isolation procedures, and decision trees. Use when SOC teams need formalized response procedures for ransomware incidents aligned to NIST SP 800-61 and MITRE ATT&CK ransomware techniques.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes UEFI bootkit persistence mechanisms including firmware implants in SPI flash, EFI System Partition (ESP) modifications, Secure Boot bypass techniques, and UEFI variable manipulation. Covers detection of known bootkit families (BlackLotus, LoJax, MosaicRegressor, MoonBounce, CosmicStrand), ESP partition forensic inspection, chipsec-based firmware integrity verification, and Secure Boot configuration auditing. Activates for requests involving UEFI malware analysis, firmware persistence investigation, boot chain integrity verification, or Secure Boot bypass detection.
日本語の概要は準備中です。原文の説明を表示しています。
Creates response procedures for security incidents with containment steps, communication templates, and evidence collection. Use for "incident response", "security playbook", "breach response", or "IR plan".
日本語の概要は準備中です。原文の説明を表示しています。
Extracts structured data from LLM responses using JSON schemas, Zod validation, and function calling for reliable parsing. Use when users request "structured output", "JSON extraction", "parse LLM response", "function calling", or "typed responses".
日本語の概要は準備中です。原文の説明を表示しています。
Implements responsive design systems with mobile-first breakpoints, container queries, fluid typography, and adaptive layouts using Tailwind CSS. Use when users request "responsive design", "mobile-first", "breakpoints", "fluid typography", or "adaptive layout".
日本語の概要は準備中です。原文の説明を表示しています。
Unifies API response patterns across endpoints including pagination format, error structure, status codes, response envelopes, and versioning strategy. Provides contract documentation, shared TypeScript types, middleware utilities, and migration plan. Use when standardizing "API contracts", "response formats", "API conventions", or "API consistency".
日本語の概要は準備中です。原文の説明を表示しています。
Deep-dive offensive methodology for dependency confusion and namespace attacks across all major package ecosystems. Covers npm scope confusion exploiting the gap between public and private scoped packages and .npmrc misconfigurations where registry mappings fail to pin internal scopes exclusively. Addresses PyPI namespace attacks through --extra-index-url resolution ordering, NuGet feed priority exploitation when multiple package sources are configured without clear directives, Maven and Gradle repository ordering where artifact resolution traverses repositories sequentially, Go module proxy abuse through GOPROXY misconfiguration, Ruby gems namespace squatting, and Docker image tag confusion with unqualified image references. Provides complete proof-of-concept methodology using safe callbacks including DNS canary via interactsh or Burp Collaborator and HTTP beacon with no destructive payload. Covers reconnaissance techniques for discovering internal package names through GitHub repository analysis, error ...
日本語の概要は準備中です。原文の説明を表示しています。
End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.
日本語の概要は準備中です。原文の説明を表示しています。
Practical incident-response runbook for a suspected or confirmed ComfyUI / GPU-daemon compromise. Triage, scope, contain, forensic collection, weight-integrity verification, rebuild from clean snapshot, postmortem. NOT for hygiene scans on a healthy box (use supply-chain-defense-for-ml-extensions), and NOT for runtime hardening of a fresh deployment (use gpu-hosted-asset-hardening).
日本語の概要は準備中です。原文の説明を表示しています。
OpenClawの脆弱性報告を、公開済みのバージョンと信頼範囲の根拠で確認し、終了・継続・影響の絞り込みを判断して、管理者向けの返信案をまとめます。
OpenClaw Control UIの画面変更を、状態別の比較ギャラリーと実ブラウザの操作テストで確認し、利用者のコメントや変更前後の画像を残すスキル。
OpenClawのモデル通信やツール実行の不具合を、ログと再現操作で切り分けるスキル。保存済みの会話や添付資料も調べ、原因の修正と再検証につなげます。
OpenClawにモデル提供サービスを追加し、実際の応答まで確認するスキル。認証情報は環境変数やファイルへの参照で扱い、設定の検証と結果報告も進めます。
コードレビューの指摘を実際のコードや対応環境と照らし合わせ、妥当性を確認します。不明点の整理、根拠を示した返答、修正ごとのテストまで進めるスキルです。
繰り返すLLMへのAPIリクエストで、共通の指示や資料を再利用しやすく並べるスキル。キャッシュ利用量と費用、応答時間を確認し、構成の見直しを支援します。
Node.js、Express、Next.jsのAPIとデータ処理を設計・見直すスキル。役割の分離、データベース最適化、キャッシュ、認証の実装例を示します。