Moterra Official Anthropic partner
Pricing About us
Get a quote
← All writing
AI deployment

Claude Skills for financial institutions: what to build, and how to govern it

Moterra Moterra 28 September 2026 13 min read
Claude Skills for financial institutions - what to build, and how to govern it

Financial institutions already run on written procedures: how a credit memo is built, what a suitability report must contain, what a complete KYC file looks like. Claude Skills turn those procedures into something Claude follows the same way every time, with the rule and the source cited at each step.

This guide is for banks, lenders, insurers, wealth and asset managers. It covers which skills to build by business line, one worked example, the controls a regulator will expect, and where the model should run.

Short answer

A Claude skill packages a procedure, its checklist and its calculations into a folder Claude loads when the task matches. In a financial institution the best first skills are high-volume procedures with a written standard: credit memos, KYC file checks, complaint responses, suitability reports, promotion reviews and underwriting triage. Each skill drafts; a named person decides. Skills need an owner, a test set and a review date, and the model they run against should sit where your outsourcing and data rules allow, often your own AWS or Azure account.

What a skill is, in a financial institution's terms

A skill is a procedure manual, its checklist and its calculator, in one folder.

Anthropic introduced Skills in October 2025. Each skill has a SKILL.md file with a name, a description and the steps, plus optional reference files, such as a credit policy or a rule checklist, and scripts for anything that must be exact. Claude reads only the short description until a request matches, then loads the full procedure. A desk can hold dozens of skills without any of them getting in the way.

Why skills fit regulated finance

Four properties make skills a better fit for regulated work than prompts or chat.

01 Consistency. The same procedure runs for every customer, which is what consistent outcomes under the Consumer Duty require.
02 Evidence. A skill can require a rule reference and a source link on every point, so the output arrives with its own audit trail.
03 Judgement separated from calculation. Ratios, dates, thresholds and required wording run in a script that gives the same answer every time. Claude handles the drafting and reasoning.
04 Control. Skills are files: owned, versioned, tested and withdrawn like any other controlled procedure.

Skills, Projects and connectors: three layers

Skills are one of three things that turn a Claude licence into a working tool. Each answers a different question.

ProjectsConnectors and retrievalSkills
AnswersWhat does this team know?Where is the data?How do we do this task?
What it holdsStanding instructions and documents for one team or clientLinks to live systems through MCP, and search over document librariesA procedure, its checklist, templates and scripts
LoadedInside that projectWhen a tool is called or a document is retrievedOnly when the task matches
ExampleA Credit Risk project with the credit policy and sector notesFactSet, the loan file in SharePoint, the KYC record in SQLDraft the credit memo in committee format

Put simply, Projects provide the context, connectors provide the data, and Skills provide the method. A credit analyst working in the Credit Risk project asks for a memo; a connector pulls the financials; the credit memo skill decides how the memo is built. Remove any one layer and the output falls back to general knowledge.

For internal documents, retrieval means Claude searches the firm's own policies, precedents and procedures and quotes the passage it relied on, so a question such as "what does our standard facility agreement say about change of control?" is answered from the document, not from memory. For live systems, an MCP server acts as a permission-scoped bridge: Claude can query the CRM or the loan system, and where configured take an action, only within the user's role.

What Anthropic built for financial services

In July 2025 Anthropic launched Claude for Financial Services, a Financial Analysis Solution aimed at analysts, researchers and investment teams.

The solution brings market feeds and internal data into one interface, with every claim linked back to its source document for verification. It combines four parts:

01 The models. Anthropic reports that Claude 4 models led other frontier models as research agents on Vals AI's Finance Agent benchmark. In a FundamentalLabs Excel agent, Claude Opus 4 passed five of seven levels of the Financial Modeling World Cup and scored 83% accuracy on complex Excel tasks.
02 Claude for Enterprise and Claude Code, with expanded usage limits. For analysis through market events and deal deadlines, and in Claude Code for modernising trading systems, building proprietary models, automating compliance, and running Monte Carlo simulations and risk models.
03 Pre-built MCP connectors. To the financial data providers and enterprise platforms listed below.
04 Implementation support. Onboarding, training and best practice through Anthropic and consulting partners including Accenture, Deloitte, KPMG, PwC and Slalom.

The data connectors

Box Secure document management and data room analysis.
Daloopa Fundamentals and KPIs from public filings, disclosures and presentations.
FactSet Equity prices, fundamentals and consensus estimates.
Morningstar Valuation data and research analytics.
PitchBook Private capital market data for sourcing, diligence and benchmarking.
S&P Global Capital IQ financials, earnings call transcripts and research workflow.
Databricks and Snowflake Analytics and data platforms holding the firm's own structured and unstructured data.

Anthropic lists the target workflows as due diligence and market research, competitive benchmarking and portfolio deep dives, financial modelling with full audit trails, investment memos and pitch decks, and portfolio monitoring. On data, it states that by default customer data is not used to train its generative models. Claude for Enterprise and the solution are also available through AWS Marketplace, so procurement can run through an existing AWS agreement.

What institutions have reported

AIG said its early rollouts compressed the timeline to review business by more than five times, while data accuracy rose from 75% to over 90%.

AIG, via Anthropic

Bridgewater's AIA Labs used Claude for the first versions of its Investment Analyst Assistant, generating Python code, building visualisations and iterating through financial analysis.

Bridgewater AIA Labs, via Anthropic

Commonwealth Bank of Australia describes its Anthropic partnership as central to work on fraud prevention and customer service. The pattern across all three is the same: the model is strong on its own, and the gains come when it is pointed at the firm's data with a defined method. That method is what a skill encodes.

Skills by business line

The strongest candidates have weekly volume, a written standard and a qualified reviewer at the end.

Banking and lending

Credit memo drafting Assemble the memo from financials, facility terms and the credit policy, with ratios calculated in code. Decision stays with · Credit officer
Covenant monitoring Extract covenants from facility agreements and test headroom against the latest management accounts. Decision stays with · Relationship and credit teams
KYC file completeness Check a client file against the customer due diligence checklist under the Money Laundering Regulations 2017 and list the gaps. Decision stays with · MLRO's team

Retail, wealth and advice

Suitability reports Draft the report from the fact-find against COBS 9 and 9A, with Consumer Duty outcomes evidenced. Decision stays with · Adviser
Complaint final responses Draft the response to the firm's template, track the eight-week DISP deadline and cite the relevant facts. Decision stays with · Complaints handler

Insurance

Submission triage Summarise a broker submission against underwriting guidelines and list missing information. Decision stays with · Underwriter
Claims file summary Summarise the file against policy wording, flag exclusions and list open questions. Decision stays with · Claims handler

Markets, research and asset management

Comparable company analysis Pull peers through the licensed data connector, apply the desk's multiples in a script, link every figure to its source. Decision stays with · Analyst
DDQ and RFP responses Answer due diligence questionnaires from the approved policy and fund library only, flagging anything without an approved source. Decision stays with · Client service and compliance

Compliance and risk

Financial promotion review Check drafts against COBS 4 and the Consumer Duty, cite the rule for each issue, confirm required risk warnings in code. Decision stays with · Compliance
Regulatory change mapping Break a new policy statement into discrete obligations and map each to the internal policy it touches. Decision stays with · Policy owner

A worked example: the credit memo skill

What a credit memo skill looks like on disk:

credit-memo/SKILL.md
---name: credit-memodescription: Drafts a credit memo for a new or renewed facilityfrom financial statements, facility terms and the credit policy.Use when asked to prepare, draft or update a credit memo.--- # Steps1. Run scripts/ratios.py on the financials (leverage, ICR, DSCR).2. Compare each ratio with reference/credit-policy.md limits.3. Draft sections in templates/memo.md order.4. List every policy exception with its clause reference. # Rules- Every figure links to its source document and page.- Never recommend approval. End with: For credit committee.

The script calculates leverage, interest cover and debt service cover the same way on every file. The policy file holds the limits. Claude drafts the narrative, flags exceptions against the policy and stops short of a recommendation. The credit officer gets a consistent first draft; the committee gets a memo where every number can be traced.

Connecting skills to internal data

A skill supplies the method. The data arrives through connectors.

The market data connectors above cover the research desk. The procedures in this guide also need the institution's own records.

Internal systems matter as much: the loan file in SharePoint, the KYC record in a SQL database, the complaint in the case system. Moterra AI Bridge connects these, and connectors inherit the permissions already in place, so a person sees exactly what they could already see.

Why most rollouts stall, and where skills fit

Buying licences gives staff access. It does not change how the institution works.

A common picture: seats bought, a few enthusiasts using Claude daily, and little else changed. Three gaps explain most of it.

01 No configuration for the business. Claude arrives as a general tool with no Projects, no skills and no role context, so staff see little difference from what they had.
02 No connection to the data. Without retrieval over internal documents and connectors to live systems, Claude cannot answer questions specific to the institution with confidence.
03 No structured training. Access without guided, role-specific practice rarely becomes a daily habit. Training by team, on that team's own tasks and skills, is the most reliable driver of use.

The order matters. Discovery comes first: which workflows cost the most senior time, what data exists, and which regulatory and information-security constraints apply. Regulated constraints such as information barriers, data scoping and audit trails are designed into the architecture at that stage, not added after the build. Skills sit at the centre of the configuration layer, because they are where the institution's own procedures live.

The controls a financial institution needs

A skill runs code on client data. Six controls make it defensible.

01 Accountability. A skill drafts; a named person decides. Write it into the skill, and map AI use to the relevant senior manager under SM&CR.
02 Model risk. Record material skills in the model and tool inventory, with an owner, a test set of real cases and a review date. Firms applying PRA SS1/23 already have the framework.
03 Script review. Read every bundled script before release. Look for network calls, file access outside the task and hidden instructions.
04 Information barriers. Under SYSC 10, each side of the wall gets its own skills and connectors, assigned by identity provider group.
05 Record keeping. Every skill run is logged against the named user, alongside the source documents it used.
06 Change control. A new rule or policy triggers a new skill version, tested against the same cases before it ships.

Where the model runs

The skill is the same everywhere. What changes is who processes the data.

Anthropic-hosted planYour own cloud
Model runs inAnthropic's infrastructureYour AWS or Azure tenant, your chosen region
Skills reach staff byUpload or admin provisioningMDM, by identity provider group
Audit trailAdmin console, Compliance APICloudTrail or Azure Monitor, into your SIEM
Encryption keysAnthropicYou, via KMS or Key Vault

Outsourcing rules in SYSC 8, PRA SS2/21 on outsourcing and third-party risk, and DORA for EU entities all ask who processes the data, where, and how the firm exits. Running Claude in the institution's own AWS or Azure account keeps processing inside a cloud relationship that has already been through that review.

That is what Private Claude Cowork by Moterra deploys: Claude Desktop and Cowork configured against your own tenant, skills delivered as Cowork Plugins by identity group, and connectors through Bridge. Moterra manages the deployment; it does not host the data. More on the regulatory side in Deploying Claude under GDPR and DORA.

The first 30 days

Start with three skills in one business line, and prove them before scaling.

01 Week 1 - choose. Pick three procedures with volume, a written standard and a named reviewer. Collect twenty past cases for each.
02 Week 2 - build. Write the skills, move calculations into scripts, and test against the past cases with the reviewer.
03 Week 3 - pilot. Release to one team. Log every draft the reviewer changed materially, and fix the skill, not the output.
04 Week 4 - approve and publish. Record owner, test results and review date in the inventory, then provision by group.

After a month the institution has three tested, owned skills and a repeatable approval route for the next ones.

Next step

Bring the three procedures you would turn into skills first.

Thirty minutes on which skills to build, the controls around them, and where the model runs.

Get a quote

Frequently asked questions

What are Claude Skills?

Claude Skills are folders containing a SKILL.md file of instructions, plus optional scripts, templates and reference documents. Claude reads each skill's short description up front and loads the full procedure only when a task matches. For a financial institution, a skill is a written procedure, its checklist and its calculations, packaged so Claude applies them the same way every time.

Which skills should a bank or insurer build first?

Procedures with weekly volume, a written standard and a named reviewer: credit memo drafting, KYC file completeness checks, complaint final responses, suitability report drafting, financial promotion review and underwriting submission triage. Each produces a draft for a qualified person to approve.

Can Claude Skills make regulated decisions?

A skill should not. The right design produces a draft, a check or an evidence pack, and states in the skill that approval stays with the accountable person, whether an adviser, underwriter, credit officer, MLRO or compliance. That keeps accountability where the Senior Managers and Certification Regime places it.

How do Claude Skills fit model risk management?

Treat each skill as a governed tool: a named owner, version control, a test set of real cases, and a review date. Scripts that calculate figures should be tested like any other end-user computation. Firms applying PRA SS1/23 typically record material skills in the same inventory as other models and tools.

How do skills respect information barriers?

Through assignment and permissions. Skills and connectors are provisioned by identity provider group, so each side of a SYSC 10 barrier gets its own set, and connectors inherit the permissions already in place. Every model call is logged against the named user.

What is Claude for Financial Services?

Anthropic's Financial Analysis Solution, launched in July 2025. It pairs Claude for Enterprise and Claude Code with expanded usage limits, pre-built MCP connectors to providers including FactSet, S&P Global, PitchBook, Morningstar, Daloopa, Box, Databricks and Snowflake, and implementation support. Customer data is not used for model training by default.

Can financial institutions run Claude Skills in their own cloud?

Yes. Skills are files read by the client, so they work in Claude Desktop and Cowork configured against Claude on Amazon Bedrock or Microsoft Foundry in the institution's own account. Model calls stay in that tenant and region, which is how many firms meet outsourcing expectations under SYSC 8, PRA SS2/21 and DORA.

What results have financial institutions reported with Claude?

Anthropic cites AIG compressing its business review timeline by more than five times in early rollouts, with data accuracy rising from 75% to over 90%, and Bridgewater's AIA Labs using Claude for the first versions of its Investment Analyst Assistant. Anthropic also reports Claude Opus 4 scoring 83% accuracy on complex Excel tasks in a FundamentalLabs agent.

Sources · Anthropic Skills announcement · Claude docs, Agent Skills overview · Anthropic, Claude for Financial Services · Vals AI Finance Agent benchmark · FCA Handbook COBS 4, COBS 9, DISP 1, SYSC 8, SYSC 10 · PRA SS1/23, SS2/21 · Money Laundering Regulations 2017 · Checked 28 Sep 2026

Moterra Moterra Official Anthropic partner. Deploys Claude inside companies' own AWS and Azure tenants.

Related reading

All articles →
AI deployment Claude Cowork on 3P vs Claude Enterprise: what's the difference? The two organisation-wide routes side by side: where data sits, who administers it, and what each costs to run. Security and compliance Deploying Claude under GDPR and DORA What UK and EU regulated companies need from a Claude deployment: residency, keys, and the contractual position.
Moterra Moterra Official Anthropic partner

Moterra is a private AI deployment company. We help businesses deploy Claude inside their own AWS or Azure environment, connect it to the tools they already use, and keep it secure and governed, so everyday processes get faster.

ISO 27001 / 42001 SOC 2 Type II GDPR · DORA
© 2026 Moterra. All rights reserved. Privacy PolicyTerms and Conditions
Build your Private Claude Cowork plan. Pick users, support, and MCP plugins. We show the monthly cost, Year 1 TCO, and how it compares to Enterprise editions of Claude, ChatGPT and M365 Copilot. Get this quote straight to your inbox when you are done.
01 Users Everyone who gets Claude Cowork and Code.
{{ usersLabel }}
5500+
02 Support Standard is included in every plan.
{{ pTierNote }}
03 MCP plugins Optional. 4 or more get 20% off the plugin total.
04 Commitment A term waives the one-time setup fee.
{{ pTermNote }} Setup {{ pSetupTag }}
Your quote {{ monthlyHeadline }} {{ effectiveLine }}
{{ managedLabel }} {{ managedPrice }} Priority support {{ supportPrice }} {{ pluginsLabel }} {{ pluginsPrice }} Monthly recurring {{ monthlyTotal }} Infrastructure costs + tokens (via AWS/Azure), est. {{ awsPrice }} One-time setup {{ setupPrice }} Year 1 total {{ yearOneTotal }}
Vs. alternatives · per user / month
Private Claude by Moterra {{ effectivePerUser }} in your cloud (AWS or Azure) {{ moterraCatch }}
Claude Enterprise {{ claudePrice }} {{ claudeSaving }} + tokens billed separately, often €50-200+/user with usage · 20-seat minimum
ChatGPT Enterprise {{ gptPrice }} {{ gptSaving }} price not published, quote-only · ~150-seat minimum · annual prepay
M365 Copilot Enterprise {{ copilotPrice }} {{ copilotSaving }} + existing M365 E3/E5 licence required · annual prepay

Indicative figures. Moterra includes private deployment in your own AWS; others are shared-cloud SaaS. Final quote confirmed in writing by your Moterra account manager.

Book a demo

Thirty minutes, and the hardest questions first.

Tell us where you are and a Moterra specialist will confirm a time within one working day.

Goes straight to your sales team · no marketing list · no follow-up sequence

✓

{{ qfInboxText }}

Get your quote by email

We'll send it to you and loop in our team.

Turnstile
Verification failed, please reload the page and try again. Please fill in company, name and work email. Something went wrong. Please try again or email sales@moterra.ai directly.
✓

{{ qfSalesDoneText }}

Talk to sales

Leave your details and we'll reach out with your exact setup already in hand.

Turnstile
Verification failed, please reload the page and try again. Please fill in company, name and work email. Something went wrong. Please try again or email sales@moterra.ai directly.