next-best-action
Design and implement next-best-action engines that surface proactive, prioritized recommendations to advisors based on portfolio, life, market, and compliance events. Use when the user asks about building event-driven advisor alerts, designing trigger logic for portfolio drift or large cash movements, prioritizing competing actions across a book of business, routing NBA recommendations to the right team member, measuring NBA acceptance rates, or automating compliance-driven actions like annual review reminders. Also trigger when users mention 'next best action', 'advisor nudges', 'proactive outreach', 'what should I do for this client', 'event-driven triggers', 'action queue', 'client contact gap', 'RMD reminder', or 'advisor productivity tool'.
What this skill does
# Next-Best-Action — Event-Driven Advisor Recommendations ## Purpose Enable the design, evaluation, and implementation of next-best-action (NBA) systems for financial advisory practices. This skill covers the full NBA lifecycle — from event detection and trigger design through action identification, prioritization scoring, advisor delivery, workflow integration, and effectiveness measurement. It provides frameworks for building proactive, data-driven advisor productivity tools that surface the most valuable action an advisor should take for each client at any given time, replacing reactive and manual task management with intelligent, personalized recommendations. ## Layer 10 — Advisory Practice (Front Office) ## Direction prospective ## When to Use - Designing or evaluating an NBA engine for an RIA, broker-dealer, or wealth management platform - Building event-driven triggers that detect portfolio, life, market, compliance, or practice events - Defining an action library and recommendation logic for advisor outreach - Designing prioritization and scoring models to rank competing actions - Routing NBA actions to the appropriate team member (advisor, CSA, operations, compliance) - Selecting delivery channels and designing advisor nudge formats - Integrating NBA recommendations with CRM, portfolio management, financial planning, and trading systems - Implementing compliance-driven NBA actions (annual reviews, disclosure delivery, suitability re-certification) - Measuring NBA effectiveness (acceptance rate, time-to-action, revenue impact, compliance completion) - Evaluating vendor NBA platforms or building custom NBA capabilities ## Core Concepts ### Next-Best-Action Framework Next-best-action is an advisor productivity and client service methodology that analyzes client data across systems to surface the single most valuable action an advisor should take for each client at any given time. The concept originates in CRM and marketing automation — industries that have long used event-driven recommendation engines to guide customer-facing personnel toward high-value interactions — but its application in wealth management addresses a distinct set of challenges: advisors managing hundreds of client relationships cannot manually monitor every portfolio, life event, compliance deadline, and practice touchpoint across their entire book of business. NBA differs fundamentally from traditional task management. Traditional task management is reactive and manual: advisors create their own to-do lists, respond to inbound client requests, and rely on memory or periodic reviews to identify outreach opportunities. NBA is proactive and data-driven: the system continuously monitors client data across custodial feeds, CRM records, financial plans, compliance calendars, and market data, automatically identifying situations that warrant advisor attention and recommending specific actions with supporting context. The core components of an NBA system are: - **Event detection** — Continuous monitoring of data sources to identify triggering events (portfolio drift, large cash movement, life milestone, compliance deadline, market dislocation). - **Action identification** — Mapping detected events to a catalog of recommended actions (schedule review, propose rebalancing, discuss tax-loss harvesting, update beneficiaries). - **Prioritization** — Scoring and ranking competing actions across all clients to ensure advisors focus on the highest-value activities given limited time. - **Routing** — Directing each action to the appropriate person based on role, expertise, relationship, and availability. - **Delivery** — Presenting recommendations through the channels advisors actually use (dashboard, mobile notification, email digest, CRM task). - **Tracking** — Recording action outcomes (accepted, deferred, rejected, completed) to close the feedback loop and improve future recommendations. ### Event Detection and Trigger Types The quality of an NBA system depends on the breadth and reliability of its event detection. Events fall into five categories, each requiring different data sources and detection logic. **Portfolio events** are detected from custodial data feeds, portfolio management systems, and market data: - Drift beyond threshold — A client's actual allocation has deviated from the target model beyond the firm's tolerance band (e.g., equity allocation at 72% vs. 65% target with a 5% tolerance). Requires real-time or daily position data and model assignment. - Large cash deposit or withdrawal — A significant cash movement (typically defined by absolute amount or percentage of portfolio) has occurred. Detected from custodial transaction feeds. A $200,000 deposit into a $1 million account signals an investment opportunity; a $200,000 withdrawal from the same account may signal a liquidity event requiring plan reassessment. - Concentrated position — A single holding has grown to exceed a concentration threshold (e.g., 10% or 15% of portfolio value), whether through appreciation, additional purchases, or stock compensation vesting. Detected from position-level holdings data. - Tax-loss harvesting opportunity — Unrealized losses in taxable accounts exceed a significance threshold, particularly near year-end or after market declines. Requires lot-level cost basis data and market prices. - Required minimum distribution (RMD) due — A client with a traditional IRA or inherited IRA is approaching or has reached an RMD deadline. Requires account type data and client date of birth. RMD deadlines are absolute (December 31 for most, April 1 of the following year for the year the owner turns 73). - Margin call — A client's margin account has breached maintenance requirements. Requires margin balance and equity data from the custodian. Margin calls are time-sensitive and typically require same-day or next-day resolution. **Life events** are detected from CRM data, client-reported information, and public records: - Birthday milestones — Age-based financial triggers: 59-1/2 (penalty-free IRA withdrawals), 62 (early Social Security eligibility), 65 (Medicare eligibility), 70-1/2 (qualified charitable distributions from IRAs), 73 (RMD beginning age under SECURE 2.0 for those born 1951-1959). Detected from client date of birth in CRM. - Marriage, divorce, death of spouse — Major life transitions requiring comprehensive financial plan review, beneficiary updates, account re-titling, and potentially revised investment strategy. Typically detected through advisor-reported CRM updates or client-initiated contact. - New child or grandchild — Triggers discussions about education savings (529 plans), life insurance review, estate plan updates, and beneficiary designation changes. - Job change or retirement — Income changes, employer benefit transitions (401k rollover), stock option/RSU vesting acceleration, and potential shift in investment time horizon and risk profile. **Market events** are detected from market data feeds, portfolio analytics, and research systems: - Sector or asset class drawdown affecting client holdings — A significant decline in a sector or asset class in which the client has meaningful exposure. Requires mapping client holdings to sectors and monitoring sector-level returns. - Interest rate change impacting fixed income allocation — Significant rate movements that affect the duration risk, yield, or relative value of a client's fixed income holdings. Particularly relevant for clients with large bond allocations or approaching income-distribution phase. - New fund or product launch replacing a current holding — A lower-cost, better-performing, or more tax-efficient alternative to a fund currently held by clients. Detected through product research and comparison analytics. **Compliance events** are detected from compliance calendars, CRM activity logs, and regulatory data: - Annual review overdue — The client has not received a formal portfolio or suitability review
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.