← AnyQRCONTENT HISTORY

Update to AnyQR

Snapshot Oct 28, 2026 · 12:13 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

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 JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Build a clean campaign URL with deliberate UTM parameters and encode it as a QR code. Use when the user wants a marketing, poster, flyer, social, email, or event QR with tracking parameters, or wants an existing campaign URL cleaned up before QR creation. Do not use for link shortening, analytics reporting, destination reputation checks, or non-HTTP links.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 224
    }
  ],
  "name": "campaign-link-qr-builder",
  "skill_md_contents": "---\nname: campaign-link-qr-builder\ndescription: Build a clean campaign URL with deliberate UTM parameters and encode it as a QR code. Use when the user wants a marketing, poster, flyer, social, email, or event QR with tracking parameters, or wants an existing campaign URL cleaned up before QR creation. Do not use for link shortening, analytics reporting, destination reputation checks, or non-HTTP links.\n---\n\n# Campaign Link QR Builder\n\n## Gather the inputs\n\nRequire an HTTP or HTTPS destination URL. Collect only the tracking dimensions the user needs:\n\n- `utm_source`\n- `utm_medium`\n- `utm_campaign`\n- Optional `utm_content`\n- Optional `utm_term`\n\nInfer a value only when it is unambiguous from the request. Ask for a missing value when the user explicitly wants tracking and the omission would make the campaign attribution unclear.\n\n## Construct the final URL\n\n1. Trim surrounding whitespace and require an `http:` or `https:` scheme.\n2. Preserve the destination host, path, fragment, and unrelated query parameters.\n3. Preserve existing UTM parameters unless the user asks to replace them. Resolve conflicting requested values before creating the QR.\n4. Normalize newly supplied UTM values consistently within the URL. Prefer concise lowercase values separated by hyphens unless the user has an established naming convention.\n5. Percent-encode query values using normal URL semantics; do not manually double-encode them.\n6. Show the exact final URL when it materially differs from the supplied destination.\n\nIf the result is unusually long, warn that it may produce a denser QR. Do not substitute an unrequested shortener or redirect.\n\n## Create the QR code\n\nCall `qr-code` with only:\n\n- `qrCodeInformation.kind` set to `url`.\n- `qrCodeInformation.url` set to the final URL.\n- `qrCodeInformation.encodedText` set to an empty string.\n\nTreat the normalized `structuredContent.qrCodeInformation` returned by the tool as authoritative.\n\n## Deliver the result\n\nReturn:\n\n- The exact encoded campaign URL.\n- A compact mapping of each UTM parameter to its purpose.\n- Any preserved pre-existing query parameters worth noting.\n- Confirmation that the QR is editable and exportable in the widget.\n\n## Boundaries\n\nDo not claim the destination was opened, verified, or found safe. Do not claim that analytics are configured or receiving traffic. Do not shorten the link, create a redirect, or modify a remote website; those capabilities are not exposed by the app.\n"
}

SHA-256 of public snapshot: 128e3edab1c5b465887069686c5b236d460647ec76ee80061b0d581d019a73eb