「risk」の検索結果

Comprehensive market environment analysis and reporting tool. Analyzes global markets including US, European, Asian markets, forex, commodities, and economic indicators. Provides risk-on/risk-off assessment, sector analysis, and technical indicator interpretation. Triggers on keywords like market analysis, market environment, global markets, trading environment, market conditions, investment climate, market sentiment, forex analysis, stock market analysis, 相場環境, 市場分析, マーケット状況, 投資環境.

"Apply the Capital Asset Pricing Model (CAPM) to estimate expected returns and assess risk-return tradeoffs. Use this skill when the user needs to calculate expected return on an asset, interpret beta as systematic risk exposure, evaluate whether an investment compensates for risk, or when they ask 'what return should I expect', 'what is the risk premium', or 'how does beta affect pricing'.".

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

Drafts a BSA/AML Risk Assessment for U.S. financial institutions per FinCEN, FFIEC, and OCC standards. Evaluates inherent risks (customer, product, geographic, transaction, third-party), control adequacy, and residual risk. Use when preparing annual BSA compliance assessments, post-acquisition integration reviews, or when business changes trigger reassessment under 31 U.S.C. § 5318(h).

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

This skill guides evaluation of venous thromboembolism (VTE) risk factors in Cushing's syndrome patients to prevent thrombotic complications. Use when assessing a CS patient for thrombotic risk, especially perioperatively; triggers include preoperative assessment, postoperative period (within 4-6 weeks), or presence of CS with additional risk factors such as prior VTE, immobilization, malignancy, or estrogen use.

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

コンプライアンス・内部統制支援の専門スキル。J-SOX/SOX対応、リスクコントロールマトリクス（RCM）作成、 内部監査計画策定をサポート。内部統制の整備・運用評価から監査対応まで一貫した支援を提供。 日英両言語のテンプレートを提供し、グローバル企業にも対応。COSO内部統制フレームワーク（2013年版）に準拠。 Use when: creating J-SOX/SOX compliance documentation, building risk control matrices, planning internal audits, or assessing internal control effectiveness. Triggers: "J-SOX", "SOX", "内部統制", "コンプライアンス", "RCM", "リスクコントロールマトリクス", "内部監査", "compliance", "internal control", "internal audit", "risk assessment", "COSO"

Knowledge base from the GAO Schedule Assessment Guide (GAO-16-89G, 2015). Use for building, assessing, or auditing a program's integrated master schedule (IMS): the ten best practices of a reliable schedule (capture, sequence, resource, duration, traceability, valid critical path, reasonable total float, schedule risk analysis, updating, baseline), the four characteristics (comprehensive, well-constructed, credible, controlled), critical path method arithmetic (forward/backward pass, total float), schedule risk analysis (Monte Carlo, contingency), statusing and baseline control, and the Appendix II audit triad. Scheduling/time-management oriented: it is the authority on schedule reliability, but it is NOT a cost-estimating guide, a full SE process model, an agile guide, or a risk-management framework — see sibling packs (gao-cost, dau-se-guidebook, nasa-schedule, nasa-risk) for those.

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

Reviews one deal's notes and timeline (CRM opportunity record, activity log, emails, meeting notes, forecast entries) for risk signals such as a single contact thread, no identified budget owner, slipped or missing dates, silence after a proposal, an undefined decision process or a competitor named late, and returns a DRAFT risk register: each signal with the quoted evidence and its date, a severity on a stated scale, and one proposed next action with an owner role for the user to decide on. Use when the user asks to "review the risks on this deal", "why is this opportunity stalling", "is this deal single-threaded", "deal health check before the forecast call" or "what should we do next on <opportunity>". Do not use for a whole-account plan, use account-plan-builder instead; for scoring early leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

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

Use when working with Codeball — codeBall AI-powered pull request risk assessment including automatic PR quality scoring, risk classification, and auto-approval for low-risk changes. Use when configuring CodeBall for automated PR triage, risk-based review routing, and review workload optimization.

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

予測市場や取引エージェントの処理を、規約・データ品質・秘密情報・プライバシー・取引実行の観点で点検し、問題点と必要な対策を整理するスキル。

• 取引サービスの認証を加える前の確認
• 資産情報とAPIキーの扱いの点検
• 市場データの品質と出典表示の確認

Retrieve composite country risk intelligence — Country Instability Index (CII), travel advisory level, and active sanctions exposure — for one country by ISO code. Use when the user asks how risky or unstable a country is right now.

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

Ranks any list of impediments and their countermeasures using a value-stream scoring model (ROI, Cost to Implement, Ease of Deployment, Risk Factor) and a fixed prioritization formula. Use when someone asks to prioritize, rank, sequence, or triage impediments, countermeasures, remediation items, risks, findings, gaps, action items, or backlog entries; or mentions value-stream prioritization, A3 / lean countermeasure ranking, ROI vs. effort scoring, or building a remediation / improvement backlog. Works with GHQR findings, audit results, retrospective action items, risk registers, architecture review gaps, or any free-form `{impediment, countermeasure}` list.

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

Credit risk data cleaning and variable screening pipeline for pre-loan modeling. Use when working with raw credit data that needs quality assessment, missing value analysis, or variable selection before modeling. it covers data loading and formatting, abnormal period filtering, missing rate calculation, high-missing variable removal,low-IV variable filtering, high-PSI variable removal, Null Importance denoising, high-correlation variable removal, and cleaning report generation. Applicable scenarios arecredit risk data cleaning, variable screening, pre-loan modeling preprocessing.

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

Risk measurement and stress testing — VaR/CVaR/max drawdown calculation, Monte Carlo simulation, extreme-value tail-risk analysis, and historical scenario stress testing.

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

Build a vulnerability exception and risk acceptance tracking system covering approval workflows, compensating controls documentation, and automatic expiration for vulnerabilities that miss SLA remediation timelines. Use when standing up a governance process for risk acceptance and exception approvals to support PCI DSS, SOC 2, or NIST CSF compliance.

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

Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.

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

Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.

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

Chief AI Officer advisory for startups: model build-vs-buy decisions (API vs fine-tune vs in-house), AI risk classification under EU AI Act + US state patchwork, AI cost economics (API-to-self-hosted breakeven), and AI team org evolution. Use when deciding whether to call an API or fine-tune, classifying AI use cases for regulatory risk, calculating when self-hosting pays off, sequencing AI hires, or when user mentions CAIO, AI strategy, model selection, foundation model, fine-tuning, EU AI Act, NIST AI RMF, AI governance, model risk, or AI economics. Strategic only — does not duplicate engineering AI/ML skills.

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

Identify risky assumptions for a new product idea across 8 risk categories including Go-to-Market, Strategy, and Team. Use when evaluating startup risks, assessing a new product concept, or mapping assumptions for a new venture.

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

Scoring rules for daily churn-risk detection — usage decline, support friction, billing/payment risk, and renewal proximity — plus how to combine them into a ranked at-risk list with a reason and a suggested next step per account.

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

Audits a project's dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned or archived upstreams, npm publisher concentration, and install-time script execution. Use when asked to audit dependencies, assess supply-chain or third-party package risk, or review a dependency tree before an engagement.

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

Use when sizing Public Equity Investing positions, finding equity hedges, or building an integrated position-and-hedge risk plan from a listed-equity thesis. Do not use for thesis construction, standalone event underwriting, trade execution, personal investment advice, or credit-instrument risk.

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

[omh] Risky command screened by Jev: Jev action check before a risky command: secrets, outbound sends, blast radius; can only add a hold. Use when the user says: jev-action-check, jev action check, ask jev if this command is safe, jev risk check.

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

[omh] Recurring operating status and blockers: status, risks, blockers, priorities, and follow-ups. Use when the user says: ops-review, ops review, weekly ops review, status review, operating review, release risks, risks and blockers, priorities.

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

[omh] Engineering leadership over roadmap and risk: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence. Use when the user says: cto-loop, cto loop, cto, cto pm, pm dev qa security ops, roadmap technical tradeoffs, technical tradeoff, delivery risk.

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