「reporting」の検索結果

Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

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

Validates predictive models on omics and biomedical data with nested cross-validation, group/batch/temporal-aware splits, the full data-leakage taxonomy, probability calibration, decision-curve net benefit, optimism correction, sample-size planning, and TRIPOD+AI reporting. Use when estimating model performance honestly, choosing a CV scheme, detecting leakage, or judging whether reported discrimination means the model is actually useful. For feature selection itself see machine-learning/biomarker-discovery; for confirmatory-trial inference see clinical-biostatistics/trial-reporting.

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

Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.

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

Use this skill when the user asks about Environmental Health & Safety (EHS) for trucking — fuel spill response, hazmat release reporting, EPA + state environmental reporting, emergency contact information (CHEMTREC), environmental impairment liability insurance, and how to handle a CMV-related environmental incident. Cite 40 CFR + 49 CFR 174.6.

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

Builds SOC performance metrics and KPI tracking dashboards measuring Mean Time to Detect (MTTD), Mean Time to Respond (MTTR), alert quality ratios, analyst productivity, and detection coverage using SIEM data. Use when SOC leadership needs operational visibility, continuous improvement tracking, or executive-level reporting on security operations effectiveness.

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

Implement a phishing report button in email clients with automated triage workflow that analyzes user-reported suspicious emails and provides feedback to reporters.

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

Automatically categorizes test failures, suggests responsible owners, and provides common fix checklists. Generates actionable test reports with failure analysis. Use for "test reporting", "failure triage", "test analysis", or "test automation".

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

Comprehensive red team operations methodology covering full engagement lifecycle from planning through reporting. Addresses engagement scoping and rules of engagement negotiation, multi-tier C2 infrastructure design with redirectors and domain fronting, malleable traffic profiles and beacon tradecraft, OPSEC discipline including attribution avoidance and indicator management, EDR and AMSI evasion techniques using direct syscalls and unhooking, data collection with chain-of-custody controls, and structured reporting with purple team debrief workflows. Covers assumed-breach, external-to-internal, insider threat, and hybrid physical-cyber engagement scenarios with MITRE ATT&CK mapping throughout. Targets operators planning or executing adversary simulation engagements against mature defenders.

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

Cross-cutting methodology for the CVE-hunting pipeline (ported from find-cve-agent): when a bug is design-vs-real, false-positive avoidance, version checking before reporting, responsible disclosure norms, acceptance-rate expectations per vuln class, vulnerability chaining playbook, known false-positive patterns, maintainer-response patterns, secure-pattern reference (what NOT to flag), and a self-criticism checklist to run before claiming a finding. Use this alongside the cve-hunter/cve-exploiter/cve-validator agents and the /cve-hunt pipeline — load it whenever judging if a finding is real, worth reporting, or already fixed.

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

OpenClawのテストやプラグイン検証の遅さ・メモリ使用量を計測し、読み込みや起動処理の原因を調査。テストの検証範囲を保ちながら改善し、前後の数値を比較します。

• 遅いテストや重い読み込みの原因調査
• プラグイン検証の時間とメモリ削減
• テスト中のメモリ増加を調べたいとき

運用者が設定したTeamサーバーの更新を、指定担当のNight Watchに引き継ぎ、既存の更新機構による検証・復旧・完了確認まで進めるスキル。

• Teamを公式mainへ更新したいとき
• 失敗・延期した更新の続行調整
• データベース移行と復旧の調整

ParallelsのmacOS仮想環境で、導入からDiscordへの送信、ホストの返信、ゲストでの読み取りまでを検証し、双方向通信の成否を確認するスキル。

• 新規macOS環境で送受信を確認したいとき
• アップグレード後の双方向通信確認
• Discord往復通信の失敗調査

現在のブランチの変更差分だけを点検し、冗長なコメントや不要な防御処理、型の強引な変換、周囲と合わない書き方を、動作を変えずレビュー前に整理するスキル。

• AI生成コードの冗長コメント整理
• 不要な防御処理や型変換の点検
• 変更箇所を周囲の書き方にそろえる

MCP設定を読み、承認後も取得するコードが変わり得るパッケージ参照を確認するスキル。サーバーを実行せず、npm・Python・Dockerの指定を分類します。

• MCP設定を承認前に確認したいとき
• latestタグや版の範囲指定の確認
• CIへの再現可能な設定チェックの追加

プロジェクト文書の整理依頼を適切な専門スキルへ振り分け、文書の役割、リンク、設計判断の索引、根拠への参照を、ファイルを変更せずに点検するスキルです。

• プロジェクト文書の整理手順を選びたいとき
• 既存文書の情報源を把握したいとき
• ローカルリンクと設計判断の索引の点検

AIエージェントが失敗や同じ操作を繰り返す原因を、エラーと実行状況から整理します。小さな復旧操作を試し、結果と根拠を引き継げる報告にまとめるスキルです。

• エージェントの連続失敗を診断したいとき
• 同じツール操作のループ調査
• 情報の蓄積による出力劣化の点検

工場やオフィスの電力・天然ガス調達を、料金体系、使用量、契約条件から検討するスキル。供給会社の比較、ピーク料金対策、再生可能エネルギー契約や予算作成を支援します。

• 複数拠点のエネルギー見積もり比較
• 料金プランとピーク料金の見直し
• 再生可能エネルギー契約・証書の評価

GitHubの公開ソフトウェアに不正な変更がないか、履歴やアーカイブを照合して調査します。削除された情報の回収を試み、侵害の手がかりと根拠付きの報告書をまとめます。

• 不審なコミットやビルド手順の調査
• 履歴から消えたコミットの回収調査
• 認証情報の漏えい経緯を調べたいとき

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

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

Create and maintain agent-authored Paperclip status cards, or compile a prose interest prompt into bounded CompanySearchQuery objects and write the first summary from the assigned Summarizer run.

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

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

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

Detect and classify telemetry anomalies on Cognitum Seed devices. Use when investigating a device that's reporting odd metrics, before approving a firmware canary advancement, or when triaging fleet-wide health alerts.

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

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear about us," "self-reported attribution," "dark social," or wants to instrument attribution themselves — "stitch my bookings to their source," "SavvyCal/Calendly attribution," "close the identify gap," "track conversions on a third-party domain," "first-party / self-hosted attribution." For event tracking setup and UTMs, see analytics. For ad-platform pixels/CAPI, see ads. For pipeline and CRM revenue reporting, see revops. For the AI-search attribution blind spot, see ai-seo.

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

Cherry Studio first-party tool and bundled-shell routing for general agents. For straightforward local work in shell-capable sessions, run JS/TS with `bun <file>` and one-off JS tools with `bun x`; run Python with `uv run [--with <pkg>] python` and one-off Python CLIs with `uvx`; search with `rg`. Load this guide before changing project dependencies, deciding whether a tool should be ephemeral or reusable, reading or converting local Office/PDF files, coordinating or delegating across Agent Sessions, or using Cherry-owned web/browser, knowledge, persistent memory, schedules/notifications, IM channels, image generation, artifact reporting, managed CLI, skill, or MCP-server-registration capabilities—even if the user names no tool. Consult it before shell/file workarounds; live tool schemas are authoritative.

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