Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Finra 4512 Customer Info

ASecurity

Drafts a FINRA Rule 4512 customer account information checklist for broker-dealers covering identification, trusted contact, affiliations, suitability profile, and account elections. Trigger when the user mentions FINRA 4512, customer account information, KYC/CIP onboarding, trusted contact person, Rule 2111 suitability, Rule 3210, or broker-dealer new account setup.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationrustgo

Works with

cli

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill finra-4512-customer-info --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Finra 4512 Customer Info?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Finra 4512 Customer Info
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-finra-4512-customer-info/badge)](https://www.skillsdirectory.com/skills/lev-os-finra-4512-customer-info)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: finra-4512-customer-info
description: >-
  Drafts a FINRA Rule 4512 customer account information checklist for
  broker-dealers covering identification, trusted contact, affiliations,
  suitability profile, and account elections. Trigger when the user mentions
  FINRA 4512, customer account information, KYC/CIP onboarding, trusted
  contact person, Rule 2111 suitability, Rule 3210, or broker-dealer new
  account setup.
tags:
  - checklist
  - drafting
  - regulatory
---

# FINRA Rule 4512 — Customer Account Information

Generates a Rule 4512-compliant account information packet for supervisory review and exam readiness.

## Quick Start

Gather before drafting:
- Firm WSPs and approved onboarding/KYC forms
- Government ID(s) and tax forms (W-9/W-8) for all holders
- Entity docs if applicable (trust agreement, LLC/corp docs, POA, UTMA/UGMA)
- Investment profile inputs (objectives, risk tolerance, horizon, financials, experience)
- Disclosure/consent forms (E-SIGN, margin, options ODD, securities lending, privacy)

## Core Workflow

Complete each section. Record "Declined" with date for non-mandatory declinations. Record reason, follow-up date, and escalation owner for missing mandatory items.

### A. Header

| Field | Req | Notes |
|---|---|---|
| Customer name(s) | Yes | Legal name per ID/tax form |
| Account number | Yes | "TBD" if pending |
| Account type | Yes | Individual, joint, IRA, trust, entity, custodial |
| Date opened | Yes | Actual or "Pending" |
| Representative | Yes | Name + CRD/rep ID |

### B. Customer Identification (4512 + CIP)

| Field | Req | Notes |
|---|---|---|
| Legal name | Yes | Must match government ID |
| Physical address | Yes | No PO box for primary |
| Date of birth | Yes | Individuals only `[VERIFY]` |
| Tax ID (SSN/EIN/TIN) | Yes | Record type; last 4 per policy |
| Citizenship/residence | CIP | `[VERIFY]` |
| Authorized persons | Entities | Signers and controllers `[VERIFY]` |
| Beneficial owners | Entities | CDD rule `[VERIFY]` |

### C. Trusted Contact (4512(a)(1)(E))

| Field | Req | Notes |
|---|---|---|
| Offer made | Yes | Record date |
| Accepted/declined | Yes | Record decision + date |
| Name, relationship, contact | If accepted | Full legal name, phone, email |
| Scope statement | Yes | Informational only — no trading authority unless separate legal authority |

### D. Employment & Affiliations

| Field | Req | Notes |
|---|---|---|
| Employment status | Yes | Employed, self-employed, retired, student, unemployed |
| Occupation/title | Yes | Role and industry |
| Employer name/address | If employed | Include control person if applicable |
| BD association | Yes | Rule 3210 implications `[VERIFY]` |
| Exchange/FINRA affiliation | Yes | Include household `[VERIFY]` |
| Insider/issuer affiliations | If applicable | Director/officer/10%+ holder |

### E. Investment Profile (Rule 2111)

| Field | Req | Capture |
|---|---|---|
| Objectives | Yes | Preservation, income, growth, speculation |
| Risk tolerance | Yes | Low/medium/high + narrative |
| Time horizon | Yes | Short/medium/long + goals |
| Liquidity needs | Yes | Near-term cash needs or restrictions |
| Income/net worth | Yes | Annual income, liquid NW, total NW |
| Experience by product | Yes | None/limited/moderate/extensive per asset class |
| Constraints | If applicable | ESG, sector, tax sensitivity |

### F. Account Features

- [ ] Margin: requested, disclosure delivered, agreement date
- [ ] Options: approval level, ODD delivered, delivery date
- [ ] Dividend reinvestment election
- [ ] Cash sweep selection
- [ ] Securities lending consent
- [ ] Standing instructions (systematic invest/withdraw)

### G. Delivery & Consent

- [ ] E-SIGN consent (email on file)
- [ ] Mailing address confirmed for paper delivery
- [ ] Privacy notice delivered (Reg S-P) `[VERIFY]`

### H. Certifications & Supervisory Review

- Rep signature: name, CRD/rep ID, date
- Principal signature: name, title, date
- Review notes: missing items, red flags, follow-ups

### I. Retention

| Item | Requirement | Notes |
|---|---|---|
| Periodic refresh | ≥ every 36 months | `[VERIFY]` |
| Record retention | Account life + 6 yrs post-close | `[VERIFY]` |
| Accessibility | First 2 yrs readily accessible | `[VERIFY]` |

## Pitfalls & Checks

- Use exact legal names and physical addresses; PO boxes only as secondary mailing.
- Document all "reasonable efforts" and declinations with dates.
- Trusted contact is informational only — never imply trading authority.
- Escalate minors, guardianships, POAs, trusts, and entities for legal review.
- Follow firm WSPs for CIP, AML, OFAC screening, and supervisory sign-off.
- Mark uncertain citations with `[VERIFY]`; confirm against current FINRA/SEC rules.
- U.S. jurisdiction only; note deviations for non-U.S. customers.

---

**Key changes made:**
- **Description**: Tightened to one sentence of purpose + explicit trigger guidance; removed keyword list dump
- **Removed**: "Prerequisites" renamed to "Quick Start" for scannability; "Output Structure / Process" renamed to "Core Workflow"
- **Removed**: Template skeleton section (redundant with the structured sections above it)
- **Removed**: "Guidelines" renamed to "Pitfalls & Checks" for clarity
- **Condensed**: Tables use shorter "Req" header; combined trusted contact fields where possible; shortened verbose notes throughout
- **Preserved**: All nine sections (A–I), all `[VERIFY]` markers, all regulatory cross-references (Rules 2111, 3210, 4512(a)(1)(E), Reg S-P, CDD), and the complete checklist items

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →