kri-engineer

Build Key Risk Indicator engines aggregating platform signals into governance-level risk metrics.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Muath2000/TradeStation --skill kri-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kri-engineer
Source: https://github.com/Muath2000/TradeStation/tree/main/.claude/skills/kri-engineer
Command: npx skills add https://github.com/Muath2000/TradeStation --skill kri-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of converting raw, disparate platform data into clear, actionable Key Risk Indicators (KRIs) that inform governance and executive decision-making.

Core Features & Use Cases

  • KRI Definition & Management: Design and configure KRIs with custom formulas, thresholds, and data sources.
  • Automated Alerting & Escalation: Trigger alerts and workflows based on KRI threshold breaches.
  • Trend Analysis & Forecasting: Monitor KRI trends and predict future performance against risk appetite.
  • Board Reporting: Integrate KRI status and trends into executive-level reports.
  • Use Case: A CISO needs to understand the organization's overall security posture. This Skill can aggregate data from vulnerability scanners, compliance checks, and vendor assessments to create KRIs like "Critical Vulnerabilities Unpatched > 24 hours" and "Vendor Risk Score > 80", providing a consolidated view for the board.

Quick Start

Use the kri-engineer skill to build a new KRI definition for tracking the percentage of critical vulnerabilities that remain unpatched for more than 24 hours.

Frequently Asked Questions about kri-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a Key Risk Indicator engine for aggregating platform signals into governance metrics?

Building a Key Risk Indicator engine involves configuring KRI definitions with custom formulas, thresholds, and data sources to aggregate disparate platform signals into governance-level risk metrics. You can manage automated alerting, trend tracking, and board report integration for executive decision-making.

Can I create custom formulas and thresholds for compliance and vulnerability risk indicators?

Yes, you can create custom formulas and thresholds for compliance and vulnerability risk indicators. The engine supports complex formula building across diverse risk domains, allowing you to define specific conditions like critical vulnerabilities remaining unpatched beyond a set timeframe.

How does automated alerting work when a risk indicator breaches a configured threshold?

Automated alerting triggers configured workflows and escalations immediately when a risk indicator breaches a defined threshold. This ensures governance teams are notified of threshold violations across operational, financial, or vendor risk domains for timely response.

What is the best way to track and forecast risk indicator trends for board reporting?

The best way to track and forecast risk indicator trends is using a KRI engine that monitors metric progression and predicts future performance against organizational risk appetite. This enables direct integration of status and trends into executive-level board reports.