Brand Product Knowledge Builder
limecloud/lime
将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界,整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的产品资料知识库。适用于用户要求“整理产品知识库”“沉淀产品 FAQ”“把品牌产品资料变成项目资料”“维护产品资料包”的场景。
Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission.
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JoelLewis/finance_skills client-onboarding --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .claude/skills/client-onboarding && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .claude/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboardingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JoelLewis/finance_skills client-onboarding --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .agents/skills/client-onboarding && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .agents/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JoelLewis/finance_skills client-onboarding --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .cursor/skills/client-onboarding && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .cursor/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JoelLewis/finance_skills.git --path plugins/advisory-practice/skills/client-onboarding--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JoelLewis/finance_skills client-onboarding --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .gemini/skills/client-onboarding && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .gemini/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JoelLewis/finance_skills client-onboardingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .github/skills/client-onboarding && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .github/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JoelLewis/finance_skills --skill client-onboarding -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JoelLewis/finance_skills client-onboarding --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/advisory-practice/skills/client-onboarding .opencode/skills/client-onboarding && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "client-onboarding" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-onboarding into .opencode/skills/client-onboarding/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-onboarding", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
client-onboardingDesign and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission.
Client Onboarding is an agent skill from JoelLewis/finance_skills. Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Use when the user asks about building a digital onboarding flow, integrating identity verification or CIP checks, reducing NIGO rejection rates, opening complex account types like trusts or entities, connecting to custodian APIs, designing suitability questionnaires, or comparing advisor-assisted vs self-service models. Also…
Its SKILL.md is about 8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Sales & Support, covering Help center and FAQ content. The repository describes itself as: Claude Code skill plugins for financial services — 81 skills across 7 domain plugins covering investment management, compliance, advisory practice, trading, and operations. The licence is MIT.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 5c498ea. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Client Onboarding loads about 8k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 180 tokens; SKILL.md has 3,999 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from JoelLewis/finance_skills at commit 5c498ea, republished under its MIT licence (© JoelLewis). 3,999 words, ~8,018 tokens.
.claude/skills/client-onboarding/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Client onboarding is an orchestrated, multi-stage process that transforms a prospect into a funded, investable account. The canonical stages are:
The two primary flow models are advisor-assisted and self-service (digital-direct). In advisor-assisted onboarding, the advisor guides the client through each step, often in a meeting or screen-share, with the onboarding platform pre-populating data from the CRM. In self-service onboarding, the client completes a guided digital workflow independently, with the advisor reviewing and approving the completed application. Most firms support a hybrid model where self-service handles simple account types and advisor-assisted handles complex ones.
The onboarding platform acts as an orchestrator across multiple downstream systems: CRM (client master), KYC/AML vendor (identity verification), custodian (account opening API), document management (storage and retrieval), and portfolio management system (model assignment). The platform must manage state transitions, handle errors at each stage, and provide visibility to both the advisor and compliance.
Identity verification during onboarding must satisfy CIP requirements under USA PATRIOT Act Section 326 and, for legal entities, the FinCEN CDD Rule (31 CFR 1010.230). The onboarding workflow collects the following minimum identifying information:
Verification methods integrated into digital onboarding:
OFAC and sanctions screening is a mandatory gate before account opening. The onboarding platform must screen all individuals associated with the account (account holders, authorized signers, beneficial owners, trustees) against the OFAC SDN list, FinCEN 314(a) lists, and any firm-specific restricted lists. A match or potential match must halt the onboarding flow and route to compliance for manual review.
Beneficial ownership collection for entity accounts requires identification of every individual who directly or indirectly owns 25% or more of the equity interests in the legal entity, plus at least one individual with significant managerial control (the control person). The onboarding workflow must dynamically present beneficial ownership forms when the account type is an entity (LLC, corporation, partnership, certain trusts).
Enhanced due diligence triggers that the onboarding system should detect and flag: politically exposed persons (PEPs), connections to high-risk jurisdictions (per FinCEN advisories and FATF guidance), complex multi-layered ownership structures, and negative news screening results. When EDD is triggered, the onboarding flow should pause and escalate to the compliance team before proceeding.
Onboarding is the primary data collection event for investment suitability. Before any investment recommendation can be made, the firm must gather sufficient information to satisfy FINRA Rule 2111 (suitability) for broker-dealers and Regulation Best Interest for BD recommendations, or the fiduciary duty of care for registered investment advisers.
Required data elements:
Risk questionnaire design follows two approaches:
Best practice is a combined approach: psychometric questions to assess willingness, financial data to assess capacity, and a mapping algorithm that produces a risk score or category. The risk score then maps to a model portfolio or investment strategy range.
Regulatory requirements at onboarding: The suitability profile must be documented before the first investment recommendation. For discretionary accounts, the investment policy statement (IPS) should be established during onboarding. For Reg BI accounts, the Care Obligation requires that any recommendation — including account type — have a reasonable basis given the client's profile.
The onboarding workflow must guide account type selection based on the client's needs. Account types and their key characteristics:
Individual and joint accounts:
Retirement accounts:
Trust accounts:
Entity accounts:
Custodial accounts:
Estate accounts:
Account features configured during onboarding:
Each account type requires a specific document package. The onboarding system should dynamically assemble the required documents based on the account type and features selected.
Universal documents (all account types):
Account-type-specific documents:
Feature-specific documents:
Document assembly in modern onboarding platforms involves pre-populating forms with data already collected during earlier onboarding stages (identity, suitability, account type). The system generates a personalized document package with client data filled in, leaving only signature blocks and any fields that require manual completion. This dramatically reduces errors and accelerates the process.
Document management considerations:
Electronic signatures are legally binding for account opening documents under the E-SIGN Act (15 USC 7001) and the Uniform Electronic Transactions Act (UETA), adopted in some form by 49 states and DC.
E-SIGN Act requirements for valid electronic signatures:
E-signature platform integration: Most advisory firms use DocuSign, Adobe Sign, or custodian-embedded signing tools (e.g., Schwab's e-signature within their account opening API). Integration patterns include:
Consent to electronic delivery is a prerequisite. Before delivering documents electronically, the firm must obtain the client's affirmative consent, inform them of their right to receive paper copies, and verify their ability to access electronic documents. This consent is typically captured as one of the first steps in a digital onboarding flow.
Wet signature exceptions: Some custodians and certain form types still require original (wet ink) signatures. Common exceptions include: certain international account forms, some trust documentation, specific alternative investment subscription agreements, and medallion signature guarantees for account transfers. The onboarding system should identify these exceptions and route them to a wet-signature workflow.
Signature ceremony design for multi-party accounts:
Audit trail requirements: The e-signature record must include: signer identity (name, email), timestamp of each signature, IP address, authentication method used, document hash (to prove the signed document was not altered post-signature), and a certificate of completion. This audit trail must be retained as part of the account records.
After documents are signed, the completed application package is submitted to the custodian for account creation. Submission methods vary by custodian and account complexity:
API-based submission (straight-through processing):
Semi-automated submission:
Manual submission:
NIGO (Not In Good Order) handling: A NIGO rejection means the custodian has found errors or missing information in the application. Common NIGO causes:
NIGO remediation workflow: the onboarding system should receive NIGO notifications from the custodian (via API callback, email, or status polling), parse the rejection reason, notify the advisor and/or client, collect the corrected information or documents, and resubmit. Reducing NIGO rates is one of the highest-impact onboarding optimizations.
Account funding methods:
Initial investment: Once the account is funded, the onboarding system should trigger model portfolio assignment. For discretionary accounts, this means linking the account to the appropriate model in the portfolio management system (PMS) and generating the initial trade orders. For non-discretionary accounts, the advisor submits the first investment recommendation.
Effective onboarding embeds compliance gates at specific stages, preventing the workflow from advancing until requirements are met:
Gate 1 — Identity verification (before account opening):
Gate 2 — Suitability documentation (before investment):
Gate 3 — Beneficial ownership (before entity account opening):
Gate 4 — Disclosure delivery (before or at account opening):
Gate 5 — Supervisory review (risk-based, before account activation):
Compliance hold and escalation:
Onboarding is the primary data collection event that populates downstream systems. The data collected during onboarding flows to:
Integration patterns:
Data validation: The onboarding system should validate data consistency across systems. Common validation checks:
Pre-population for existing clients: When an existing client opens an additional account, the onboarding system should pre-populate known data from the CRM and existing account records. Identity verification may be streamlined (re-verification vs full CIP depending on firm policy), and suitability data may only need to be confirmed rather than re-collected.
Measuring onboarding effectiveness enables continuous improvement:
Key performance indicators:
Bottleneck identification:
Optimization strategies:
Three worked examples are in references/examples.md — load for an end-to-end scenario: (1) designing a digital onboarding flow for individual taxable accounts with Schwab/Salesforce/Orion integration, (2) onboarding an irrevocable trust account for a high-net-worth client alongside individual accounts, (3) reducing a 35% NIGO rate through validation rules and automated document assembly.
© JoelLewis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/advisory-practice/skills/client-onboarding of JoelLewis/finance_skills.
Open the folder on GitHubat commit 5c498ea
Client Onboarding next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Client Onboarding this skillJoelLewis/finance_skills | 205 | — | ~8k | Automated safety check: Pass | MIT | |
| Brand Product Knowledge Builderlimecloud/lime | 1.5k | — | ~709 | Automated safety check: Pass | Apache-2.0 | |
| Cc10x Guideromiluz13/cc10x | 164 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Yao Geo Intent Mineryaojingang/yao-geo-skills | 868 | — | ~500 | Automated safety check: Pass | MIT | |
| Faq CollectorCherryHQ/cherry-studio | 52k | — | ~154 | Automated safety check: Pass | AGPL-3.0 | |
| Eol Internal Enablementdeanpeters/Product-Manager-Skills | 7.2k | — | ~3.1k | Automated safety check: Pass | Custom licence |
limecloud/lime
将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界,整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的产品资料知识库。适用于用户要求“整理产品知识库”“沉淀产品 FAQ”“把品牌产品资料变成项目资料”“维护产品资料包”的场景。
romiluz13/cc10x
Answers questions about cc10x itself — what it is, how to install and configure it, how the router, workflows, memory, and hooks operate, and how to troubleshoot.
yaojingang/yao-geo-skills
A skill your agent uses when a user asks for GEO 意图拓词、AI 搜索意图挖掘、AI 搜索问题集、问题簇、追问链路、查询重写、内容选题库、FAQ 题库、监测 Prompt 库, or AI Intent Miner.
CherryHQ/cherry-studio
将成功解决的用户问题收录到 FAQ 知识库。问题解决后自动判断是否收录。也可以在用户说"收录到 FAQ"、"记录这个问题"、"add to FAQ"时手动触发。
deanpeters/Product-Manager-Skills
Build the support FAQ, sales talking points, and objection handling teams need before an EOL announcement.
Harryoung/efka
Handle user satisfaction feedback. An agent skill from Harryoung/efka.
JoelLewis/finance_skills
Analyze equity securities, factor models, and equity portfolio construction.
JoelLewis/finance_skills
Determine how to distribute capital across asset classes using strategic and tactical allocation frameworks.
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
JoelLewis/finance_skills
Analyze commodity markets including futures curve dynamics, roll yield, and supply/demand fundamentals.
JoelLewis/finance_skills
Analyze currency markets, exchange rate mechanics, and FX risk management for international portfolios.
JoelLewis/finance_skills
Provide frameworks for managing and paying off personal debt effectively.
Categories
Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission. Client Onboarding is an agent skill from JoelLewis/finance_skills. Design and implement end-to-end client onboarding workflows from prospect intake through funded account, covering KYC verification, document collection, e-signature, and custodian submission.
Client Onboarding fits situations like: the user asks about building a digital onboarding flow; integrating identity verification; reducing NIGO rejection rates; opening complex account types like trusts.
Run `npx skills add JoelLewis/finance_skills --skill client-onboarding -a claude-code`. Or copy the skill folder (plugins/advisory-practice/skills/client-onboarding in JoelLewis/finance_skills) into .claude/skills/client-onboarding in your project. Claude Code loads it when a task matches its description.
Run `npx skills add JoelLewis/finance_skills --skill client-onboarding -a codex`. Or copy the skill folder (plugins/advisory-practice/skills/client-onboarding in JoelLewis/finance_skills) into .agents/skills/client-onboarding in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JoelLewis/finance_skills --skill client-onboarding -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-onboarding, .gemini/skills/client-onboarding, .github/skills/client-onboarding and .opencode/skills/client-onboarding in your project.
SKILL.md names no scripts, command-line tools or credentials: Client Onboarding is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Client Onboarding is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 8k tokens (SKILL.md is roughly 32k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Client Onboarding: Brand Product Knowledge Builder (limecloud/lime, 1.5k stars), Cc10x Guide (romiluz13/cc10x, 164 stars), Yao Geo Intent Miner (yaojingang/yao-geo-skills, 868 stars) and Faq Collector (CherryHQ/cherry-studio, 52k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
JoelLewis (a GitHub user) maintains it in JoelLewis/finance_skills, which has 205 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on July 18, 2026.
Source: JoelLewis/finance_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.