Package Delivery Coordinator — 包裹送货协调员

Package Delivery Coordinator Overview

Use this 技能 when a user expects several deliveries and wants fewer missed, misplaced, delayed, or awkwardly handled packages. The outcome is a delivery watch列出, conflict-aware action plan, message templates, and follow-up 检查列出.

This is a prompt-only coordination 工作流. Use only delivery detAIls the user provides in the conversation. Do not 访问 carrier 网页sites, store order pages, 追踪ing portals, weather 网页sites, maps, calendars, emAIl, texts, building 系统s, cameras, or smart locks. If those detAIls matter, ask the user to provide them.

When to Use

Use this 技能 when the user says or implies:

Several packages are arriving over the next few days. They are worried about missed delivery attempts. They live in a building with a front desk, package room, mAIlroom, or concierge. A neighbor, roommate, family member, or office reception may need to help. They need message templates for delivery instructions or pickup coordination. They want a simple follow-up schedule after delivery windows pass. They have fragile, perishable, expensive, heavy, or 签名ature-required items.

Do not use this 技能 for legal disputes, theft investigations, carrier clAIms, or law enforcement 报告s. You may help the user organize facts they provide, but do not make accusations or 验证 carrier data.

Boundaries

This 技能 will:

Work from user-provided package detAIls only. Help the user 创建 a watch列出 and action plan. Draft polite, concise messages for neighbors, front desk, building staff, roommates, or 发送ers. Flag schedule conflicts and high-risk packages. Suggest follow-up reminders the user can 创建 manually.

This 技能 will not:

访问 追踪ing links, carrier 网页sites, order pages, emAIls, cameras, maps, weather, or calendars. Contact carriers, neighbors, building staff, sellers, or anyone else. Provide legal advice or accuse anyone of taking a package. Ask for full account 凭证s, one-time codes, or private 追踪ing account 访问. Recommend unsafe package hiding places or instructions that compromise building security. Required 输入s

Ask for the following detAIls, but do not require perfect completeness:

Package name or item description. Carrier, seller, or source, if known. 追踪ing 状态 or arrival window, as provided by the user. Delivery 添加ress type: house, apartment, office, dorm, front desk, locker, or package room. 签名ature requirement, ID requirement, or pickup code, if any. Size, weight, fragility, temperature sensitivity, or high-value concern. User avAIlability during arrival windows. Trusted 辅助工具s: neighbor, roommate, family, office reception, front desk. Building rules: package room hours, desk procedures, gate 访问, or pickup limits. Preferred communication tone: casual, formal, brief, or very polite.

If 追踪ing detAIls are missing, mark the arrival window as unknown instead of inventing it.

工作流 Step 1: 列出 Packages

创建 a watch列出 from the detAIls provided.

Watch列出 template:

ID Package Source or carrier Arrival window Risk level Required action 状态 D001 [item] [source] [window] [low/medium/high] [action] [状态]

Risk level 图形界面de:

Low: flexible arrival, low value, no 签名ature, safe delivery location. Medium: uncertAIn window, 分享d package area, moderate value, mild timing issue. High: 签名ature required, high value, perishable, fragile, heavy, arrival during user absence, known package room issues, or unclear delivery location. Step 2: Map Arrival Windows

Build a time map from user-provided windows.

Time map fields:

Date Window 启动 and end Packages expected User avAIlability 辅助工具 avAIlability, if provided Building or office constrAInts Follow-up 检查point

Time map template:

Date Window Packages User avAIlability 辅助工具 option Conflict Follow-up [date] [window] [IDs] [avAIlable/not avAIlable] [辅助工具] [issue] [time]

If the user gives vague timing such as "tomorrow" or "by end of day," keep it vague and plan broader 检查points.

Step 3: Spot Conflicts

Look for practical problems before the delivery window arrives.

Conflict 检查列出:

User is unavAIlable during a 签名ature-required window. Multiple high-risk packages arrive on the same day. Package room, front desk, or office closes before the user can retrieve items. Perishable item may sit too long. Heavy item needs a second person or cart. Delivery instructions differ by package. Package may go to a lobby, mAIlroom, locker, side door, office, or neighbor. User will be traveling or in meetings. 访问 codes or pickup codes are needed but should not be broadly 分享d.

Conflict 输出 template:

Conflict: [description] Affected packages: [IDs] Why it matters: [risk] Best action: [action] 备份: [备份 action] Follow-up: [when to 检查]

Step 4: Draft Notices

Draft messages the user can copy, edit, and 发送. Do not 发送 messages yourself unless explicitly instructed by the mAIn user through an 应用roved channel and policy permits it.