⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
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 the alts platforms, iCapital, Addepar and CAIS (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 portfolio platform (Orion Connect, Addepar or Envestnet), then flags cash nee
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Claude for Financial Advisors
A plugin from Anthropic that gives financial advisors a set of ready-to-run workflows for Claude Cowork that draw live data from the tools their firm already uses, by way of third-party connectors.
The plugin is a set of skills written as plain instructions (Markdown and JSON). It holds no client data: when an advisor runs a skill, Claude pulls what it needs from the connected third-party systems. The advisor must explicitly approve any action that writes back to an external system (e.g. CRM updates, client drafts). Claude gathers, organizes, summarizes, compares and presents information, while the advisor exercises judgment, makes the recommendation and gives the advice.
Educational and operational support for advisors; not investment, legal, or tax advice.
Maintenance status: Reference implementation. Not actively maintained or monitored, and not accepting contributions. Issues and pull requests may not receive a response. This project is provided AS IS, without warranty.
Skills
| Skill | What it does |
|---|---|
/onboarding | Guided first-run setup: learns the advisor's firm, priorities, and tech stack, then connects their tools and runs a sample demo. |
/pre-meeting | Builds a client review prep doc - snapshot, relationship signals, open items, portfolio review, planning topics, agenda, talking points. |
/post-meeting | Turns a meeting artifact or transcript into a CRM note. |
/compliance | Pre-checks client-facing material against SEC Marketing Rule, antifraud, books-and-records, and Reg BI; produces a findings table, suggested disclosures, and a clean redraft. |
/prospect-intake | Normalizes a prospect's statements into a summary, an analyst handoff, and a what-to-expect memo. |
/portfolio-rebalance-review | Reviews performance, drift vs. IPS or model, and model mapping; drafts a tax-aware rebalance plan for the advisor to evaluate, with alternatives on request, and a memo documenting the advisor’s rationale. |
/alts-brief | Meeting-ready read on a household's alternative investments, sized against the liquid book. |
/estate-and-tax-brief | Cross-checks the estate plan against actual account titling and beneficiaries; prior-year tax look-back; optional CRM follow-up tasks. |
Each skill pulls from whichever connectors are live and falls back to paste/upload when a system isn't connected. Every write to a client system pauses for advisor approval.
Connectors
| Connector | What it does |
|---|---|
| 55ip | J.P. Morgan Asset Management (55ip) extends tax transition technology to Claude, so advisors can evaluate the tax impact of moving a client's holdings into a new portfolio. |
| Addepar | Brings investment intelligence into Claude, giving advisors governed access to portfolio data, analytics and workflows across public and private markets. |
| BlackRock | Brings Advisor Center’s portfolio analytics, model portfolios, and investment research resources to advisors through Claude. |
| Black Diamond | Brings portfolio, performance, holdings and rebalancing data into Claude, so advisors can review their book, spot clients out of tolerance, surface tax loss harvesting opportunities, and generate client reports, tasks and rebalance sessions with their approval. |
| CAIS | CAIS opens its alternative investment platform to advisors in Claude, so they can query fund data, review manager and fund performance, and see a client's public and private holdings together. |
| Conquest Planning | Conquest brings its Strategic Advice Manager planning engine into Claude so advisors can create new client plans, review and apply strategies, update existing plans and prepare for client meetings all in one place. |
| Envestnet Tamarac | Brings portfolio and performance reporting, including reconciliation status, from Tamarac into Claude so that advisors can conduct household reviews, drift checks, and meeting prep. |
| FINNY | FINNY, the growth and prospecting platform, connects Claude to an advisor's campaign results by channel and sequence step, and lets advisors enrich prospect lists from their CRM, or upload new lists directly in Claude. |
| Flourish Financial | Flourish connects Claude to financial advisors’ books of business, enabling them to work with client information, check rates, manage invitations, and prepare for client meetings, all within Claude. |
| Franklin Templeton | Franklin Templeton provides publicly approved fund and share-class information in Claude, including performance, fees, NAV, holdings, distributions, and fund documents, along with its published market and investment insights. |
| iCapital | Brings a client’s alternatives book into Claude, with holdings and performance across private funds, so advisors can see NAV against commitments, unfunded capital, recent calls, and distributions alongside the liquid portfolio. |
| Invesco | Invesco brings portfolio intelligence and practice management insights into Claude through its Invesco for Advisors connector. |
| Jump | Jump, an AI platform for financial professionals, gives Claude client context (meetings, documents, tasks) and Jump-built skills that prepare next steps for the advisor’s review. |
| MoneyGuide | Brings a household's financial plan into Claude — net worth, probability of success, and goals. |
| MSCI | MSCI brings its proprietary data and analytics into Claude, so wealth firms can assess investment options across public and private markets, monitor performance, and evaluate rebalancing opportunities. |
| Nevis | Nevis, the AI platform for wealth management, draws on client information from meetings, documents, and communications to support meeting prep and follow-up in Claude. |
| Orion Advisor Solutions | Brings portfolio and performance reporting from Orion Connect, and client records from Redtail CRM, into Claude so that advisors can conduct household reviews, drift checks, and meeting prep. |
| Schwab | Brings custodial data from Schwab into Claude: accounts, balances, positions and their lots, transactions, and alerts. |
| Vanguard | Brings information on its model portfolios and advisor investment solutions into Claude, so advisors can draw on Vanguard's trusted research, portfolio construction, and asset allocation expertise when making decisions for clients. |
| Wealthbox | Connects Claude to client records and meeting history to power onboarding, meeting prep, and follow-up. |
| Wealth.com | Gives Claude a structured view of each client’s estate plan, including trust and will summaries, and the full balance sheet, so advisors can begin document review using an organized summary of available information instead of a binder full of documents. |
| Zocks | Brings Claude the client intelligence it captures from every conversation, including profiles, goals, life events, and commitments. |
These join other connectors already available in Claude, including Microsoft 365, Salesforce, Box, FactSet, S&P Global, Morningstar, and more.
The Claude for Financial Advisors plugin, which bundles advisor skills and connectors into a single install, has been tested with BlackRock, Charles Schwab, Addepar, Envestnet, iCapital, Orion, Wealthbox, Wealth.com and Zocks, and advisors choose which of these to connect during guided setup. Some partners also offer their own plugins: BlackRock is launching one for Advisor Center, joining existing plugins from S&P Global and LSEG.
Installation
claude plugin marketplace add anthropics/claude-for-financial-advisors
claude plugin install claude-for-financial-advisors
Contributing
This repo is not actively monitored (see the maintenance status above). CONTRIBUTING.md describes how the plugin is put together and the design rules to keep if you fork or adapt it, plus the CLA requirement in case a pull request is ever reviewed.
Security
To report a security vulnerability, see SECURITY.md.
**Securit
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
skills/alts-brief/SKILL.md46 KBa9dad67aeb99truncatedupstream ↗
Showing the inlined prefix. The rest is in the upstream file.
--- name: alts-brief description: Prepare a meeting-ready alternative-investments brief for a client, household, IRA, trust, or named account before a review: pulls the alts book from the alts platforms, iCapital, Addepar and CAIS (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 portfolio platform (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. 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. --- # Alts Brief Give an advisor a clear, meeting-ready read on a household's alternative investments: what's on platform, how it's tracking against their goals, and what needs attention — sitting alongside the liquid book so the advisor can see the whole household, not just the alts sleeve in isolation. ## Inputs Required: **client/household name**. Optional: an as-of/cutoff date if the advisor wants the "recent activity" portion of the brief anchored to a specific date rather than "latest available" (default: since the last brief, or trailing 12 months if this is the first one), and a specific fund or manager to focus on if they only want part of the book. **Identity grain:** alts are frequently held at a level *below* the household — an IRA, a trust, a single person, or one named account. Take the advisor's grain literally: "the Harrington IRA," "the Whitmore Trust," "Robert Harrington," or "the Northgate account" each mean that entity, not the whole household. Don't silently widen a named account up to its household, and don't narrow a household down to one account. **Disambiguation rule:** never proceed on a name match alone, the same as every other skill in this plugin — if more than one client, household, or account matches the name, show the candidates and ask which one before building anything on it. This skill reads no CRM, so the matching happens in the reads: dispatch them on the name and grain as the advisor gave them, and a read that finds several candidates or a different household returns `IDENTITY MISMATCH` with what it saw — that is when you show the candidates and ask. Never call a platform's tools yourself to check the name first: that call is a read, and reads are dispatched (Data Gathering below). Where no read matched the name — nothing connected, or nothing found — say in the brief that the name and grain are as the advisor gave them. Once you have the name and grain, **pull the alts book and the liquid/IPS picture in parallel** (Steps 1 and 2) — one missing source degrades only its own section, never the other. Before starting, tell the advisor what you're gathering and why, so a slow multi-source pull doesn't look like a silent hang. And once the client and grain are known, don't ask "should I start?" — narrate what you're doing and go; the approval gates here are the format conversion at the end and the /compliance recommendation, not permission to begin. ## Data Gathering — Steps 1 and 2 run at the same time Steps 1 and 2 read different systems and share no state. **Dispatch them as `claude-for-financial-advisors:source-extract` reads, one per platform, in a single message**: one `Agent(claude-for-financial-advisors:source-extract)` call per read, all in the same response, each in the foreground (`run_in_background: false`) so every block comes back as its call's result inside this turn: iCapital, Addepar and CAIS for the alts book (Step 1), Orion Connect and Envestnet for the liquid book (Step 2), with Step 2's fields added to Addepar's read because it serves both steps. The five go out every time, whatever you expect a platform to hold — with one exception: when your tool search finds tools for more than one of the liquid-book platforms, their Step 2 reads wait on the book-of-record question below, and every other read still goes in the first message. **Writing each dispatch is where you look for its platform's tools**: take their names from your own tool list, or, where they aren't there, from a `ToolSearch` by the platform's own name, and put every name you found into that dispatch exactly as written — the full name, never a prefix you guessed and never the platform's name in a tool's place — because a read calls only the tools you name, by exactly the names you give. **Asking a platform's assistant is a read.** A question put to a platform's own assistant reads that platform, even where the platform keeps the question in the advisor's own history, so it is never a reason to leave the platform unread. A dispatch hands its read every tool you found for its platform, never a shorter list and never a note to avoid one, and a read you finish inline works from the same list: which of them a read calls is for the read's own instructions and the platform's provider file to decide. Where you found none — not in your list, nothing from the search, or no `ToolSearch` offered in this session — that dispatch says so in their place, and names no status for the read to return: the read's own contract decides that, and the brief reports what it returned. That search decides what each read is handed, never whether it is dispatched — only the advisor's book-of-record answer below holds a read back — and it never stands in for a read's return: what the brief says about a platform comes from its read (below). Make it yourself, never through a general-purpose helper. Hand each the household identity as you have it, the one system that subagent is to query, the tool names you found for it or that you found none, the field schema under its step heading, and the window its step states for that read. **An alts platform the advisor asks you to read beyond those five** gets its own read the same way: one more `source-extract` dispatch in that same message, handed Step 1's schema and the tool names you found for it, and never read by you instead. Everything below about a read covers it, and Step 6's Sources line names it. Each returns a filled schema block. They do not summarize, flag, or size anything against the IPS target — Steps 3 and 4 are yours, and they need the raw figures, not a subagent's read of them. **A platform's part of the brief is written from its read's block** — its figures, each with any qualifier the source states on it (an estimate, "approximately", a range, positions valued as of different dates), its `NOTHING FOUND` line and its "— pending" cells alike — or from your own inline read where Finish every read below sends you there. There is no third source: a platform with neither has not been read, and your own tool search is not a read. **Finish every read in this turn.** A read whose dispatch errors, is refused because the concurrent-subagent limit is reached, returns `CANNOT CALL`, or hasn't come back by the time you would otherwise end your turn is yours to do inline — the same platform, the tools you found for it, the same schema — and its result goes into the brief exactly as a returned block would. Those four cases are the only times you call a platform's tools yourself before the brief is written, and each is something a dispatch did, so a platform you haven't dispatched has nothing to finish: never read one inline in place of its dispatch, ahead of it, or to check the name. A read you finish inline follows the plugin's provider file for its platform where there is one, as its dispatched read would: before your first call, list `${CLAUDE_PLUGIN_ROOT}/providers/`, and if it holds a folder named for thatREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/anthropics-claude-for-financial-advisors-skills-alts-brief.md