Parcel Package Tracking

**Judgement:** A focused, practical skill for users already in the Parcel ecosystem who want to programmatically list and add deliveries. It’s well-scoped and appears technically straightforward, but entirely dependent on the external Parcel service and a valid `PARCEL_API_KEY`. **What it does well:** - Covers the core Parcel flows: listing deliveries (recent/active), adding new ones with details and optional push confirmation, and discovering carriers. - Clear CLI interface with explicit parameters and example commands, making it easy to wire into automations. - Reasonably low risk in terms of destructive actions—it mostly reads data and creates tracking entries. **Risks & limitations:** - Requires a secret `PARCEL_API_KEY`; mishandling this key could expose a user’s delivery history and shipment information. - Limited to the documented actions (`list`, `add`, `carriers`); more advanced Parcel features (e.g., rich status insights, webhooks) do not appear to be exposed. - Reliability and performance are tied to Parcel’s API availability and rate limits, which are outside this skill’s control. **Recommended scenarios:** - Assistants that help users keep track of personal deliveries or quickly add a new shipment right after purchase. - Workflow automations that integrate order systems or email parsers with Parcel for tracking consolidation. - Developer or power-user setups where Parcel is already the primary package-tracking app and a CLI/API hook is needed to tie it into broader tools.