ClawHub

qantas-freight-tracking

v1.0.1

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

⭐ 0· 60·0 current·0 all-time
by@sicl
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk971fr05tpgwp5my4vdb82yy8n83tj0h

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments