qantas-freight-tracking

Track Qantas Freight shipments by air waybill number and get origin, destination, shipper, consignee, pieces, weight, ETD, and latest shipment status.

Security Scan

The skill's instructions, requirements, and footprint are internally consistent with a simple Qantas Freight AWB-parsing/tracking helper and do not ask for unrelated credentials, installs, or privileges.

Purpose & Capability

Name and description (track Qantas Freight AWBs and report shipment fields) match the SKILL.md, which is purely parsing and presentation logic; no unrelated credentials, binaries, or installs are requested.

Instruction Scope

SKILL.md is narrowly scoped to extracting specific fields from an `awb` JSON structure and formatting results (including multi-AWB handling and edge cases). It does not instruct the agent to read files, environment variables, or system paths. One minor omission: the document assumes an `awb` response object is available (and states the endpoint is public) but does not specify how to fetch that data — this is a functional gap, not a security issue.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk installation profile (nothing will be written or executed on disk by the skill itself).

Credentials

No environment variables, credentials, or config paths are requested. The SKILL.md states the public endpoint works without auth; if your integration requires credentials, ensure you only provide service-appropriate keys.

Persistence & Privilege

Skill is user-invocable and not forced-always. It does not request persistent system presence or modification of other skills/configuration.

Assessment

This skill is an instruction-only parser for Qantas Freight AWB JSON responses and appears coherent. Before installing: confirm where/how your agent will fetch the AWB JSON (the SKILL.md assumes a public endpoint but gives no fetch instructions); verify the actual Qantas Freight API behavior (some endpoints require auth or have rate limits); avoid testing with sensitive or private AWBs; and ensure your agent is not configured to automatically forward parsed shipment data to external endpoints you don't control. If you will integrate with an authenticated API, provide only the minimal, service-specific credential and verify scope/permissions.

Freight Tracking

Step 1 — Parse Response

Extract from awb.shipmentSummary:

Field	Key
AWB	awb.awb
Origin	awb.shipmentSummary.origin
Origin name	awb.shipmentSummary.originStationName
Destination	awb.shipmentSummary.destination
Destination name	awb.shipmentSummary.destinationStationName
Total pieces	awb.shipmentSummary.statedPieces
Total weight (kg)	awb.shipmentSummary.statedWeight
Service	awb.shipmentSummary.product
Handling codes	awb.shipmentSummary.handlingCodes
Shipper	awb.shipmentSummary.shipperName
Consignee	awb.shipmentSummary.consigneeName
Latest stage	Key in awb.shipmentSummary.stageSummary with value "ACTIVE", strip STAGE_ prefix
Events	awb.shipmentHistory (chronological array)

Step 2 — Multiple AWBs

1. Pass up to 10 AWBs in the array
2. Show summary table with all results
3. Each row contains its own <details> expandable block

Edge Cases

• Empty response: AWB not found — return "AWB not found"
• Multiple AWBs: Loop through array, one <details> block per AWB
• No latest event: Fall back to last item in shipmentHistory

Notes

• AWB format: XXX-XXXXXXX (3 digits, hyphen, 7 digits) — enter with or without hyphen
• Public endpoint works without login/authentication
• Times are in airport local timezone (transactionDate) and UTC (transactionDateUtc)