Xdcc Batch Express Query for Openclaw

The query engine uses the Python standard library. The guided registration flow requires Playwright; if it is unavailable, the skill reports the issue rather than silently bypassing registration checks. Use the bundled onboard.py entry point for the complete credential-check, onboarding, validation, and query workflow.

# First use: provide the customer's phone number and password for registration
python onboard.py --phone <customer-phone> --password <customer-password> --file orders.txt --output results

# Existing account or saved credentials: query a tracking-number file
python onboard.py --file orders.txt --output results

# Validate saved credentials without running a query
python onboard.py --validate-only

# Run the package's static self-test and build a ZIP distribution
python scripts/selftest.py
python scripts/package.py

The customer must personally complete SMS and slider verification. Do not ask for or store a full phone number when only the final four digits are needed for tracking. Keep API credentials out of source code and public documentation.

Credentials are stored in ~/.workbuddy/xdcc-credentials.env using these keys:

Tracking input can be supplied as a file with one NO or NO,TEL record per line, inline tracking numbers via --nos, or a phone-number mapping CSV via --telmap. A shared --tel value can be used as a fallback. Output supports JSON, UTF-8-with-BOM CSV for direct opening in Excel, and readable TXT reports.

Results include shipment state and description, pickup/dispatch/signing timestamps, pickup and delivery cities, courier details, time-span and timeout indicators, and tracking events such as TraceList, LastTrace, and Count. Aggregates cover status distribution, timeout totals, signing-time averages and peaks, courier distribution, and failures. Supporting documentation lives in references/api_reference.md, references/onboarding_guide.md, and references/SECURITY_AUDIT.md.