GitHub guide
How to use the Anthropic financial services GitHub reference without creating workflow chaos
The repository is file-based and approachable, but teams still need a deployment path, connector map, and approval policy before putting it near client or fund workflows.
Use this guide when a technical lead, COO, or analytics team is deciding whether to install plugins, use Managed Agents, or build a governed wrapper around the reference templates.
Read the repository by layer
Start with the agent plugins to understand what each workflow owns. Then inspect the vertical plugins for reusable skills and commands. Finally, review managed-agent cookbooks if you need an API-controlled deployment.
Avoid treating every directory as equally urgent. The first pilot should use the smallest set of skills and connectors that can produce a measurable reviewer-approved output.
- Agent plugins: named workflows and bundled skills.
- Vertical plugins: reusable commands, methods, and connector settings.
- Managed-agent cookbooks: deployment wrappers and orchestration examples.
Keep connectors boring on day one
MCP connectors can be powerful, especially for market data, research platforms, and document stores. They also create governance work. Start with sources your team already licenses and logs.
The right first question is not how many connectors you can add. It is which connector materially improves the reviewer’s output quality without expanding the risk surface too quickly.
Translate open-source structure into firm controls
Map every agent action to a human owner. Decide who approves a model change, who signs a client-ready deck, who clears a KYC exception, and who owns support when a connector is unavailable.
This site’s Desk plan is designed around that first translation: workflow selection, output templates, approval boundaries, and checkout-led onboarding.
Common questions
Should we fork the repository directly?
A fork is useful for experimentation, but production use usually needs a controlled wrapper, firm templates, connector governance, logging, and reviewer policies.
Does the repository require a build step?
Most of the reference content is markdown, YAML, and JSON. The operational work is less about building assets and more about deploying the right workflow with the right controls.