Agent skill · product strategy · borghei
fintech-advisor
Strategic advisory for fintech founders on US/EU regulatory triggers, license-vs-partner, KYC/AML, and embedded finance. Use when scoping a fintech idea or regulatory exposure, or mentioning fintech, money transmitter, neobank, KYC, or PSD2.
Why this skill is useful
Provides specific regulatory frameworks and a Python script for assessing regulatory triggers that the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 4k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Fintech Advisor Strategic frameworks for fintech founders, operators, and product leaders. Knowledge-heavy by design — the right answer in fintech is usually a regulatory and economic judgment, not a calculation. Disclaimer: This skill provides frameworks and orientation. It is not legal, regulatory, securities, tax, or investment advice. Every fintech business needs licensed legal counsel. Use this skill to organize internal thinking; engage specialist counsel for binding decisions. --- Table of Contents Keywords Quick Start Core Workflows Tools Reference Guides Templates Best Practices --- Keywords fintech, payments, banking, neobank, lending, money transmitter, KYC, AML, PSD2, open banking, BaaS, banking-as-a-service, embedded finance, card issuing, ACH, SEPA, stablecoin, crypto, broker-dealer, RIA, regulation, compliance --- Quick Start Initial Regulatory Triage in 10 Minutes 1. Write a 1-paragraph description of what your fintech does (who pays whom, in what form, who holds the funds) 2. Run python scripts/regulatorytriggerchecker.py businessdescription.txt 3. Use the output as input to a conversation with a fintech-licensed lawyer — never as the conclusion License vs. Partner Decision 1. Read references/licensevspartnerplaybook.md 2. For each capability you need (hold funds, issue cards, originate loans, send payments), decide: get a license, or partner with a licensed entity (BaaS, sponsor bank) 3. Most early-stage fintechs partner. License only if the unit economics or moat absolutely require it. --- Core Workflows Workflow 1: Regulatory Exposure Scoping Goal: Understand which US / EU regulatory regimes a proposed fintech business model triggers, before committing to architecture. Steps: 1. Write a clear business description: who pays whom, what is held by whom, where the entity operates 2. Run the trigger checker for a quick orientation 3. Map each trigger to the relevant regulator (FinCEN, OCC, state banking commissioners, SEC, CFPB, FCA, BaFin, ACPR) 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/fintech-advisor