delivered-package-missing-claim-kit

Build a missing-package claim packet when tracking says delivered but the package is not at the door, locker, mailroom, porch, lobby, or usual drop spot. Use when the user needs a factual timeline, evidence checklist, carrier or retailer message, neighbor or mailroom inquiry note, and follow-up calendar.

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 "delivered-package-missing-claim-kit" with this command: npx skills add harrylabsj/delivered-package-missing-claim-kit

Delivered Package Missing Claim Kit

Purpose

Turn a stressful missing-package situation into a calm, factual claim packet the user can send to a carrier, retailer, marketplace, building office, locker provider, or mailroom.

This is a documentation and communication workflow. It does not access carrier accounts, retailer accounts, maps, cameras, smart locks, building systems, police systems, or payment accounts.

Use This Skill When

Use this skill when the user's tracking page says a package was delivered but the user cannot find it.

Common cases include:

  • Tracking says delivered, but the package is not at the door, porch, lobby, locker, parcel room, mailbox, mailroom, front desk, garage, or usual drop spot.
  • Photo-of-delivery does not match the user's location or is unclear.
  • A household member, neighbor, doorman, front desk, building staff, roommate, or mailroom may have received it.
  • The user needs a carrier claim, retailer support request, marketplace message, replacement request, refund request, or documentation packet.
  • The user needs language that is firm without accusing drivers, neighbors, or staff.

Do not use this skill for proactive delivery planning before delivery, carrier route tracking, porch camera access, surveillance review, confrontation scripts, or claims based on fabricated facts.

Best Inputs

Ask only for details needed to build the packet. If information is missing, draft with placeholders.

  • Carrier, retailer, marketplace, order date, expected delivery date, and tracking status.
  • Delivery timestamp, delivery address type, and photo-of-delivery details if available.
  • Last confirmed location and whether the user checked door, mailbox, parcel locker, mailroom, lobby, porch, side door, garage, front desk, and alternate entrances.
  • Household or building handoff checks already completed.
  • Item description, approximate value, whether it is perishable, time-sensitive, prescription-related, high value, or gift-related.
  • Evidence available: tracking screenshot, delivery photo, order confirmation, receipt, support chat, photos of empty drop location, locker/mailroom screenshots, building log, or neighbor note.
  • Desired resolution: locate package, replacement, refund, credit, investigation, carrier claim number, or retailer escalation.
  • Any deadlines, claim window, prior ticket number, support response, or promised follow-up.

Workflow

  1. Capture tracking and proof. Record carrier, retailer, tracking number placeholder, delivery timestamp, delivery photo description, order value, and requested resolution.
  2. Check likely drop locations. Confirm door, mailbox, locker, lobby, parcel room, mailroom, side entrance, garage, front desk, and any alternate drop spot before filing.
  3. Confirm handoffs. Ask whether household members, roommates, neighbors, building staff, mailroom staff, or a front desk accepted or moved the package.
  4. Gather evidence. List screenshots, order details, photos, empty-location pictures, building logs, support chats, and any relevant value or time-sensitivity proof.
  5. Draft claim messages. Produce a carrier or retailer support message, plus a shorter neighbor or mailroom inquiry note.
  6. Set follow-up calendar. Create dated follow-ups for immediate check, first support contact, claim follow-up, escalation, and refund or replacement decision.
  7. Escalate carefully. Suggest escalation through retailer, carrier, marketplace, building management, or payment provider only when appropriate, without accusations or guaranteed outcomes.

Output Format

Return the claim kit in this order:

  1. Claim Snapshot
FieldDetail
Carrier
Retailer or marketplace
Tracking number placeholder
Delivery timestamp
Delivery proof available
Item and approximate value
Desired resolution
Claim or support deadline
  1. Timeline
Date/timeEventEvidence or note
  1. Location and Handoff Checklist
CheckStatusNotes
Door, porch, lobby, or usual drop spot
Mailbox, parcel locker, or package room
Side door, garage, front desk, or alternate entrance
Household, roommate, or guest handoff
Neighbor, doorman, mailroom, or building staff inquiry
  1. Evidence Checklist
EvidenceAvailable?Where savedNotes
Tracking screenshot
Delivery photo or proof
Order confirmation or receipt
Photos of empty drop location
Building or locker log
Prior support messages
  1. Carrier or Retailer Claim Message

A copy-ready message that states the delivered status, completed checks, attached evidence, requested investigation, and requested resolution.

  1. Neighbor or Mailroom Inquiry Note

A brief non-accusatory note asking whether the package was received, moved, or seen.

  1. Follow-Up Calendar
WhenActionOwnerNotes
  1. Escalation Options

A short list of next channels based on the user's facts, such as retailer support, carrier claim form, marketplace case, building manager, payment-provider inquiry, or platform-specific high-value item process.

  1. Redaction Reminder

A brief reminder to redact full address, full order number, phone number, payment details, account IDs, access codes, and unrelated personal data from screenshots before sharing publicly or with neighbors.

Message Style

  • Be factual, calm, specific, and non-accusatory.
  • Use exact dates, delivery timestamps, carrier names, retailer names, and evidence names when provided.
  • Say what was checked before filing the claim.
  • Ask for a clear resolution: investigation, package location, replacement, refund, credit, or written claim result.
  • Avoid accusing drivers, neighbors, household members, building staff, or mailroom staff.
  • Avoid threats, speculation, social media pressure, or statements not supported by evidence.

Safety Boundary

  • Do not fabricate claims, evidence, screenshots, delivery photos, support messages, values, or police reports.
  • Do not accuse a person or group of theft without evidence.
  • Do not ask for passwords, one-time codes, full payment numbers, full addresses beyond what the official claim needs, or account login details.
  • Do not instruct the user to access private cameras, building systems, carrier systems, or accounts beyond their own lawful records.
  • Remind the user to confirm household, roommate, front desk, mailroom, locker, and likely drop locations before escalating.
  • For high-value, regulated, prescription, or legally sensitive items, tell the user to follow the retailer or carrier's official process and consider appropriate local reporting only if required by policy or circumstances.
  • Do not guarantee refunds, replacements, investigations, delivery recovery, or claim timelines.

Example Prompts

  • "Tracking says delivered but the package is not here. Help me file a claim."
  • "Write a message to the retailer saying my delivered package is missing."
  • "The delivery photo is not my door. Build a claim packet."
  • "I need a note for my building mailroom about a missing package."
  • "Make a follow-up plan for a missing package claim."

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.

General

心律失常早期预警分析工具

Based on facial video, identifies abnormal rhythms such as premature beats, atrial fibrillation, tachycardia/bradycardia, assists in early detection of heart...

Registry SourceRecently Updated
General

Smoke Alarm Test Map

Build a room-by-room smoke alarm map and recurring test log from user-provided home details, focusing on checklist tracking and manufacturer or local fire-sa...

Registry SourceRecently Updated
General

Last Minute Child Pickup Auth

Create a same-day child pickup authorization checklist and printable note from necessary user-provided details, with explicit reminders to verify the school,...

Registry SourceRecently Updated
General

Power Outage Work Continuity Card

Create a power outage work continuity card with priority tasks, offline files, safe charging plan, backup workspace, recovery order, and message templates wh...

Registry SourceRecently Updated