Apply the investment adviser fiduciary duty (IA Act Section 206), ERISA fiduciary standards, the DOL fiduciary rule and PTE 2020-02, and state fiduciary rules. Use when the user asks whether a fiduciary standard applies, what the duty of care and duty of loyalty require of an adviser, ERISA Section 404 prudent expert obligations, PTE 2020-02 rollover exemption conditions, DOL fiduciary rulemaking status, or state-level fiduciary developments. Also trigger when users mention 'are we a fiduciary here', 'retirement plan adviser obligations', 'DOL fiduciary rule', or 'dual registrant hat switching' from the adviser side. (For the broker-dealer best-interest standard and the canonical Reg BI vs fiduciary comparison, use reg-bi.)
npx skills add https://github.com/JoelLewis/finance_skills --skill fiduciary-standards
Regulatory status current as of June 2026 — verify effective dates, dollar thresholds, and pending rulemakings against current SEC/FINRA/FinCEN sources before advising.
Sections 206(1) and 206(2) of the Investment Advisers Act of 1940 are anti-fraud provisions that the Supreme Court (in *SEC v. Capital Gains Research Bureau*, 1963) interpreted as establishing a federal fiduciary duty for investment advisers. Section 206(1) prohibits employing any device, scheme, or artifice to defraud a client. Section 206(2) prohibits any transaction, practice, or course of business that operates as a fraud or deceit on a client. Together, they impose an affirmative duty of utmost good faith, full and fair disclosure, and an obligation to act in the client's best interest.
The SEC's June 2019 interpretation clarified that the IA fiduciary duty comprises two component duties:
Duty of Care:
Duty of Loyalty:
ERISA imposes a fiduciary duty on persons who exercise discretionary authority or control over a retirement plan or its assets, or who provide investment advice for a fee:
The Department of Labor has repeatedly sought to expand the ERISA fiduciary definition:
Several states have enacted or proposed their own fiduciary standards:
Standard III — Duties to Clients includes:
While CFA standards are not regulatory requirements, they represent industry best practices and are often referenced in enforcement actions and regulatory guidance.
The headline distinction: the IA fiduciary duty is a relationship-level, ongoing obligation (care, loyalty, monitoring), while Reg BI is a point-of-recommendation standard for broker-dealers serving retail customers. For the canonical side-by-side comparison table of the two standards, see the reg-bi skill ("Reg BI vs IA Fiduciary Duty").
Firms registered as both IA and BD must clearly disclose which capacity they are acting in for each transaction or relationship:
Scenario: An RIA that also manages proprietary mutual funds recommends those funds to advisory clients. The ADV Part 2A mentions the affiliation in general terms ("we may recommend affiliated products") but does not disclose the specific financial incentive or quantify the conflict. The proprietary funds charge 75 bps while comparable third-party funds charge 40 bps.
Compliance Issues: Fiduciary duty of loyalty violation. The disclosure is not "sufficiently specific" under the SEC 2019 Interpretation — a client cannot understand the magnitude of the conflict from boilerplate language. The 35 bps cost differential is a material financial incentive that must be specifically disclosed.
Analysis: The firm must: (1) specifically disclose that it receives revenue from proprietary funds, (2) quantify or clearly describe the financial benefit, (3) explain how this creates a conflict (incentive to recommend proprietary over cheaper alternatives), (4) obtain informed consent after meaningful disclosure, and (5) document that the recommendation is in the client's best interest despite the conflict. If the firm cannot demonstrate that the proprietary fund offers value justifying the cost differential, the recommendation may violate the duty of care regardless of disclosure quality.
Scenario: A 401(k) plan adviser recommends a fund lineup that includes revenue-sharing share classes when lower-cost institutional share classes of the same funds are available. The revenue sharing offsets the adviser's fees. Total plan cost is 1.2% when it could be 0.7% with institutional shares and a transparent advisory fee.
Compliance Issues: ERISA Section 404 prudent expert violation and potential Section 406 prohibited transaction. The fiduciary is not acting with the required prudence by selecting higher-cost share classes. Revenue sharing arrangements that benefit the adviser create a prohibited transaction unless covered by an exemption (such as PTE 2020-02).
Analysis: Under ERISA's exclusive benefit rule, the adviser must select the lowest-cost share class available unless a higher-cost class provides demonstrable additional value. Revenue sharing that reduces the adviser's visible fee while increasing total plan cost is a conflict that ERISA fiduciary duty requires to be resolved in favor of participants. The DOL has brought enforcement actions on this exact pattern. The adviser should use institutional share classes and charge a transparent advisory fee.
Scenario: A dual-registrant firm opens advisory accounts for financial planning clients but executes certain transactions (annuity purchases, insurance products) through the brokerage side. Client communications do not clearly distinguish which capacity the firm is acting in for each transaction. The firm applies Reg BI standards to annuity recommendations rather than fiduciary standards.
Compliance Issues: Failure to disclose capacity and potential application of the wrong standard. If the client reasonably believes they are receiving ongoing fiduciary advice across all aspects of the relationship, the firm cannot silently switch to a lower standard for selected transactions.
Analysis: The firm must: (1) clearly disclose at the outset which services are advisory (fiduciary) and which are brokerage (Reg BI), (2) provide specific notice when switching capacity for a particular transaction, (3) ensure the client understands the different standards that apply, and (4) document the capacity disclosure and client acknowledgment. The SEC has specifically warned dual registrants against "cherry-picking" the standard that benefits the firm rather than the client.
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take joellewis/fiduciary-standards from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.