# Reconcile Uncertain Deliveries Without Resending

Timeouts and conflicting receipts can leave delivery status unclear and make retries risky. This skill guides evidence matching and produces a bounded reconciliation record without resending.

## Install

```bash
npx skillstore add tdw8147-crypto/unknown-delivery-reconciliation
```

## Metadata

- Status: approved
- Slug: tdw8147-crypto-unknown-delivery-reconciliation
- Skillstore revision: r1
- Version status: missing
- Tree hash: d7ba479ae4f01721b14c0c9c4d62e511dc45f082e33b57b0f4f0fe3736f839ca
- Author: tdw8147-crypto
- GitHub username: tdw8147-crypto
- License: MIT
- Repository: https://github.com/tdw8147-crypto/skill-delivery-kit/tree/30eb4e17579f14a1ee3b7c7511ef744fbccdf9a9/unknown-delivery-reconciliation
- Ref: ed1772c6059847312cb8ef5d65867d5bb3b602c3
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, external\_commands
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/tdw8147-crypto-unknown-delivery-reconciliation
- Manifest: https://skillstore.pages.dev/api/skills/tdw8147-crypto-unknown-delivery-reconciliation/manifest

## Capabilities

- Guides matching receipts to the original request ID, target, submission time, and submitted content fingerprint.
- Separates accepted, sent, delivered, read, definitely not sent, and outcome unknown using documented channel meanings.
- Distinguishes relevant receipts from newer records for different targets, requests, or replacement attachments.
- Structures a reconciliation record with acceptance requirements, observations, identity matches, evidence gaps, and a conclusion.
- Defines one original-request lookup with an attempt cap or expiry and an explicit stopping result.
- Keeps proposed checks separate from completed checks and limits simulations to supplied evidence.

## Use Cases

- Resolve a customer upload timeout: Compare the original upload with available receipts and explain whether delivery is established without asking the customer to upload again.
- Review conflicting dispatch records: Separate records for different recipients or identifiers before deciding whether the original outbound request meets its acceptance requirement.
- Check a replacement attachment: Compare submitted fingerprints when a same-named replacement file appears, preserving unknown status when the original delivery lacks matching evidence.

## Prompt Templates

### Review one timed-out submission

```
Reconcile this timed-out submission using the supplied receipt: [request and receipt]. State whether the required acceptance level is met. Do not resend.
```

### Compare conflicting receipts

```
Compare these receipts for the original request: [ID, target, submission time, fingerprint, and observations]. Match identity before comparing timestamps. Explain excluded records and report the supported status.
```

### Reconcile a replacement attachment

```
The upload timed out and a same-named file now has a different fingerprint: [evidence]. Distinguish the original payload from the replacement. Provide a record and at most one proposed lookup.
```

### Define a bounded unresolved-case handoff

```
Use only this simulated evidence: [original identity, possible aliases, receipts, channel definitions, and access limits]. Preserve unresolved identity mappings and mark missing fields. Define one original-only lookup with a one-attempt cap and explicit stop result. Do not contact a real channel or resend.
```

## Limitations

- Provides instructions, not a delivery service or bundled status-query integration.
- Cannot confirm delivery without trustworthy evidence linked to the original request.
- Cannot resolve undocumented status meanings or unproven identifier aliases.
- Does not send, resend, or guarantee remote idempotency.

## Best Practices

- Provide the original request ID, target, submission time, and submitted content fingerprint.
- Include receipt sources, observation times, raw labels, and documented channel meanings.
- Set one lookup limit and stop when acceptance is met or the limit is reached.

## Anti Patterns

- Do not resend with the same ID, a new ID, or a test click to resolve uncertainty.
- Do not treat matching filenames, newer timestamps, or unrelated receipts as proof of original-request delivery.
- Do not turn timeouts, zero local counters, or empty searches into definitive failure or unlimited polling.

## Security Audit

- Audited at: 2026-11-10T10:47:54.941\+00:00
- Summary: All 31 static findings are false positives involving documentation links, installation directories, Markdown formatting, example timestamps, or Chinese text. The workflow prohibits duplicate sends and limits follow-up checks. No evidence found of malicious execution, credential access, exfiltration, or audit-directed prompt injection in the reviewed files.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0