broker-record-reconciler

Reconcile broker records across Tally, Notion, Wix, and local data with provenance and conflict reporting.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/JFeimster/moonshine-capital-portal --skill broker-record-reconciler-jfeimster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: broker-record-reconciler
Source: https://github.com/JFeimster/moonshine-capital-portal/tree/main/skills/broker-record-reconciler
Command: npx skills add https://github.com/JFeimster/moonshine-capital-portal --skill broker-record-reconciler-jfeimster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Broker records drift across Tally intake forms, the Notion Partners CRM, Wix projections, and local repository data, creating duplicates, identity mismatches, and lifecycle inconsistencies that are risky to fix by hand. This Skill audits and reconciles those records without silently overwriting trusted values or bypassing operator-controlled lifecycle states. ## Core Features & Use Cases - Canonical identity matching: Matches records by partnerId, Tally submission ID, then normalized email, and flags identity, immutable-field, lifecycle, duplicate, and availability conflicts instead of guessing. - Field-level provenance and dry-run reports: Records every observed value, source, timestamp, normalization, and selection reason in a deterministic report before any change is made. - Authorized apply with verification: Performs only explicitly authorized writes through existing adapters, then re-fetches and verifies affected records. - Use Case: An operator finds two Notion pages for the same broker and a Wix record showing a different partnerId. Run a dry-run reconciliation to get a conflict report that retains the earliest canonical page, blocks the unsafe merge, and proves zero writes occurred. ## Quick Start Ask the agent to reconcile the broker records for a specific partner across Tally, Notion, and Wix in dry-run mode and produce a conflict and provenance report without making any changes.

Frequently Asked Questions about broker-record-reconciler

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

FAQPage Schema
How do I reconcile broker records across Tally, Notion, and Wix?▼

Run the reconciler in review or dry-run mode to fetch records from each source, match them by partnerId, submission ID, then normalized email, and produce a field-level report. Writes only happen in apply mode after explicit authorization.

How does duplicate detection work for Notion broker pages?▼

When multiple Notion pages resolve to the same canonical identity, the reconciler retains the earliest canonical page and flags later pages for human review and archival. It never deletes duplicates automatically.

Can reconciliation overwrite approval or lifecycle status in Notion?▼

No. Operator-imposed states such as suspended, rejected, hidden, and archived are protected during routine reconciliation. A Wix pending value normalizes to needs_review and never authorizes approval or publication.

What happens when Tally and Wix show different partner IDs for one broker?▼

The record is classified as an identity conflict and the merge is stopped. The report shows both identifiers, affected record IDs, and protected fields, requiring human review before any change.

Does the reconciler modify data during a dry run?▼

No. Dry-run mode calculates the exact proposed merge and field-level delta but attempts zero writes. The report explicitly states that no records were changed, and apply mode separately verifies writes by re-fetching records.