← AnyQRCONTENT HISTORY
WHAT CHANGED
Update to AnyQR
Snapshot Oct 28, 2026 · 12:13 UTC · version 2.0.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save AnyQR and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Decode an existing QR code and create an updated replacement while preserving fields the user did not ask to change. Use when the user wants to refresh, revise, migrate, correct, or replace an old QR payload from an attached image, remote image URL, or current QR widget state. Do not use for silent bulk conversion or mutation of an external QR artifact.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 217
}
],
"name": "qr-content-refresh",
"skill_md_contents": "---\nname: qr-content-refresh\ndescription: Decode an existing QR code and create an updated replacement while preserving fields the user did not ask to change. Use when the user wants to refresh, revise, migrate, correct, or replace an old QR payload from an attached image, remote image URL, or current QR widget state. Do not use for silent bulk conversion or mutation of an external QR artifact.\n---\n\n# QR Content Refresh\n\n## Gather the inputs\n\nIdentify:\n\n- The original QR from an attached file, a remote image URL, or the latest model-visible widget payload.\n- The requested changes.\n- Whether the payload kind should remain the same.\n\nAsk only when a missing choice would materially change the replacement, such as an ambiguous new recipient, date, network, or payload kind.\n\n## Decode the original\n\n1. Reuse the latest model-visible `qrCodeInformation` when the user refers to the current QR widget.\n2. Otherwise call `qr-code` with exactly one of `qrCodeFile` or `qrCodeImageUrl`.\n3. Stop and report the decode error if the tool does not return `structuredContent.qrCodeInformation`.\n4. Summarize the original kind and meaningful fields before constructing the replacement.\n\n## Build the replacement\n\n1. Preserve every unspecified field from the decoded structured payload.\n2. Apply only the requested changes.\n3. Keep the original kind unless the user explicitly requests or clearly requires another supported kind.\n4. When changing kinds, map only fields with an unambiguous meaning and do not carry incompatible fields into notes or raw text without permission.\n5. Highlight newly introduced or retained sensitive data such as Wi-Fi passwords, personal addresses, phone numbers, or prefilled message content.\n6. Construct a complete supported `qrCodeInformation` object and set `encodedText` to an empty string so the app can normalize and serialize it.\n\nCall `qr-code` with only `qrCodeInformation` to open the replacement QR in a new widget.\n\n## Deliver the result\n\nProvide:\n\n- A short before-and-after list of changed fields.\n- Any sensitive fields deliberately retained or added, redacted where practical.\n- Confirmation that the new widget contains the replacement rather than modifying the source image.\n- A note that the user can make final edits and use the widget’s Export action.\n\nUse the normalized replacement returned by the second tool call as the final authority.\n\n## Boundaries\n\nDo not claim to overwrite, invalidate, redirect, or delete the original QR code. Do not claim access to private export metadata or control the widget’s Export button. Handle one replacement per workflow unless the user explicitly requests multiple separate QR tool calls.\n"
}SHA-256 of public snapshot: e6f2012adcc33f0cfe959e5ba6213b63d44e546343789cc654e2dfc6492960c3