if you’re building anything in claude code the ten financial services plugins anthropic shipped today are worth reading even if you never touch finance, the architecture is a masterclass in how to structure agent workflows Here’s what they actually built ,each template (pitch builder, model builder, kyc screener, valuation reviewer etc) is a bundle of: → skill files defining trigger conditions and workflow steps → governed data connectors to external sources (factset, s&p capital iq, pitchbook, morningstar, moody’s, daloopa) → subagents handling specialized pieces independently → slash commands exposing specific actions to the user → per-tool permissions and audit logging the whole thing is on github and it’s structured so you can fork and customize, drop your firm’s terminology, processes, formatting standards, branded templates. Claude then works like it was built for your team specifically the pattern worth highlighting for anyone building in claude code: they’re using skill files as the core control mechanism, a SKILL.md with clear trigger conditions and workflow steps telling claude when and how to activate specific capabilities. This is domain-agnostic architecture implemented for finance. I’ve been applying the same pattern to two completely different workflows in claude code and seeing anthropic formalize it in their official plugins validates the approach: First is a content production pipeline where claude orchestrates visual production through magichour and kling’s api (face swap,video gen, image editing all through one integration point) and programmatic editing through remotion. Each step has its own skill definition and the orchestration logic lives in a central workflow file so the subagent pattern from the finance plugins maps directly, one subagent handling script generation, another handling visual asset production, another handling assembly. Second is an outbound sales automation where claude orchestrates prospecting through fuseai’s api and routes leads based on intent signals, same architectural pattern, skill files defining triggers and connectors to external data The kyc screener template is structurally almost identical to what i built for lead qualification. The microsoft 365 integration matters for claude code users too , context now carries between excel, powerpoint, word, and outlook automatically. the pitch builder outputs comps in excel, pitchbook in powerpoint, cover note in outlook. if you’ve been hacking around cross-application context with manual export/import steps this is the native solution practical next steps are read the github repo, study how they structured skill files and subagent definitions then fork the financial analysis plugin as a starting template and the rebuild the skills and connectors for your own domain.The architecture transfers directly regardless of industry. anyone else poking through the repo?what patterns people are pulling out for nonfinance use cases submitted by /u/acedric
Originally posted by u/acedric on r/ClaudeCode