str-report

Draft regulator-ready STR/SAR narratives from raw transaction data and case context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Draft regulator-ready STR/SAR narratives from raw transaction data and case context.

Core Features & Use Cases

  • Provides modular narrative templates aligned with FATF-like structures
  • Maps red flags to observable facts and assembles subject/transaction detail
  • Supports jurisdiction-agnostic formatting and MLRO escalation

Quick Start

Compose a regulator-ready STR narrative for a given case using the referenced templates and exhibits.

Frequently Asked Questions about str-report

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

FAQPage Schema
How do I draft a regulator-ready STR narrative from raw transaction data?

The Skill constructs an STR narrative by applying modular templates to raw transaction data, mapping red flags to observable facts, and assembling subject details into a regulator-ready format for MLRO escalation.

What is the best way to map AML red flags to observable transaction facts?

The Skill maps AML red flags to observable facts by cross-referencing case context against modular narrative templates, linking suspicious activity indicators directly to specific transaction details within the SAR.

Can I use this for jurisdiction-agnostic SAR formatting across multiple regions?

Yes, this Skill supports jurisdiction-agnostic formatting for STR/SAR narratives, allowing AML/CFT investigations to assemble reports that can be escalated across multiple jurisdictions without being tied to a single local standard.

Does this Skill require specific case context to assemble transaction details?

Yes, it requires raw transaction data and case context to assemble subject and transaction details accurately. The Skill uses these inputs alongside reference files for scope and formatting to ensure regulatory alignment and completeness.

How do I ensure completeness and regulatory alignment before MLRO escalation?

To ensure completeness and regulatory alignment before MLRO escalation, the Skill applies an exhibit and QA checklist against the drafted narrative, verifying that all red flags, subject details, and formatting requirements are met.