account-truth

Reconcile account data from CRM, memory, and ledgers using HubSpot API.

3|Updated Jun 15, 2026
One-click install
npx skills add https://github.com/aura-farming/escc --skill account-truth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: account-truth
Source: https://github.com/aura-farming/escc/tree/main/skills/account-truth
Command: npx skills add https://github.com/aura-farming/escc --skill account-truth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires HubSpot API, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The account-truth skill solves the problem of ensuring that the data about an account across different systems (CRM, memory, and ledgers) is accurate and up-to-date.

Core Features & Use Cases

  • Account Data Reconciliation: Compares and reconciles account data from CRM, memory, and ledgers.
  • Identity Resolution: Links account identities across different data sources.
  • Data Accuracy: Ensures the accuracy of account data by providing a verified, read-only account truth.
  • Use Case: Before a QBR or handoff, use account-truth to verify the current state of the account across all relevant systems.

Quick Start

To get the account truth for a specific company, run the command: escc truth <account>

Frequently Asked Questions about account-truth

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

FAQPage Schema
Why does account data mismatch between CRM and ledgers?

Account data mismatches occur when CRM, memory, and ledgers update independently. Reconciliation compares these sources to identify discrepancies, resolving identities and providing a verified, read-only account truth for decision-making.

How do I reconcile account data across CRM and ledgers?

Account data reconciliation compares and aligns records from your CRM, memory, and ledgers to ensure accuracy. This skill retrieves and compares data across systems, resolving identities to provide a single verified account truth.

Do I need HubSpot API access for CRM data reconciliation?

Yes, HubSpot API access is required for CRM data retrieval during account reconciliation. The integration pulls account records from HubSpot to compare against memory and ledger data for identity resolution and accuracy verification.

What is the best way to verify account accuracy before a QBR?

Account data verification before a QBR involves running a reconciliation process to check the current state of the account across all relevant systems. This skill provides a read-only verified account truth to support data-driven decision-making.

Can I link account identities across different data sources?

Identity resolution links account identities across CRM, memory, and ledgers. By comparing data retrieval outputs from these distinct sources, the skill matches and unifies account records to ensure accurate cross-system data alignment.

When do I need account reconciliation for data accuracy?

Account reconciliation is needed when maintaining accurate account data across CRM, memory, and ledgers is critical. It is especially useful before account handoffs or Quarterly Business Reviews to verify cross-system consistency.