← Back to Skills Marketplace
harrylabsj

Delivered Package Missing Claim Kit

by haidong · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
77
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install delivered-package-missing-claim-kit
Description
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...
README (SKILL.md)

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
Field Detail
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/time Event Evidence or note
  1. Location and Handoff Checklist
Check Status Notes
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
Evidence Available? Where saved Notes
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
When Action Owner Notes
  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."
Usage Guidance
Before using it, avoid pasting unnecessary personal information, and follow the skill’s reminder to redact full addresses, order numbers, payment details, account IDs, access codes, and unrelated personal data before sharing screenshots or messages.
Capability Analysis
Type: OpenClaw Skill Name: delivered-package-missing-claim-kit Version: 1.0.0 The 'delivered-package-missing-claim-kit' skill is a documentation-only workflow designed to help users draft claim messages and organize evidence for missing packages. It contains no executable code, scripts, or API calls, and explicitly includes safety boundaries that forbid the collection of sensitive data (passwords, payment info) or the fabrication of evidence. All files (SKILL.md, skill.json, and ACCEPTANCE.md) are consistent with a low-risk, prompt-based assistance tool.
Capability Tags
cryptocan-make-purchases
Capability Assessment
Purpose & Capability
The stated purpose is to organize facts, evidence, messages, and follow-ups for a missing delivered package; the visible instructions are consistent with that purpose.
Instruction Scope
The workflow asks for relevant delivery, order, evidence, and resolution details, and explicitly avoids fabricated claims, surveillance access, accusations, or guaranteed outcomes.
Install Mechanism
There is no install spec and no executable code; metadata declares this as a prompt-flow/document-only skill.
Credentials
No binaries, environment variables, APIs, credentials, carrier accounts, retailer accounts, cameras, locks, maps, or payment accounts are requested.
Persistence & Privilege
The artifacts do not show persistence, background activity, privileged local access, account mutation, or stored memory behavior.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install delivered-package-missing-claim-kit
  3. After installation, invoke the skill by name or use /delivered-package-missing-claim-kit
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the Delivered Package Missing Claim Kit. - Guides users through gathering facts, evidence, and communications for packages marked "delivered" but not found. - Provides a structured claim packet: claim snapshot, timeline, location/handoff and evidence checklists, carrier/retailer message, neighbor/mailroom note, follow-up calendar, escalation options, and a redaction reminder. - Designed to be calm, factual, and non-accusatory, focusing on documentation rather than speculation or confrontation. - Includes clear boundaries on privacy, legal issues, and evidence integrity.
Metadata
Slug delivered-package-missing-claim-kit
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is 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... It is an AI Agent Skill for Claude Code / OpenClaw, with 77 downloads so far.

How do I install Delivered Package Missing Claim Kit?

Run "/install delivered-package-missing-claim-kit" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Delivered Package Missing Claim Kit free?

Yes, Delivered Package Missing Claim Kit is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Delivered Package Missing Claim Kit support?

Delivered Package Missing Claim Kit is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Delivered Package Missing Claim Kit?

It is built and maintained by haidong (@harrylabsj); the current version is v1.0.0.

💬 Comments