freight-domain-glossary_skill

This skill helps you understand freight brokerage terminology and workflows across loads, tenders, carriers, stops, and accounts in laneweaverTMS.
  • Go

3

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill linehaul-ai/linehaulai-claude-marketplace --skill freight-domain-glossary

  • SKILL.md5.8 KB

Overview

This skill is a concise glossary for freight brokerage terminology used with laneweaverTMS. It clarifies entities, identifiers, financial terms, status workflows, equipment types, operational and regulatory terms to help teams read and act on loads, tenders, carriers, stops, and invoices. Use it as a quick reference to reduce ambiguity and speed decision-making in operations and engineering.

How this skill works

The glossary maps core domain concepts to canonical IDs, typical formats, and lifecycle states used in laneweaverTMS. It explains relationships between accounts, tenders, loads, carriers, and stops, and documents financial calculations, common accessorials, equipment types, and status enums. Use it to translate business language into consistent fields, database conventions, and operational outcomes.

When to use it

  • Onboard new operations, sales, or engineering team members
  • Integrate or debug laneweaverTMS data pipelines and APIs
  • Define or validate database schemas, enum values, and ID formats
  • Standardize communications between brokers, carriers, and customers
  • Model workflows for automation, dispatch, or billing processes

Best practices

  • Use canonical ID formats (L-XXXXXX, T-XXXXXX) when searching or generating load/tender records
  • Store monetary values as NUMERIC(10,2) and use enum types for statuses to enforce consistency
  • Record carrier identifiers (MC, DOT, SCAC) as text and validate against issuing authorities when possible
  • Capture accessorials explicitly on load financials to compute gross and net profit accurately
  • Map status transitions in code to the documented lifecycle to avoid invalid state changes

Example use cases

  • Convert an incoming EDI 204 tender into a T-XXXXXX record and follow tender->planned->load workflow
  • Reconcile invoice status changes from draft -> sent -> partial_payment -> paid for A/R reports
  • Filter carriers by SCAC/MC/DOT and apply regulatory checks (CSA score, HOS/ELD compliance)
  • Automate dispatcher alerts when a load moves from dispatched -> at_origin -> in_transit -> at_destination
  • Calculate gross profit by subtracting carrier_rate from customer_rate and adjust for accessorials to get net profit

FAQ

Loads use L-XXXXXX and tenders use T-XXXXXX; these are generated by triggers in laneweaverTMS.

How are monetary fields represented in the database?

All monetary values are stored as NUMERIC(10,2) to preserve precision for billing and settlement.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
freight-domain-glossary skill by linehaul-ai/linehaulai-claude-marketplace | VeilStrat