held-away-radar

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.

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.

Deep single-household analysis naming the one highest-value next action and proving why — unused tax space, a closing Roth conversion window, RMD and IRMAA sequencing, Social Security and survivor math, irreversible pension elections, tax drag, protection and estate gaps. Never the advisor's own open tasks read back. Shows the runner-ups it rejected and names who outside the firm has to act. Use whenever the user asks what to do for a client, the best move, the biggest opportunity, what they are missing with someone, or wants a household's situation analysed. For a household's full tax picture, tax-opportunity-scan is the skill. 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.

The HyperFrames CLI by job - scaffold, check, look at frames, edit the timeline, preview, render locally or in the cloud, publish, project history - plus reading its JSON and recovering from build or render failures.

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts, rollback, and production infrastructure. Applies to any framework agents-cli deploys (ADK, LangChain, ...). Part of the agents-cli skills suite. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), evaluation (use google-agents-cli-eval), or project scaffolding (use google-agents-cli-scaffold).

This skill should be used when the user wants to "create an agent project", "start a new ADK project", "build me a new agent", "add CI/CD to my project", "add deployment", "enhance my project", or "upgrade my project". Part of the agents-cli skills suite. Covers `agents-cli scaffold create`, `scaffold enhance`, and `scaffold upgrade` commands, template options, deployment targets, and the prototype-first workflow. Do NOT use for writing agent code (ADK projects: use google-agents-cli-adk-code) or deployment operations (use google-agents-cli-deploy).

This skill should be used when the user wants to "set up tracing", "monitor my agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring deployed agents, including ADK (Agent Development Kit) agents. Covers Cloud Trace, prompt-response logging, BigQuery Agent Analytics, third-party integrations (AgentOps, Phoenix, MLflow, etc.), and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment setup (use google-agents-cli-deploy) or API code patterns (use google-agents-cli-adk-code).

Deploy and operate apps on Prisma Compute with the Prisma 8 CLI. Use whenever the user mentions Prisma Compute, deploying or hosting a Prisma app, `prisma deploy`, `prisma dev module.ts`, Prisma Composer apps (`module.ts`, `compute()`, the `composer` section of `prisma.config.ts`), preview stages, deploy on push (`prisma git connect`, `prisma/cloud-deploy-action`), `prisma service` logs, versions, rollback, or custom domains, `project env`, `PRISMA_SERVICE_TOKEN`, regions, 504s, sleeping instances, or `waitUntil`; also when a project still uses the removed `@prisma/cli app deploy`, `prisma.compute.ts`, `defineComputeConfig`, `compute:deploy`, or `build logs` surface.

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".