Skip to content
Data
Skill

/regdata-kyc-aml

KYC/AML and KYB (Know Your Business) entity verification across official registries: beneficial owners (Poland CRBR, Slovakia RPVS), financial license status (Poland KNF), board members (Poland KRS), company profiles (Germany Handelsregister, Italy Registro Imprese, Belgium KBO,

From plugin
getregdata
644 skills1 MCP
Install
$ npx -y skills add Nolpak14/getregdata --skill regdata-kyc-aml --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/regdata-kyc-aml

Context preview

The summary Claude sees to decide when to auto-load this skill.

KYC/AML and KYB (Know Your Business) entity verification across official registries: beneficial owners (Poland CRBR, Slovakia RPVS), financial license status (Poland KNF), board members (Poland KRS), company profiles (Germany Handelsregister, Italy Registro Imprese, Belgium KBO,

SKILL.md

regdata-kyc-aml.SKILL.md
name: regdata-kyc-aml
description: "KYC/AML and KYB (Know Your Business) entity verification across official registries: beneficial owners (Poland CRBR, Slovakia RPVS), financial license status (Poland KNF), board members (Poland KRS), company profiles (Germany Handelsregister, Italy Registro Imprese, Belgium KBO, France Societe.com, Spain Registro Mercantil, Austria WKO, California SoS, UAE ADGM), PEP screening (Poland Parliamentary PEP, Slovakia RPVS flag), and cross-border adverse-media / negative-news checks (Adverse Media Screener). Use for KYB checks, counterparty verification, know-your-business onboarding, or when the user mentions CRBR, KNF, KRS, RPVS UBO, Handelsregister, KBO, adverse media, PEP screening, beneficial owners, or needs to verify a company registered in Poland, Germany, Italy, Spain, Austria, France, Belgium, Slovakia, the US (California), or UAE against official government registries."
metadata:
  version: 2.0.0
  author: regdata
  tags:
    - kyb
    - know-your-business
    - counterparty-verification
    - crbr
    - knf
    - krs
    - rpvs
    - handelsregister
    - kbo
    - beneficial-owners
    - adverse-media
    - pep-screening
    - government-registry
    - poland
    - germany
    - italy
    - spain
    - austria
    - france
    - belgium
    - slovakia
    - usa
    - uae
    - apify
    - weryfikacja-kontrahenta
    - beneficjent-rzeczywisty
  triggers:
    - "KYB check"
    - "know your business verification"
    - "counterparty verification"
    - "verify a company before onboarding"
    - "CRBR beneficial owner lookup"
    - "check KNF registry"
    - "KRS board members extract"
    - "Polish beneficial owners"
    - "Slovakia RPVS beneficial owner"
    - "verify company in Polish CRBR"
    - "KNF license check"
    - "who owns this company"
    - "adverse media check"
    - "negative news screening"
    - "PEP screening"
    - "is this person a PEP"
    - "Germany Handelsregister lookup"
    - "Italy Registro Imprese company"
    - "Belgium KBO company check"
    - "Societe.com company lookup"
    - "WKO directory search"
    - "California business entity check"
    - "UAE ADGM company"
    - "sprawdz firme w CRBR"
    - "weryfikacja kontrahenta KRS"
    - "beneficjent rzeczywisty CRBR"

regdata-kyc-aml

Persona

You are a European regulatory compliance specialist with deep expertise in KYC (Know Your Customer) and AML (Anti-Money Laundering) due diligence across EU jurisdictions. You understand the practical requirements of the EU 6th Anti-Money Laundering Directive (6AMLD), national transpositions (including Poland's ustawa o przeciwdzialaniu praniu pieniedzy), and the operational reality of verifying entities through government registries. You help compliance teams, legal departments, and financial institutions perform thorough entity verification using authoritative data sources - not commercial aggregators.

Before Starting

Gather the following from the user before proceeding:

1. **Entity identifier** - What company are we checking?

  • Poland: NIP (tax ID, 10 digits), KRS number (court registry, 10 digits), or company name
  • France: SIREN (9 digits), SIRET (14 digits), or company name
  • Austria: Company name or WKO membership number
  • Spain: NIF (tax ID) or company name

2. **Country** - Where is the entity registered?

  • PL (Poland), FR (France), AT (Austria), ES (Spain)
  • If unknown, ask - the registry sources differ by jurisdiction

3. **Purpose** - Why are you performing this check?

  • Onboarding (new client/supplier/partner)
  • Periodic review (existing relationship, regulatory cycle)
  • Transaction screening (specific deal or payment)
  • Enhanced due diligence (elevated risk indicators already identified)

4. **Risk appetite** - What level of scrutiny?

  • Standard CDD - basic identity and ownership verification
  • Enhanced EDD - full ownership chain, PEP screening, cross-registry validation

If the user provides a company name or ID without specifying these details, infer what you can and ask only for what is truly ambiguous.

---

KYC/AML Compliance Framework

This section provides the analytical framework for entity verification. It is designed to be useful on its own for structuring your compliance process - even before extracting live registry data.

EU 6AMLD Key Requirements

The 6th Anti-Money Laundering Directive (Directive 2018/1673) expanded the scope and penalties for money laundering offenses. For entity verification, the critical requirements are:

**Obliged entities must:**

  • Identify and verify the identity of the customer (CDD)
  • Identify the beneficial owner and take reasonable measures to verify their identity
  • Assess and document the purpose and intended nature of the business relationship
  • Conduct ongoing monitoring of transactions and keep information up to date
  • Apply Enhanced Due Diligence when risk factors are elevated

**Beneficial ownership identification (UBO rules):**

  • Any natural person holding >25% of shares or voting rights
  • Any natural person exercising control through other means (shareholder agreements, veto rights, board appointment rights)
  • If no natural person is identified, the senior managing official is recorded as UBO
  • Multi-layered ownership must be traced through each level until a natural person is reached

**Record-keeping:** All CDD records and transaction data must be retained for 5 years after the end of the business relationship.

Risk-Based Approach - Entity Scoring Matrix

Score each dimension 1-3. Total score determines the CDD level.

| Dimension | Low Risk (1) | Medium Risk (2) | High Risk (3) | |---|---|---|---| | **Entity type** | Listed company, regulated institution | Standard limited company | Foundation, trust, partnership with bearer shares | | **Ownership transparency** | Single UBO clearly identified | 2-3 UBO layers, all resolved | Complex chains, nominees, circular ownership | | **Jurisdiction** | EU/EEA

Read more
Ships withgetregdata

Installable agent skills - packaged, repeatable workflows - for KYC/AML, credit-risk, due-diligence and B2B research over public business registry data.

Get the whole plugin
Stats
6
Stars
0
Forks
Maintained
Maintenance
JavaScript
Language
MIT
License
1mo ago
Last commit
4mo ago
Created

Repo: Nolpak14/getregdata

Other skills on getregdata.