next-best-action

Finds the clients an advisor is quietly losing from their own book, ranking the households that have gone silent past their usual rhythm by how they felt last time, whether their sentiment was already falling, whether they stopped driving the conversation, and whether they have named another advisor. Says who to call first and how to open. Use whenever the user asks who is at risk, who has gone quiet, who they haven't spoken to in a while, who to call this week, or whether they are losing anyone — and for a re-engagement list, a brief on one household, or a draft re-engagement email. Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Reads one advisory client or household two ways — a fast temperature check on whether they are cooling, steady or warming, and a full behavioral profile covering what motivates them, what they are afraid of, how they decide, whether their stated risk tolerance matches their behaviour, and how engaged they have been — then a calibrated stance for the next conversation. Use whenever the user asks what a client is like, how to approach them, what motivates them, how a meeting went, what the mood is, why they won't commit, or whether a relationship is cooling or warming. Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Builds a client-ready Client Journey for one household — a five-stage lifecycle timeline marking where the family sits today, a relationship tree including beneficiaries never met, their outside professional team, a dated timeline of life events and turning points, and every motivator, worry and consequential fact on record with its corroboration and age — plus what they have never been asked that the rest of the book covers. Use whenever the user wants everything known about a household, a family tree or lifecycle report, who is who in a family, what is new on a client, or a comprehensive picture polished enough to walk a client through. Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Ranked pipeline of held-away asset opportunities from the advisor's own recent meetings — old 401(k)s, outside brokerage accounts, inheritances, business sale proceeds, real estate, spouse assets — grouped by household and marked new, raised again, nothing new since, task created, or client agreed. Use whenever the user asks what held-away or outside money came up recently, wants their consolidation pipeline or money in motion, mentions old 401(k)s or outside accounts, or says things like "run the radar" or "held-away opportunities". Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Prepares an annual or semi-annual household review from the last 12 to 24 months — goals then versus now, what changed in their finances and their life, the decisions taken, the commitments made, and the handoffs the review creates for the client's CPA, attorney and other professionals. Produces an advisor summary, and on request a client letter in a chosen tone, a client-facing review presentation on the firm's own template, and a brief for each outside professional. Use whenever the user is preparing for or writing up a client review, wants a year-in-review letter or a review deck, or asks what happened with a household this year, what they promised them, or who needs to know afterwards. Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Builds a household's full tax opportunity picture from every analyzed meeting on record, across two horizons — current-year items with deadlines (deferral capacity, a second plan nobody checked, taxable-account drag, giving structure, equity dates, education vehicles) and multi-year strategies 3-5 years out (conversion windows, drawdown sequencing, the survivor's position, business structure, property sales). Ranks by impact, cites the meeting each item came from, names the tax questions nobody has asked, and flags what the household raised that went nowhere. Use whenever the user asks about tax planning, tax opportunities or tax exposure for a client, wants a tax review or CPA handoff, asks what they are missing on someone's taxes, mentions Roth conversions, deferral capacity, tax drag, harvesting, charitable giving or equity comp timing, or asks what to cover before year end or tax season. Advisor intelligence, not advice. Requires Zocks MCP — will not run from transcripts, uploads, or any other source.

Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

First-run setup for the Snowflake to AIDP migrator. Finds or creates the one migration config file (snowmig-config.yaml), reads every field back with secrets masked, verifies Snowflake authentication by password, key-pair, programmatic access token or SSO, verifies the AIDP end, then smoke-tests the connection and reports the account, region, role and warehouse. Use the first time the migrator runs on a machine, or when any other stage fails with an authentication, connection or "no config found" error.

Measure Jetson DRAM/NvMap usage and verify before/after memory reclamation with live audit data.

Read-only PREVIEW of a Snowflake environment from the operator's machine - inventory of tables and views with row counts, byte sizes and column types, plus the census of objects that are not tables or views, table-maintenance state and security posture. Use ONLY when the user wants to look at an account without migrating it - answering what is in there, how big the tables are, what the security posture looks like. This is NOT the discovery step of a migration: a migration discovers inside AIDP as a workflow (runbook S6), because a laptop-side read leaves no log and no evidence on the platform. If the user asked to migrate, route to snowflake-migrator-overview and follow S1 through S12.

Manage and search AIDP audit logs — enable/disable auditing, set retention, and query audit-log entries for a DataLake. Use when the user asks about audit logging, who did what, compliance/retention of AIDP activity, or wants to search audit events. Self-contained — official `aidp audit` CLI preferred, `oci raw-request` fallback.