break-trace Skill
Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break. Published by anthropics in financial-services.
Decision snapshot
Is this a fit?
Security review, Writing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · Apache-2.0 license
No specific cautions were detected. Review the source and requested permissions before installing.
What is break-trace Skill?
Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break. Published by anthropics in financial-services. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Writing
- Security review use cases
- Writing use cases
Declared skill metadata
- Source file: plugins/vertical-plugins/fund-admin/skills/break-trace/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use break-trace Skill
- Use it for security review.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: anthropics
- Repository: anthropics/financial-services
- Skill file: plugins/vertical-plugins/fund-admin/skills/break-trace/SKILL.md
What it does
Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why. Use after gl-recon has classified a break.
Skill instructions
Root-cause a break Given a single break row (key, GL values, subledger values, bucket, likely cause), trace it to source and produce a root-cause statement. Trace path 1. Pull the GL side — via the internal-gl MCP, fetch the journal entry or posting that produced this GL line: entry id, posting date, source system, batch id, preparer. 2. Pull the subledger side — via the subledger MCP, fetch the matching transaction: trade id, trade/settle dates, counterparty, source feed, FX rate used. 3. Diff the attributes — line up posting date, FX rate/date, account mapping, quantity sign, amount sign. The differing attribute is usually the cause. Cause → statement Write the root cause as a single sentence in the form "⟨side⟩ ⟨did what⟩ because ⟨reason⟩", e.g.: - "GL posted on settle date (T+2) while subledger posted on trade date — timing break, will clear on 2026-05-07." - "Subledger used WM/R 4pm rate; GL used Bloomberg close — FX break of 12 bps on the base amount." - "Security ABC123 maps to
Verified compatibility and discovery
Frequently asked questions
What is break-trace?
break-trace is a open-source AI agent skill with Copy skill directory. Root-cause a reconciliation break to its source transaction or posting — follow the audit trail from the break row back to the originating entry on each side and state what differs and why.
Who is break-trace best for?
break-trace is best for reusing agent instructions, scripts, and references, security review workflows, writing workflows.
How do I install break-trace?
Install or run break-trace using Copy skill directory. Check break-trace for the latest setup command.
Is break-trace actively maintained?
break-trace may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
