kyc-doc-parse

Parse onboarding documents into structured KYC fields and output JSON records.

Updated May 9, 2026
One-click install
npx skills add https://github.com/mahyarmalekii/MarketIntel --skill kyc-doc-parse-mahyarmalekii
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kyc-doc-parse
Source: https://github.com/mahyarmalekii/MarketIntel/tree/main/backend/financial-services/plugins/vertical-plugins/operations/skills/kyc-doc-parse
Command: npx skills add https://github.com/mahyarmalekii/MarketIntel --skill kyc-doc-parse-mahyarmalekii

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the parsing of investor or client onboarding packets, extracting structured KYC fields for identity, ownership, control, source of funds, and document inventory. It streamlines the initial step of KYC screening and integrates with a rules engine for further processing.

Core Features & Use Cases

  • KYC Document Parsing: Extracts identity, ownership, control, source of funds, and document inventory from onboarding packets.
  • Structured Data Output: Outputs JSON records with structured information for further processing by rules engines.
  • Use Case: For financial institutions processing a high volume of client onboarding packets, this Skill can automate the initial review process, saving time and reducing errors.

Quick Start

Use the kyc-doc-parse skill to parse the onboarding packet and generate a structured JSON output.

Frequently Asked Questions about kyc-doc-parse

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

FAQPage Schema
How do I automate KYC document parsing for client onboarding packets?

Automating KYC document parsing involves extracting identity, ownership, control, source of funds, and document inventory fields from untrusted onboarding packets. This process generates structured JSON records for direct integration with downstream financial compliance rules engines.

What structured data fields are extracted during financial compliance onboarding?

Structured data extraction for financial compliance captures identity, ownership, control, source of funds, and document inventory details. This structured data output allows financial institutions to process high volumes of client onboarding packets efficiently.

How does structured KYC data integrate with rules engines?

Structured KYC data integrates with rules engines by outputting standardized JSON records containing extracted identity, ownership, and source of funds fields. These JSON records serve as the direct input for automated screening and compliance evaluation.

Can I parse untrusted investor onboarding documents without manual review?

Parsing untrusted investor onboarding documents without manual review is possible by automating the extraction of structured KYC fields. This initial screening step outputs JSON records for integration with a rules engine, reducing errors and saving time.

What is the best way to extract source of funds information from onboarding packets?

The best way to extract source of funds information is using an automated KYC document parser. It processes untrusted client onboarding packets and extracts structured source of funds data alongside identity and ownership details into JSON records.

Are there limitations when processing high volumes of client onboarding packets?

While processing high volumes of client onboarding packets saves time, this Skill focuses on the initial parsing step. It generates structured JSON records for a rules engine, meaning it does not replace the subsequent compliance screening or final decision-making process.