SkillAgentSearch skills...

data-consolidate

Joins the plant's scheduled exports and connector data into one working dataset — ERP items (NetSuite or Infor M3), sales orders, production work orders, purchase orders, inventory, routings and closed-job operation actuals; CMMS assets and maintenance work orders; and the MES, historian, quality an…

Install / Use

npx skills add anthropics/claude-plugins-official --skill data-consolidate

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

96/100

Category

Sales

Supported Platforms

Universal

Tags

Our assessment of data-consolidate

data-consolidate scores 96/100 on our quality scale, 2nd of 41 Sales skills we index (top 5%).

Its SKILL.md is 27 KB long, well organised into 17 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 47,209 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
30/30
Structure
17/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 3 days ago, so data-consolidate is actively maintained.
  • Our last check on 2026-11-14 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-14. Automated pattern scan on 2026-11-14. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

data-consolidate compared with similar skills

All 4 of these similar skills score higher than data-consolidate; compare them before choosing.

SkillScoreStarsUpdatedFormat
data-consolidate (this skill)by anthropics9647.2k3d agoSKILL.md
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md
designby nextlevelbuilder100149.0k6d agoSKILL.md

Frequently asked questions

How do I install data-consolidate?
Run npx skills add anthropics/claude-plugins-official --skill data-consolidate. The install tabs above show the steps for each supported agent.
Which AI agents does data-consolidate work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is data-consolidate safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is data-consolidate still maintained?
The repository was last updated 3 days ago, so data-consolidate is actively maintained.

name: data-consolidate description: "Joins the plant's scheduled exports and connector data into one working dataset — ERP items (NetSuite or Infor M3), sales orders, production work orders, purchase orders, inventory, routings and closed-job operation actuals; CMMS assets and maintenance work orders; and the MES, historian, quality and planning files landing in the Microsoft 365 export folder. Keys on part number, production work order, sales order, lot, asset and supplier, classifies every key that fails to match into one of eight mismatch classes, and proposes the correction rather than reporting a count, applying nothing without a yes. Runs file-only with no connector, or connector-only with no files. Use when someone says "pull the data together," "consolidate the exports," "build the dataset," "join production to the ERP," or "why don't these numbers match," and before any reporting or quoting skill runs." compatibility: "Requires none. Reads the ERP (Oracle NetSuite or Infor M3), a CMMS connector (Limble is the worked example) and the Microsoft 365 export folder when connected, and runs on files alone or connectors alone. Emits an XLSX dataset plus an HTML data quality report."

Data Consolidate

The foundation layer. The dataset this skill produces is where every data-dependent skill reads from by default, rather than going back to the raw sources — and it is the only place the sources are joined and their key mismatches classified.

"By default" is exact, not a hedge. Three skills also read a raw export, and they are right to: see ../../shared/contracts/consolidated-dataset.md, What this dataset is authoritative for. Nothing here carries a high-frequency sensor trace, and a normalized value is not always the value as recorded.

The reason it exists. The majority of real manufacturing data does not arrive through a connector. It arrives as a file. The plant already runs scheduled exports out of its MES, historian, inspection system and planning tool, usually into a shared drive for somebody's spreadsheet. This skill reads that folder plus the live connectors, joins everything on the identifiers the plant already has, and hands back one dataset with every unmatched record explained.

Quick start

"Pull last month's production together with the ERP."

→ Read the export folder; identify each file by name and header signature
→ Report each source's timestamp and coverage window before joining anything
→ Pull the ERP (NetSuite or Infor M3) and any live CMMS connector scoped to the same window
→ Normalize keys up the ladder, logging every rule that fires
→ Join around the five anchors: part, production work order, sales order, lot, asset
→ Classify every mismatch, propose each fix, apply nothing without a yes
→ Emit the dataset and the data quality report

Inputs

First, find the plant setup: from the task's own folder (never cd into the plugin), run python3 -I <this skill's folder>/../../shared/scripts/plant_setup.py find, do its setup_page_first step, then read the profile at profile_path and any rate at rates_path, per ../../shared/replies.md.

| Input | Source | Form | |---|---|---| | Item / part master | The ERP: NetSuite or Infor M3 | Connector | | Sales orders | The ERP | Connector | | Production work orders | The ERP | Connector | | Purchase orders and suppliers | The ERP | Connector | | Inventory positions | The ERP | Connector | | Routings — operations, work centers, setup and run standards per part and revision | NetSuite where manufacturing routings are licensed; else an ERP export or an Excel sheet dropped in. Infor M3 always takes the export | Connector, CSV / XLSX | | Operation actuals — setup and run hours per closed production work order and operation | NetSuite closed work orders where licensed, or Infor M3 work order operations; else an export or an Excel sheet | Connector, CSV / XLSX |

Which M3 call fills each row, and what M3 does not give, is ../../shared/erp-connectors.md. Read it before an M3 pull. | Assets and maintenance work orders | CMMS | CMMS connector, else the maintenance export | | Actual production output | MES export to the M365 folder | CSV / XLSX | | Downtime events | MES or historian export to the M365 folder | CSV | | Inspection / quality results | Quality system export to the M365 folder | CSV / XLSX | | Planning / schedule | Planning tool export to the M365 folder | CSV / XLSX |

Four of those have no connector and never will. File-only is the designed path, not the degraded one. Routings and actuals are often a spreadsheet someone keeps, and that is a complete input.

The machine class to work center and cell map, the time units, and anything else this skill reads about machining come from ### Machining data in the ## Plant context block, which onboarding writes. Where that section is absent, say so once and carry on without it.


Workflow

Step 1 — Discover

Read the configured export folder. Identify each file by name pattern and header signature, and say what each one was identified as.

Report anything unrecognized rather than guessing. A file that cannot be identified is named and set aside, not silently skipped and not hopefully parsed.

Routings and operation actuals are recognized by header, not by hope. A routing carries part, operation sequence, work center and a setup and run standard; an actuals file carries a production work order, an operation and the hours booked against it. The signatures are in reference/join-keys.md, Routings and operation actuals. A file that looks like either but misses a signature column is unrecognized and named, not loaded with the gap filled.

When the folder holds months of daily files, do not read everything. Offer the choice — latest drop, or a named date range — and state which was used.

onboarding owns the folder path, the file inventory and the refresh cadence — read them from the ## Plant context block rather than asking. If no profile exists, ask for the path once, carry it through the run, and offer onboarding so the next run does not ask again.

If the folder is empty, missing, or there are no files at all, do not stall on discovery. Ask for the date window once, then go to step 3 and run connector-only. In an unattended run (Chain 3, triggered host-side — see ../../shared/scheduling.md) there is no one to ask — use the production-day range from the ## Plant context block instead, per Step 2's fallback, and say the window was chosen rather than inherited from a file. That path is specified under Degradation.

Step 2 — Freshness check

Record every source's last refresh timestamp and the window it covers, and put that in front of the user before any joining or any figure.

Refuse to join sources whose windows do not overlap meaningfully, and say so plainly rather than producing a dataset full of manufactured mismatches. The rule is ../../shared/absent-is-not-zero.md; a stale export is the normal failure here, not the exotic one.

A source timestamp later than the run time is a critical freshness finding. A created, last-modified or transaction date after now means the source's clock is ahead or its data was seeded with future dates; either way none of its as_of values can be trusted. Say so in the banner, by source and with the latest such timestamp, give no "data as of" or age for that source, and do not use its dates to set a window. The rows stay, flagged future_timestamp. A due, promised or delivery date in the future is a commitment, not this finding.

Where the windows overlap only in part, state the overlap in dates and offer exactly two choices, named as such: (1) narrow the join to the overlap, 2026-08-01 to 2026-08-31, or (2) wait for the next export and re-run. Never one choice, and never narrow silently: "I've scoped every total to August" is a decision the user did not make. Whichever they pick, every total below is labelled as scoped to that window.

The window applies by entity, not to every row alike. Narrowing scopes activity records only. Open commitments are kept by status, and reference history by a lookback, because those are exactly the records later skills need. The three kinds, and the lookback, are in reference/join-keys.md, Date windows by entity. Say in the report which kind each tab was scoped as.

Step 3 — Pull connector data

The ERP (NetSuite or Infor M3) and any live CMMS connector, scoped to the same date window as the file exports. Pulling a wider window than the files cover creates Class 7 mismatches out of nothing.

If there are no file exports, the window is the one the user just gave, or the production-day range from the ## Plant context block. Scope the connector pull to that, and say that the window was chosen rather than inherited from a file.

Never hard-fail on a missing custom field. Customers configure NetSuite heavily and field names vary by account. Fall back, and report what could not be read. An Infor M3 search stops at about 30 rows without saying so: pull in slices until one returns fewer, per ../../shared/erp-connectors.md.

Scope every pull by the profile's ### ERP scope, per ../onboarding/reference/erp-scope.md: this plant's subsidiary, locations and parts. With no scope set, say scope not set as a gap, and ask, in so many words: "Which of these items are your plant's parts?", showing what a filter would catch ("10 of 515 items start PN-"). Never pick a filter silently, and never answer "how many parts" with one figure until the scope is answered. Where the scope says production work orders are MES only, take work order identity from the MES export and say so once; never report every MES row as unmatched against an ERP that holds none.

When a connector and an export cover the same entity, check key overlap before joining them. Zero or low overlap means they are not two views of one system: ask which is authoritative (or read the profile's Source of truth line), join only that one, and set the other aside by name. Never merge them, and never report every record of one as unmatched against the other.

Step 4 — Normalize keys

Apply the normalization ladder in order — trim, case, punctuation, leading zeros, revision suffix. Read reference/join-keys.md for the ladder, the six keys and their sources of truth.

Compare on the normalized form and store the original verbatim. Every normalization that fires is logged and reportable. A missing part prefix (4471B against PN-4471-B) is part of rung 3 only where exactly one part on the parts tab matches once its prefix is dropped; the ladder says which prefix it used.

Until a fix is approved, the rows it would join are not joined. They carry join_status: proposed_normalization, and only a yes turns them into normalized. A downstream skill reading the status alone must never take a proposal for a join.

Step 5 — Join

Build the dataset around the anchor entities: part, production work order, sales order, lot, asset. Tabs, columns and required fields are fixed by ../../shared/contracts/consolidated-dataset.md — that schema is the plugin's stable interface and custom-connector maps new systems onto it, so it changes deliberately and with a version bump, never incidentally.

Keep production work orders and maintenance work orders distinct — the two systems use the same word for different records.

Detect unit-of-measure columns and flag a mismatch rather than summing across it. Each versus box of twelve, inches versus millimetres. A total computed across two units is not a total. A units conflict is an integrity flag on the row, carried on the dataset and named in the report: refuse a single total for that key, report each quantity in its own unit, and compute no conversion — not "about 6,200 each if box12 means twelve", not a speculative factor

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars47.2k
CategorySales
Updated3d ago
Forks4.9k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions