footprint-entity-expert
Installation
SKILL.md
Footprint Entity Expert
Reference for Footprint WMS domain knowledge that isn't derivable from OData metadata alone — navigation chains, business-rule filters, weight calculations, and other context you'd otherwise have to reverse-engineer from existing reports.
This skill sits above schema-explorer and datasource-creator: it tells you which entities to explore and what the gotchas are, before those skills do the mechanical work of validating fields and generating configs.
When to use this skill
| Working on… | Use this skill? |
|---|---|
| A report or flow that queries Tasks, Shipments, License Plates, Inventory, Materials, Lots, etc. | Yes — start here before schema exploration |
A datasource over an Archived... entity (shipping or receiving history) |
Yes — archive entities have specific nav chains |
| A weight or unit-of-measure calculation (case weight, pallet weight, totals) | Yes — fixed vs catch weight branching is non-obvious |
| An app or report that has nothing to do with WMS data (custom org settings, generic dashboards) | No — this skill won't apply |
| A report on data the customer added themselves (custom Material extension fields, etc.) | Partial — use the entity references for the standard fields, then verify customer extensions with schema-explorer |
If you're not sure whether the data is Footprint-shaped, the connection's apiConnectionTypeName is a good signal: FootPrintApi → yes, anything else → probably no.