「action」の検索結果

Deploy and use the Exasol Text AI Extension (TXAIE) with notebook-connector. Covers `deploy_license`, `initialize_text_ai_extension`, the `PYTHON3_TXAIE` language container, the Extraction API classes `StandardExtractor`, `NamedEntityExtractor`, `TopicClassifierExtractor`, `PipelineExtractor`, and `BranchExtractor`, named-entity, zero-shot classification, and feature extraction runs, default-model installation, and result-table querying such as `TXAIE_AUDIT_LOG`.

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

Verify Rash Studio scenes, ActionScript subset behavior, resource links, portable embeds, exports, and desktop or mobile interaction. Use for Rash acceptance checks, compatibility review, security review, or release validation.

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

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

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

Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.

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

Azure AI Content Understanding SDK for Python. Use for multimodal content extraction from documents, images, audio, and video. Triggers: "azure-ai-contentunderstanding", "ContentUnderstandingClient", "multimodal analysis", "document extraction", "video analysis", "audio transcription".

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

Detect model stealing, model inversion, and membership inference performed through inference-API abuse by monitoring query patterns, applying output perturbation, and red-teaming your own model's extractability.

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

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

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

Solana development patterns used in the Pump SDK — Anchor IDL-based program interaction, SPL Token and Token-2022 management, transaction construction with instruction composition, RPC batching, and cross-program coordination.

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

Nix + flake-parts 開発環境の構築パターン: root flake.nix（成果物）+ dev/flake.nix（devShell + CI シェル）を direnv で読み込む構成、および GitHub Actions CI テンプレートを提供する。このスキルは /nix-devenv と明示的に呼び出されたときのみ使用する。キーワードマッチによる自動起動はしない。

システムログを分析してエラーの根本原因を特定し、段階的に深堀りしていくデバッグ専門家スキル。 アプリケーションログ、システムログ、クラウドサービスログなど様々な形式に対応。 5 Whys、タイムライン分析、Fishbone分析などのRCA（根本原因分析）手法を用いて 問題の本質を突き止め、再発防止策まで提案する。 Use when analyzing system logs to find error root causes, debugging application issues, or performing technical post-mortem analysis with log data. For organizational incident management processes (post-incident review, corrective action plans, incident reports without log data), use incident-rca-specialist instead. Triggers: "analyze this log", "find the root cause", "debug this error", "why is this failing", "log analysis", "what caused this crash", "troubleshoot this issue"

M&Aアドバイザリー支援スキル。デューデリジェンス（DD）実施、企業価値評価（バリュエーション）、 シナジー分析、PMI（Post Merger Integration）計画策定を包括的に支援。 Use when conducting M&A due diligence (Financial, Legal, IT, HR), company valuation (DCF, Comparable Companies, Precedent Transactions), synergy analysis, or post-merger integration planning. Triggers: "M&A", "デューデリジェンス", "DD", "バリュエーション", "企業価値評価", "DCF", "comparable", "類似企業", "先行取引", "PMI", "統合計画", "シナジー分析", "買収", "合併"

Generate strategic-consultant-grade meeting minutes from transcripts or notes in Japanese OR English (matching the source language), then run a self-review loop (max 3 iterations) that checks for internal contradictions, action-item omissions, speaker-name errors, and date/day-of-week mistakes before reporting completion. Use this skill whenever the user asks to draft meeting minutes, summarize a transcript, or document a meeting discussion — including Japanese-language transcripts (議事録 / 会議メモ / 文字起こし) and English-language transcripts.

Prepare comprehensive meeting assets including agendas, reference materials, decision logs, and action items. Use when user says "prepare meeting", "create agenda", "meeting prep", "会議準備", or needs bilingual (Japanese/English) meeting documentation for cross-regional teams. Triggers include requests for decision log templates, action item tracking, or compiling reference materials from project estimates and specs.

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

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.

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

ego-browser (ego-lite) is a Chromium-based browser that gives AI agents a CLI-accessible Node.js runtime for driving a real browser. Use this skill whenever the user needs to interact with a website opening pages, filling forms, clicking buttons, taking screenshots, extracting page data, testing web apps, logging into sites, automating browser operations, or any other browser automation task. Triggers include requests to "open a website", "visit a URL", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "extract content from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also used for exploratory testing, dogfooding, QA, bug hunting, or reviewing app quality. Prefer ego-browser over any built-in browser automation, web fetch, or other web tools.

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

METAINFORMANT rules for directory src/metainformant/pharmacogenomics/interaction. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

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

METAINFORMANT rules for directory src/metainformant/networks/interaction. Use when editing, adding tests, or reviewing code under this path. Read the linked AGENTS.md first; use uv only, write outputs to output/, real implementations.

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

Review secret handling, brokered execution, redaction, vault boundaries, host approval, and public hygiene.

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

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.

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

Prepares a DRAFT internal audit pack from the audit plan: scope as stated, criteria with clauses quoted from the documents provided, document requests per auditee with due dates, open interview questions per process and role, previous findings to follow up and a readiness checklist. Never pre-judges conformity, writes findings or selects the sample; the lead auditor decides. Use when the user asks to "prepare the internal audit", "build the audit pack from this plan", "draft the document requests and interview questions" or "get us ready for the supplier audit". Do not use for evidence requests built from a control list, use control-evidence-request-pack instead; to chase actions from earlier audits, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Reads a risk register together with meeting notes and incident reports and returns a draft update pack: existing risks whose exposure, controls, ownership or status the sources say have changed, new risk candidates, closure candidates, and the one owner decision each item needs. Never assigns or changes a likelihood, impact, score or colour and never edits the register; owners decide. Use when the user asks to "update the risk register from these minutes", "refresh the register with the incidents since the last review", "reconcile the register against the notes" or "what changed on our risks". Do not use for writing up an incident itself, use incident-postmortem-drafter or data-incident-impact-brief instead; to track actions from minutes, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Drafts a nonconformance report from inspection notes, test results and the governing specification or procedure: what was observed, where, the evidence with references, the requirement cited quoted verbatim with the departure from it, and containment proposals for the quality lead to decide. Never classifies severity, dispositions the item, names a root cause or closes the report. Use when the user asks to "write up this nonconformance", "draft an NCR from my inspection notes", "formalise this deviation" or "turn this snag into a defect report". Do not use for tracking the actions an NCR raises, use corrective-action-tracker instead. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT month-end, quarter-end or year-end close checklist and status table for a finance team from the close calendar, the open items list and last month's close issues that the user attaches, pastes or the agent can reach, marks every task on time, due, late, at risk or blocked, and flags dependency chains and repeat issues. Use when the user asks to "build the close checklist", "where are we on the month-end close", "what is late or blocked in the close", "refresh the close tracker as of today" or "prepare the close status note". Do not use for a project tracker or weekly project status, use project-status-tracker instead; for corrective actions from audits or NCRs, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Turns process notes, a walkthrough or interview transcript, a transcript of a meeting recording or a stale existing procedure into a draft standard operating procedure: purpose and trigger, scope, definitions, roles with a RACI table, numbered steps with the check that closes each one, records produced, controls as stated, and open questions for the process owner. Every step traces to the source or reads UNKNOWN. Use when the user asks to "write an SOP from these notes", "turn this walkthrough into a procedure", "document how we do this", "draft the standard operating procedure for", "build a RACI for this process" or "tidy up this old procedure". Do not use for technical runbooks with commands and rollback, use runbook-drafter instead; for meeting minutes and action lists, use transcript-to-actions. Drafts for human review; never approves, authorises or signs off.

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