break-trace

Compare GL and subledger data to diagnose reconciliation breaks.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/Duzhenyang111/stock_money --skill break-trace-duzhenyang111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: break-trace
Source: https://github.com/Duzhenyang111/stock_money/tree/main/financial-services-main/plugins/vertical-plugins/fund-admin/skills/break-trace
Command: npx skills add https://github.com/Duzhenyang111/stock_money --skill break-trace-duzhenyang111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the root-cause analysis of reconciliation breaks, allowing users to quickly identify the source of discrepancies and take corrective actions.

Core Features & Use Cases

  • Trace Breaks: Automates the tracing of reconciliation breaks back to their source transactions.
  • Root Cause Analysis: Provides a detailed explanation of why the break occurred.
  • Automated Output: Outputs a structured report with the root cause, expected clear date, and action required.

Quick Start

Use the break-trace skill to analyze a reconciliation break identified by 'break_row_id'.

Frequently Asked Questions about break-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate root cause analysis for GL and subledger reconciliation breaks?

You can automate root cause analysis for GL and subledger reconciliation breaks by comparing data from both sources to identify discrepancies. This Skill traces breaks back to source transactions and outputs a structured report detailing the root cause and required corrective actions.

What is the best way to trace a reconciliation break using a break row ID?

Tracing a reconciliation break using a break row ID involves passing the ID to an automated diagnostic tool. This Skill processes the ID, queries the GL and subledger MCPs, and generates a structured diagnostic report with the expected clear date.

Do I need access to GL and subledger MCPs to diagnose reconciliation breaks?

Yes, you need access to both GL and subledger MCPs to diagnose reconciliation breaks. The Skill requires these MCP connections to query and compare the underlying data, enabling it to accurately identify the source of the discrepancies.

What is included in a structured report for a reconciliation break?

A structured report for a reconciliation break includes the identified root cause of the discrepancy, the expected clear date, and the specific action required. This provides clear diagnostic output for taking immediate corrective measures.

Can Python scripts be used for finance automation and break analysis?

Yes, Python scripts can be used for finance automation and break analysis. This Skill uses Python scripts for data processing, comparing GL and subledger data to automate the tracing and diagnosis of reconciliation breaks.