post-meeting

Turns a client meeting into a CRM note, action items and opportunities, drafted from Zocks, a Wealthbox meeting summary or a transcript you paste. It finds the household, checks the CRM so nothing is logged twice, and shows everything in one table for your approval before writing it to Wealthbox or Redtail. Afterwards it can file the meeting record in Google Drive.

WHEN TO USE

SCOPE

USE FOR

Log a client meeting without writing the note yourself.
Turn what you promised the client into CRM tasks.
Catch opportunities mentioned in passing, such as a maturing CD or an inheritance.
File the meeting record in Google Drive.

NOT FOR

Emailing the client: send any follow-up message through the compliance skill first.
Meetings held only in Zoom: Zoom is not a source it reads.

This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.

In this document (6)

Post Meeting

Turn a client meeting into a CRM note plus a confirmed set of follow-ups and opportunities — the write-up, to-do chasing, and opportunity-spotting advisors would otherwise do by hand, done for them, with the advisor approving every write before it happens. This is next-best-action: doing the follow-up, not drafting an email for the advisor to send. If the advisor wants something sent to the client, that goes through /compliance — this skill's default path is the CRM, not a client-facing message.

Inputs

Required: the meeting itself — identified by household/client name, or by whatever meeting metadata a connected source supplies. Pull the meeting's content in this order, stopping at the first that's available:

Zocks AI results — the meeting's AI-generated summary and extracted items, if Zocks is connected. Fall back to the raw transcript (also from Zocks) for direct quotes when the summary is ambiguous about wording.
Wealthbox meeting summary — when Zocks isn't connected, Wealthbox's notetaker exposes a summary of the meeting (not a raw transcript). Use it as-is.
Pasted transcript — if neither connector is available, ask the advisor to paste the transcript.

Zoom is not a supported source yet — do not offer it or imply it's coming.

Infer the household and the meeting date rather than asking by default: from the transcript itself, from Zocks meeting metadata (date and meeting ID, when present), or from the advisor's connected calendar. Only ask the advisor to identify the household or supply a date if none of those resolve it — never show a date picker as a first resort. Once you've inferred a date, put it on the note preview in Step 2 so the advisor can correct it if it's wrong.

Once the household and meeting are identified, don't ask "should I start?" — pull the meeting content per the waterfall above and go. The approval gate in this skill is on the write batch in Step 4, not on starting the work.

Workflow

1. Identify the household

Query the household's CRM by the client/household name. If more than one connected tool could try to solve this for the household, ask the advisor once which is the book of record — per the Ask-Once, Then Route Convention — rather than guessing, and use that one for the rest of this workflow, including the Step 5 write. Offer to help the advisor save the choice using the Personalization Convention so they aren't asked again next session. If the advisor mentions a second CRM or notes source later in the workflow, that's the same question again before anything from it gets merged in — and if two sources ever disagree on a material fact, stop and ask rather than writing a footnoted or averaged version back to the CRM.

Disambiguation rule: never proceed on a name match alone. If more than one household matches, show the advisor the candidates (name + household + masked email or last-activity date) and ask which one is correct before touching any record — logging a meeting against the wrong household is a privacy incident, not a minor mistake. Confirm identity even on a single match if anything about the context (household, recent activity) doesn't line up with what the advisor said.

Follow the Connector Placeholder Convention: if the CRM's tools aren't available in this session, say "This is where I'd search [system] for this household once that connector is built," then ask the advisor to confirm the household manually and continue.

Whatever the CRM record turns up here — prior notes, open tasks, past meetings — is auxiliary context for identifying the household and spotting duplicates in Step 3. It is never the source of this meeting's content; that always comes from the waterfall in Inputs above, with Zocks AI results as the primary source when connected.

2. Draft the meeting note

Draft the note (the meeting content pulled via the Inputs waterfall, plus the inferred meeting date/type) and show the advisor what will be written, with the inferred date called out so it's easy to correct. Getting this right before writing matters more here than for most writes — CRM notes are never edited in place, only replaced by deleting and recreating them.

3. Identify action items and opportunities

Read the meeting content for two distinct things and list them back to the advisor separately:

Action items — commitments the advisor made or next steps that were agreed to (e.g., "I'll send the updated plan," "let's set up a call about the 529").
Opportunities — things mentioned in passing that could grow or protect the relationship (e.g., "a CD maturing next month," "mentioned an inheritance," "unhappy with a held-away account"). These are signals from this meeting only, not a full CRM opportunity review — call out that a deeper look (a dedicated opportunity-review pass) is a separate step if the advisor wants one.

Only include things actually said in the meeting content — never infer a commitment or opportunity that isn't there, and label anything uncertain as a possibility rather than a fact.

Dup-check before proposing writes: Zocks (the product, separately from its MCP) may already export its own summaries, tasks, and opportunities into the CRM. Check the CRM for tasks/opportunities already logged against this household around the meeting date — at both grains, the household record's own items and each person contact's (household-linked items are invisible to contact-only lookups) — before drafting new ones, and drop anything that's already there rather than proposing a duplicate.

4. Show the batch for approval

Present everything from Steps 2–3 as one schema-shaped table, not prose, and ask for a single confirmation on the whole batch rather than approving items one by one:

Type	What	When	Who	Notes
Note	(note preview, with inferred date)	meeting date	household	—
Task	action item text	due/target date if known	owner (usually the advisor)	—
Opportunity	opportunity description	—	—	any metadata the connected CRM exposes (e.g. estimated size, stage)

The advisor can approve all, some, or edited versions of any row.

5. Write what's approved

For whichever rows the advisor approves, create the corresponding CRM record using that CRM's own entities — Wealthbox's Note/Task/Opportunity objects, or Redtail's note/activity/opportunity calls — rather than assuming a generic mapping (e.g. Salesforce custom fields) that may not exist for the connected system. Confirm back with a short summary of what was logged.

6. Offer to file the record in Drive

After the CRM writes are done, if Drive is connected, offer to file the meeting record (as markdown) there too. If Drive isn't connected, skip this step silently — never hold up the CRM writes on it.

Output

The meeting note, action items, and opportunities are written directly to the CRM per the approved batch — that's this skill's primary output, not a document.
If filing the record to Drive, file it as markdown. Don't create a .docx/.pdf/.xlsx version unless the advisor asks for one.

Out of Scope (for now)

Creating a new household/contact when no match is found — flag it to the advisor instead.
Editing any existing contact field (name, address, etc.) noticed in the meeting content — flag it instead.
A full opportunity-analysis pass against existing CRM records — this skill only surfaces what's in this meeting.
Sending anything to the client. If the advisor wants to send a follow-up message, route it through /compliance — this skill's default path is the CRM, not a client email.
Trade execution.

Important Notes

Every write pauses for advisor approval, gated through the single batch in Step 4. Never create anything the advisor hasn't seen and confirmed.
Never fabricate meeting content, action items, opportunities, or client details. If the meeting content is ambiguous about whether something was a firm commitment or a real opportunity, ask rather than assume.
Treat the meeting content as confidential client data — it may contain financial, health, or family details beyond the meeting's stated purpose.

This skill ships inside the Claude for Financial Advisors plugin. Listed package contents include 6 agents and an MCP server. Installed components and skill versions may vary by AI tool.

Run this outside your AI tool, using Node.js 22.20.0 or newer. Skills CLI 1.7.2 skips skill selection; prompts cancel installation without an interactive terminal. If choosing Project when asked about installation scope, open your project's folder before running this.

Install checklist

Check selected tools if a picker appears; Claude Code may be unchecked under Additional agents. ↑/↓ moves, Space toggles selections, Enter confirms.
Without a tool picker, check Installing to: for your intended tool. Stop if it names a different tool.
If asked, choose Symlink (Recommended) for shared files or Copy to all agents for separate copies; review the summary before confirming installation.
Install the find-skills skill? defaults to Yes, adding another skill for all projects. Choose No if you don't want that extra installation.

Skills CLI 1.7.2 sends install data to skills.sh by default, including the source, skill names, target tools and file details; GitHub sources are reported only when GitHub confirms the repository is public, while other remote sources can also be reported. Confirmed-public GitHub sources also trigger a security-audit request. Before installing, set the environment variable DO_NOT_TRACK=1 or DISABLE_TELEMETRY=1 to disable both.

npx skills add anthropics/claude-for-financial-advisors --skill "post-meeting" --full-depth

After installing for Claude Code, open it in the installation project if you chose Project; Global makes the skill available across projects on this computer. Once Claude Code loads the skill, its description helps Claude decide when to use it.

If installation created a top-level skills folder that did not exist when your Claude Code session started, run /reload-skills in that session. Run it again after later changes in that folder.

What's inside

Files included with this skill.

View on GitHub

Same repository

alts-brief
Prepare a meeting-ready alternative-investments brief for a client, household, IRA, trust, or named account before a review — pulls the alts book from iCapital or Addepar (positions, NAV vs. commitment, called and unfunded amounts, contributions/distributions/subscriptions/redemptions, lockups, and the platform's own IRR/TVPI/DPI/RVPI) and sits it beside the liquid book and IPS target from the connected portfolio system (Orion Connect, Addepar, or Envestnet), then flags cash needed for capital calls, alts % vs. target, concentration, unfunded concentration, and stale as-of data. Cites the source platform on every figure and keeps disclosures on the page. Does not recommend funds, forecast NAVs/IRRs, or simulate allocation changes. Triggers on "alts brief", "/alts-brief", "prep the [client]'s alts review", "what's going on with [client]'s PE/private investments", "how's [client] doing on their alts", or any request to review a household's alternative investment positions before a meeting.Read full description
compliance
Review any client-facing message or material (emails, letters, newsletters, social posts, website copy, presentations, performance reports, proposals) for compliance with SEC rules that govern investment advisers — the Marketing Rule (206(4)-1), fiduciary duty / antifraud provisions (206), Books and Records (204-2), and Reg BI where broker-dealer activity applies. Produces a pass/flag/fail markup, required disclosures, a books-and-records scratch-pad entry, and an archiving handoff reminder. Triggers on "compliance check", "/compliance", "is this compliant", "review this before I send it", "can I say this to a client", "check this email/post/deck". Use it whenever an advisor asks to check, review, or look over anything before it goes to a client or prospect — "check this before I send it", "look this over before it goes out" — even a routine note, because deciding that a message needs no changes is part of the review, not a reason to skip it.Read full description
estate-and-tax-brief
Prepare a meeting-ready estate and tax brief for a household — opens with what was discussed and actioned since the last meeting (Wealthbox/Redtail/Salesforce), pulls the estate plan from Wealth.com (structure, key documents and whether each is signed, balance sheet) plus the prior-year tax look-back and that year's tax constants, and cross-checks it against how accounts are titled and beneficiaried at the custodian and portfolio platforms (Schwab, Orion/Addepar, iCapital) — surfacing unfunded trusts, titling mismatches, and beneficiary gaps as a prioritized flags list. The only write is creating advisor-approved follow-up tasks in the CRM (optional, approved first). Never drafts trust language, gives legal advice, retitles an account, or changes a beneficiary. Triggers on "estate brief", "estate meeting brief", "estate and tax brief", "estate plan review for [client]", "check [client]'s trust funding", "are [client]'s beneficiaries up to date", or "does [client]'s estate plan match their accounts".Read full description
portfolio-rebalance-review
Run a portfolio review for a client or household — performance pulled from Orion, allocation drift analysis vs. IPS or model portfolio, model-portfolio mapping, rebalance preparation with tax-aware rebalance opportunities to consider, and a rebalance rationale memo for the compliance file. Triggers on "portfolio review", "/portfolio-rebalance-review", "drift analysis", "rebalance [client]", "how is [client]'s portfolio positioned", "rebalance rationale", or "map [client] to a model".Read full description
pre-meeting
Prepare a complete client review meeting prep document for a financial advisor, for whatever timeframe the review covers (quarterly, annual, ad hoc). Given a household name or email and a timeframe, pulls CRM context (Salesforce/Redtail/Wealthbox), portfolio data (Orion/Addepar/Envestnet-Tamarac), estate & tax status (Wealth.com), meeting notes (Zocks or CRM), recent correspondence (Gmail/Outlook), and the household's plan snapshot (MoneyGuide), then assembles a meeting-ready prep doc with agenda, talking points, and action items. Triggers on "pre meeting", "/pre-meeting", "prep for [client]", "quarterly review prep", "get me ready for my meeting with [client]", or "client meeting tomorrow".Read full description
prospect-intake
Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".Read full description

Post Meeting

Inputs

Workflow

1. Identify the household

2. Draft the meeting note

3. Identify action items and opportunities

4. Show the batch for approval

5. Write what's approved

6. Offer to file the record in Drive

Output

Out of Scope (for now)

Important Notes

One preparation step required

What's inside

More skills

alts-brief

compliance

estate-and-tax-brief

portfolio-rebalance-review

pre-meeting

prospect-intake