Same-Day Pickup Run Sheet

Builds an urgent same-day pickup run sheet with stops, contacts, proof needed, timing windows, route order, and fallback notes.

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "Same-Day Pickup Run Sheet" with this command: npx skills add harrylabsj/same-day-pickup-run-sheet

Same-Day Pickup Run Sheet

Overview

Use this prompt-only skill when a user needs to pick up multiple items today from stores, lockers, offices, events, neighbors, friends, sellers, or family members.

The skill turns scattered pickup details into a same-day run sheet with contacts, proof needed, timing windows, stop order, fallback notes, and safety flags.

When to Use

Use this skill when the user says things like:

  • "I have to pick up several things today."
  • "Make me a pickup run sheet."
  • "Plan my errands before stores close."
  • "I need a same-day pickup route."
  • "Track what proof I need for each pickup."
  • "Help me organize pickups from stores and people."

Required Inputs

Ask for only the details needed to build the run sheet:

  • Each pickup item and priority
  • Pickup location name, address or area, and contact person
  • Opening hours, appointment windows, cutoff times, or handoff windows
  • Order number, claim code, ID requirement, QR code, receipt, authorization name, or other proof needed
  • Item size, weight, storage needs, fragile status, or vehicle constraints
  • Payment status and any remaining amount due
  • Contact method for each stop
  • Starting point, end point, hard deadlines, and available time today
  • Safety concerns, such as unfamiliar private meetup, late-night handoff, cash exchange, or heavy item

If exact addresses or travel times are missing, create a draft order and mark items that need verification.

Workflow

  1. List pickups. Create a complete inventory of items, locations, contacts, deadlines, and priority levels.
  2. Capture windows and locations. Note open hours, appointment windows, closing times, pickup counters, parking notes, and access instructions.
  3. Note proof needed. Record IDs, QR codes, order numbers, receipts, authorization names, payment proof, bags, carts, or loading help required.
  4. Flag risks and constraints. Identify late stops, unsafe meetups, cash handoffs, private residences, heavy or fragile items, cold storage, store closing risk, and missing details.
  5. Order stops. Arrange stops by hard deadlines first, then location cluster, opening hours, item constraints, and start or end point. If travel time is unknown, label the order as provisional.
  6. Add contact and fallback notes. Include who to call or message, what to ask, what to do if the item is unavailable, and when to skip or reschedule.
  7. Build the run sheet. Produce a stop-by-stop plan with arrival target, pickup proof, contact, item, status, and next action.
  8. Create a departure checklist. List essentials to bring before leaving.
  9. Create an end-of-run check. Confirm all pickups, receipts, photos, refunds, reschedules, and follow-up messages.

Output Format

Produce the run sheet with these sections:

  1. Same-Day Pickup Snapshot
    • Date
    • Start point
    • End point
    • Available time
    • Number of pickups
    • Highest-risk deadline
  2. Priority and Deadline List
    • Item
    • Location
    • Window or closing time
    • Priority
    • Risk if missed
  3. Ordered Stop Plan
    • Stop number
    • Target arrival time
    • Location and contact
    • Item to collect
    • Proof needed
    • Payment or loading note
    • Fallback if delayed or unavailable
  4. Proof and Packing Checklist
    • ID
    • QR codes or order numbers
    • Receipts or authorization notes
    • Bags, cart, straps, cooler, charger, cash limit, or other supplies
  5. Contact Scripts
    • Quick confirmation message before leaving
    • Delay message
    • Unavailable item message
    • Safe public meetup request
  6. Safety Flags
    • Unsafe or uncertain meetups
    • Public handoff recommendation
    • Bring another person or reschedule recommendation when needed
  7. End-of-Run Log
    • Picked up
    • Missing or rescheduled
    • Receipts saved
    • Photos taken
    • Refund or follow-up needed

Safety Boundary

  • Flag unsafe meetups, late-night handoffs, isolated locations, cash-heavy exchanges, suspicious seller behavior, and pressure to change locations at the last minute.
  • Suggest public handoff spots such as staffed stores, building lobbies, police-station exchange zones where available, or other well-lit public places.
  • Do not encourage speeding, distracted driving, unsafe parking, trespassing, bypassing access rules, or confrontation.
  • Do not ask for unnecessary private personal data. Use only pickup details the user provides.
  • Do not advise misrepresenting identity, authorization, payment, or pickup status.
  • If an item is unusually heavy, fragile, hazardous, temperature-sensitive, or legally restricted, ask the user to verify safe transport requirements and bring appropriate help or equipment.
  • If route times are uncertain, clearly mark the schedule as provisional and ask the user to verify travel time before leaving.

Quality Checklist

A strong result should:

  • Capture every pickup with contact, window, proof needed, and fallback
  • Prioritize hard deadlines and closing times
  • Mark missing details instead of inventing them
  • Include a stop order that can be followed today
  • Include proof, packing, and contact checklists
  • Flag unsafe meetups and suggest public handoff spots
  • Include an end-of-run log for receipts, missing items, and follow-up

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Automation

V19 Trust Manifesto

Agent Community认知治理协议公开受信声明v1.3.7。DDP偏差检测协议(三协议标准序列/CoordinatorProtocol强制扫描/看板监控面板)+看板深度修复(5根因/3文件数据链路)。V8.1 TrustStack+合规对齐。9Agent,合规0.9235。

Registry SourceRecently Updated
Automation

V19 Trust Manifesto

Agent Community认知治理协议公开受信声明v1.3.7。DDP偏差检测协议(三协议标准序列/CoordinatorProtocol强制扫描/看板监控面板)+看板深度修复(5根因/3文件数据链路)。V8.1 TrustStack+合规对齐。9Agent,合规0.9235。

Registry SourceRecently Updated
7350Profile unavailable
Automation

bot File Processor

通用文件处理技能,用于批量重命名和格式转换。当用户需要批量重命名文件(添加前缀/后缀、替换文本、编号重命名、正则表达式重命名)或转换文件格式(图片格式转换、PDF与图片互转、DOCX转PDF、Markdown转PDF)时使用此技能。

Registry SourceRecently Updated
2620Profile unavailable
Automation

skill-design-patterns

Guides the design of effective agent skills. Use when creating a new skill, improving an existing skill, reviewing a skill's structure, or establishing skill...

Registry SourceRecently Updated
00Profile unavailable