access-policies
Build the access_policies value — the granular, IAM-shaped way to allow or deny add-in features
Analyze a bond's relative value vs yield curves and credit spreads with scenario stress testing
> /plugin marketplace add anthropics/financial-servicesHow it fires
How this command gets triggered: by you, by Claude, or both.
/analyze-bond-rvContext preview
What this command does when you run it.
Analyze a bond's relative value vs yield curves and credit spreads with scenario stress testing
description: Analyze a bond's relative value vs yield curves and credit spreads with scenario stress testing argument-hint: "<ISIN, RIC, or CUSIP> [vs benchmark]"
> This command uses LSEG bond pricing, yield curves, credit curves, and scenario analysis tools. See [CONNECTORS.md](../CONNECTORS.md) for available tools.
Perform relative value analysis on one or more bonds by combining pricing analytics, yield curve context, credit spread decomposition, and rate shock scenarios.
See the **bond-relative-value** skill for domain knowledge on spread frameworks and rich/cheap assessment.
Ask the user for:
Call `bond_price` with the identifier(s).
Extract: clean/dirty price, yield, duration, convexity, DV01, currency.
If benchmark provided, price that too.
Call `interest_rate_curve` (list then calculate) for the bond's currency.
Interpolate at the bond's maturity to compute G-spread.
Call `credit_curve` (search by country/issuerType, then calculate).
Compute residual spread = bond G-spread minus credit curve spread at matching maturity. Positive residual = cheap; negative = rich.
Call `yieldbook_scenario` with parallel rate shifts: -100bp, -50bp, 0bp, +50bp, +100bp.
Extract price change and P&L under each scenario.
Present: bond summary table, spread decomposition (G-spread, credit spread, residual), scenario P&L table, and rich/cheap assessment.
If benchmark provided, include side-by-side comparison.
Lead with the rich/cheap assessment and supporting evidence. Follow with spread decomposition and scenario tables.
Reference agents, skills, and data connectors for the financial-services workflows we see most — investment banking, equity research, private equity, and wealth management.
Build the access_policies value — the granular, IAM-shaped way to allow or deny add-in features
Build the bootstrap endpoint — per-user MCP servers, skills, dynamic config
Azure admin consent URLs — one-time tenant approval for Entra SSO and Outlook Graph access
Diagnose deployment issues (stale config, connect failures, missing add-in)
Several manifest configurations require an Entra (Azure AD) app registration in **your** tenant rather than Anthropic's default multi-tenant app — because the…
Export a copy of a user's add-in chat history, skills, MCP registrations, and settings before a machine is rebuilt