SF Express

Overview

Use this skill to help users with common SF Express tasks such as tracking shipments, understanding service levels, estimating timing or fees, and preparing to send a parcel.

Local Persistence

When the local CLI/runtime code is used, this skill may create and persist local data under:

• - INLINECODE0

- stores query history - stores shipment-subscription records - may store saved address records if those commands are implemented/used

• - INLINECODE1

- stores encrypted local files used by the privacy/storage helper

• - INLINECODE2

- stores a local encryption key file with mode 600

• - INLINECODE4

- may be created when the user runs privacy export

Only use persistence when it is necessary for the user's requested workflow. If the user asks about privacy, disclose these paths clearly.

Privacy Controls

The local CLI supports privacy operations:

• - privacy info — show local storage paths and stored-file info
• INLINECODE6 — clear local SQLite history/subscription data and encrypted local files
• INLINECODE7 — export local storage metadata to INLINECODE8

Workflow

1. 1. Determine the user's goal:

- track an existing shipment - estimate fee or delivery time - compare service types - find a nearby outlet or locker - prepare shipment details - review or clear local history/subscriptions/privacy data

1. 2. Ask for only the missing essentials, such as tracking number, route, package size, or urgency.
2. Give the most practical answer first.
3. If exact fee or timing cannot be confirmed, provide a cautious estimate and state assumptions.
4. If the task uses local runtime features that persist data, mention that local history/subscription/privacy files may be created under ~/.openclaw/data/sf-express/.
5. Do not claim to complete real shipping actions unless live tools are available and confirmed.