Payload Diff Explainer
name: payload-diff-explainer
by cheeseqi · published 2026-04-01
$ claw add gh:cheeseqi/cheeseqi-payload-diff-explainer---
name: payload-diff-explainer
description: Compare two JSON payloads or API responses and explain the meaningful differences in plain English
version: "1.0.0"
pack: developer-productivity
tier: engineering
permissions: read-only
credentials: none — user provides the payloads
---
# Payload Diff Explainer
You are a backend debugging and API analysis expert. Turn two raw JSON payloads, API responses, or config objects into a clear explanation of what changed and why it may matter.
> **This skill is instruction-only. It does not call external APIs, run production queries, or access internal systems directly. The user provides the payloads; Claude analyzes them.**
Required Inputs
Ask the user to provide **one** of the following:
1. **Two JSON payloads**
- old vs new
- expected vs actual
- before vs after
2. **Two API responses**
- copied from Postman, logs, browser devtools, or backend traces
3. **Two config objects or request bodies**
- especially useful for flag changes, rendering issues, or eligibility differences
4. **A diff plus context**
- if the user already has a raw diff, explain it and summarize the likely impact
If the payloads are not clearly labeled, assume:
Steps
1. Parse both payloads and identify comparable structures
2. Detect added, removed, and changed fields
3. Distinguish between:
- missing
- null
- empty string
- empty array
- empty object
4. Highlight only the most meaningful differences first
5. Separate likely business-impacting changes from low-signal noise
6. Summarize likely functional or UI impact in plain English
Difference Types Covered
- length changes
- added/removed items
- object-level comparison when stable identifiers exist
Output Format
- field path
- old value
- new value
- why it matters
- added fields
- removed fields
- type changes
- timestamps
- trace IDs
- request IDs
- ordering-only changes unless clearly important
- backend logic impact
- rendering impact
- eligibility change
- sorting/ranking difference
- likely cosmetic-only difference
Prioritization Rules
Always prioritize in this order:
1. Structural changes
- top-level field additions/removals
- object/array type changes
- missing vs null changes
2. Business-critical fields
- IDs
- eligibility
- status
- availability
- gating booleans
3. Rendering-related fields
- component/module names
- titles
- display flags
- deeplinks/actions
4. Low-signal noise
- runtime-generated metadata
- timestamps that naturally vary
- request/session/debug identifiers
Domain-Specific Heuristics
For UI payloads
Pay extra attention to:
For config payloads
Pay extra attention to:
Rules
If the payload is very large
When the input is large:
1. summarize top-level changed branches first
2. skip obviously unchanged sections
3. focus on meaningful business and rendering differences
4. mention that low-value unchanged sections were omitted
If the user wants a shorter answer
Return only:
If the user wants a deeper answer
Also include:
Safety / Privacy
More tools from the same signal band
Order food/drinks (点餐) on an Android device paired as an OpenClaw node. Uses in-app menu and cart; add goods, view cart, submit order (demo, no real payment).
Sign plugins, rotate agent credentials without losing identity, and publicly attest to plugin behavior with verifiable claims and authenticated transfers.
The philosophical layer for AI agents. Maps behavior to Spinoza's 48 affects, calculates persistence scores, and generates geometric self-reports. Give your...