financial-intelligence-unit

Triage FIU alerts into defensible case files and MLRO-ready packs.

7|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill financial-intelligence-unit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: financial-intelligence-unit
Source: https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill/tree/main/financial-intelligence-unit
Command: npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill financial-intelligence-unit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps transform raw alerts and referrals into structured, defensible case files for FIU investigations, ensuring rapid triage, robust analysis, and MLRO-ready escalation.

Core Features & Use Cases

  • Intake & triage: queue management, priority scoring, and data completeness checks to accelerate case creation.
  • Investigation & typologies: flow reconstruction, counterparty mapping, and typology testing to substantiate suspicions.
  • Documentation & QA: contemporaneous chronology, case exhibits, and QA reviews to enable audit-ready packs.
  • MLRO escalation & handover: concise MLRO packs with executive summaries, gap logs, and escalation options.
  • Internal reporting & training: MI outputs, playbook updates, and shared learnings to improve performance.

Quick Start

Load the FIU playbook and triage the latest TM alert to create a defensible case file.

Frequently Asked Questions about financial-intelligence-unit

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

FAQPage Schema
How do I triage AML alerts into defensible case files for MLRO escalation?

Triage AML alerts by applying priority scoring and data completeness checks to structure raw referrals into defensible case files with contemporaneous chronology and MLRO-ready escalation packs. This ensures audit-ready documentation for financial investigations.

What is typology testing in FIU case management and when is it needed?

Typology testing in FIU case management involves flow reconstruction and counterparty mapping to substantiate transactional suspicions. It is needed during AML/CFT investigations to validate whether alert patterns match known financial typologies before escalation.

Can I use this for transaction monitoring alert queues and QA reviews?

Yes, this handles transaction monitoring alert queues through intake, priority scoring, and investigation, while also supporting QA reviews to verify contemporaneous chronology, case exhibits, and suspicion mapping for audit-ready outputs.

How do I create MLRO-ready packs from raw financial intelligence alerts?

Create MLRO-ready packs by capturing case chronology, exhibit indexing, suspicion mapping, and gaps tracking into concise executive summaries with escalation options. This transforms raw alerts into structured handover documentation for MLRO review.

What's the best way to track investigation gaps and case chronology for audit review?

Track investigation gaps and case chronology by maintaining contemporaneous documentation and exhibit indexing throughout the FIU workflow. This ensures all suspicion mapping and escalation options are captured for audit and regulatory review.