agentleFS
DataWithBaraaDataWithBaraa/claude-code-data-engineering-skills/skills/reconcile/SKILL.md

reconcile

Skill84 starsChanged 13 days agoMITView on GitHub

Use when two numbers that should agree do not, a report against its source, a rollup against its detail, two systems for the same table, to find where they diverge and why.

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close, brief and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • HermeticOrmusSkill

    close

    End-of-session ritual. Captures session state, updates auto-memory, writes a session summary, then exits the session cleanly.

    Also in 3 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 3 projects that use this

  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

  • nicolasestremSkill

    brainstorm

    Structured idea generation and solution exploration with systematic analysis.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • +1 more from anthropics

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After each cause, show what is left of the difference, and go on until it is zero or inside the agreed tolerance.

    line 20
  2. Distinctive:

    Never changes a number on either side.

    line 38
  3. Distinctive:

    Never calls it a rounding difference without showing the rows.

    line 39

“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Reconcile

The job: two numbers that should match, the places where they stop matching, and the reasons. It reads, it changes no number.

Input: the two sides, the report, query or table of each, and the number each one gives.

Steps

  1. Name the two sides: the query, the table and the filter of each, and the number each one gives.
  2. Make both sides comparable: the same grain, the same period, the same filters, the same currency and unit, the same time zone.
  3. Compare the totals, then split by the dimensions until a difference sits in one slice: a day, a source, a status, a key.
  4. In that slice, compare row by row: the rows only on one side, and the rows on both sides with different values.
  5. Name the cause: a filter, a join that drops or doubles rows, a late delivery, a type conversion, a rounding, a time zone.
  6. After each cause, show what is left of the difference, and go on until it is zero or inside the agreed tolerance.
  7. Say which side is right, with the proof from the source.
  8. Give the result as one web page.

Output

One HTML file: the two numbers on top, the difference, the drill-down from the total to the slices, the rows behind each cause, and what is left after each cause.

Reads

  • both sides, the data contracts, the pipeline SQL, the query logs

Writes

  • the web page only

Never

  • Never changes a number on either side.
  • Never calls it a rounding difference without showing the rows.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.