Update to AnyQR

{
  "description": "Create a vCard QR code after minimizing and reviewing the personal information it will disclose. Use when the user wants a networking, business-card, conference, portfolio, or public contact QR and wants help deciding which contact fields are appropriate to share. Do not use to enrich contact data from external sources or publish private fields without clear user intent.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 235
    }
  ],
  "name": "privacy-first-vcard-qr",
  "skill_md_contents": "---\nname: privacy-first-vcard-qr\ndescription: Create a vCard QR code after minimizing and reviewing the personal information it will disclose. Use when the user wants a networking, business-card, conference, portfolio, or public contact QR and wants help deciding which contact fields are appropriate to share. Do not use to enrich contact data from external sources or publish private fields without clear user intent.\n---\n\n# Privacy-First vCard QR\n\n## Gather the contact details\n\nUse only details the user supplied or explicitly approved. The supported vCard fields are first name, last name, organization, title, phone numbers, email addresses, website, address, and note.\n\nClassify proposed fields before encoding:\n\n- **Clearly public:** details the user identifies as business, professional, event-facing, or already intended for publication.\n- **Potentially sensitive:** personal mobile numbers, personal email addresses, street addresses, free-form notes, or mixed business and personal details.\n\nWhen intent is unclear for a potentially sensitive field, omit it or ask whether it should be public. Do not add inferred social profiles, photographs, birthdays, identifiers, or addresses.\n\n## Prepare the vCard\n\n1. Normalize surrounding whitespace in names, phone numbers, emails, and the website without inventing missing values.\n2. Keep multiple approved phone numbers and email addresses as separate entries.\n3. Require the website to be supplied explicitly; do not search for one.\n4. Use the address and note only when the user clearly wants them encoded.\n5. Give the user a concise disclosure summary before or alongside creation when sensitive fields are included.\n\nCall `qr-code` with only `qrCodeInformation` using:\n\n- `kind: \"vcard\"`\n- The approved fields, using empty strings or empty arrays for unused supported fields.\n- `encodedText: \"\"` so the app performs canonical serialization.\n\nTreat the normalized tool output as authoritative.\n\n## Deliver the result\n\nProvide:\n\n- A field-by-field summary of what the QR shares.\n- A separate note for any deliberately omitted sensitive information.\n- The editable vCard QR widget and a reminder that the exported image contains all approved fields.\n\nAvoid repeating sensitive field values more often than needed.\n\n## Boundaries\n\nDo not validate mailbox ownership, phone ownership, website availability, or the identity of the contact. Do not claim support for photos, social-profile fields, cryptographic signatures, or remote contact-book updates. The workflow creates a QR payload only.\n"
}