Skill instructions
calendar-invite-qr-planner2.38 KB
View saved version →
---
name: calendar-invite-qr-planner
description: Turn event details into a reviewed calendar-invite QR code. Use when the user wants a meeting, appointment, class, performance, reservation, or all-day event encoded for calendar import and needs help resolving missing dates, end times, locations, or timezone ambiguity. Do not use to write directly to a calendar account or promise recurrence, reminders, organizer fields, or attendee invitations.
---
# Calendar Invite QR Planner
## Gather the event details
Collect:
- Summary.
- Optional description and location.
- Start.
- End.
- Whether the event is all-day.
Ask only about details whose ambiguity could put the event on the wrong date or time. Do not invent a duration, timezone, or end date without a clear contextual basis.
## Normalize the schedule
1. Use `YYYY-MM-DD` values for all-day events.
2. Treat an all-day `DTEND` as exclusive. When the user states an inclusive final day, encode the following date as the end and explain that representation in the preview.
3. Use ISO-like local values such as `YYYY-MM-DDTHH:mm` for floating local times.
4. Use a trailing `Z` only when the event time is explicitly UTC or has been unambiguously converted to UTC.
5. If attendees may be in multiple timezones and the user supplied only a named timezone, clarify how to represent it because the app schema has no named-timezone field.
6. Verify that the end is after the start. Resolve contradictions before creating the QR.
## Create the calendar QR
Call `qr-code` with only `qrCodeInformation` using:
- `kind: "calendar"`
- The normalized `summary`, `description`, `location`, `start`, `end`, and `allDay` fields.
- `encodedText: ""` so the app creates the calendar payload.
Treat returned `structuredContent.qrCodeInformation` as authoritative.
## Deliver the result
Provide a plain-language preview containing:
- Event title and location.
- Start and end as the user should understand them.
- The assumed timezone behavior: UTC, floating local time, or all-day.
- Any omitted optional fields.
- Confirmation that the widget is editable and exportable.
## Boundaries
Do not claim the event was added to a calendar, invitations were sent, availability was checked, or reminders were scheduled. The supported payload has no organizer, attendee, recurrence, alarm, or named-timezone field; do not hide those values in another field as if they were structurally supported.
Referenced files: 1 — file references are metadata, not package contents.
campaign-link-qr-builder2.4 KB
View saved version →
---
name: campaign-link-qr-builder
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.
---
# Campaign Link QR Builder
## Gather the inputs
Require an HTTP or HTTPS destination URL. Collect only the tracking dimensions the user needs:
- `utm_source`
- `utm_medium`
- `utm_campaign`
- Optional `utm_content`
- Optional `utm_term`
Infer 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.
## Construct the final URL
1. Trim surrounding whitespace and require an `http:` or `https:` scheme.
2. Preserve the destination host, path, fragment, and unrelated query parameters.
3. Preserve existing UTM parameters unless the user asks to replace them. Resolve conflicting requested values before creating the QR.
4. Normalize newly supplied UTM values consistently within the URL. Prefer concise lowercase values separated by hyphens unless the user has an established naming convention.
5. Percent-encode query values using normal URL semantics; do not manually double-encode them.
6. Show the exact final URL when it materially differs from the supplied destination.
If the result is unusually long, warn that it may produce a denser QR. Do not substitute an unrequested shortener or redirect.
## Create the QR code
Call `qr-code` with only:
- `qrCodeInformation.kind` set to `url`.
- `qrCodeInformation.url` set to the final URL.
- `qrCodeInformation.encodedText` set to an empty string.
Treat the normalized `structuredContent.qrCodeInformation` returned by the tool as authoritative.
## Deliver the result
Return:
- The exact encoded campaign URL.
- A compact mapping of each UTM parameter to its purpose.
- Any preserved pre-existing query parameters worth noting.
- Confirmation that the QR is editable and exportable in the widget.
## Boundaries
Do 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.
Referenced files: 1 — file references are metadata, not package contents.
guest-wifi-qr-setup2.17 KB
View saved version →
---
name: guest-wifi-qr-setup
description: Prepare a guest Wi-Fi QR code with an explicit credential and privacy check. Use when the user wants visitors, customers, tenants, or event attendees to join a wireless network by scanning a QR code. Do not use to configure a router, discover network credentials, test connectivity, or imply that a shared password remains hidden from ChatGPT or QR recipients.
---
# Guest Wi-Fi QR Setup
## Gather the network details
Require:
- The exact SSID.
- Authentication type: `WPA`, `WEP`, or `nopass`.
- The password for `WPA` or `WEP`.
- Whether the SSID is hidden.
Do not invent placeholder credentials. If the user supplies a primary household or company network, recommend a guest network when practical, but continue if the user clearly chooses to share the supplied network.
Before calling the tool, state briefly that the password will be encoded in the QR payload and persisted as model-visible QR information. Anyone who can scan or decode the exported QR can recover it.
## Prepare the payload
1. Preserve SSID and password characters exactly; the app handles QR escaping.
2. Use `nopass` only for an intentionally open network and set the password to an empty string.
3. Use the user’s stated hidden-network setting. Do not infer it from the SSID.
4. Flag WEP as legacy security without silently changing the authentication type.
Call `qr-code` with only `qrCodeInformation` using:
- `kind: "wifi"`
- The exact `ssid`, `password`, `authentication`, and `hidden` values.
- `encodedText: ""` so the app serializes and escapes the payload.
Treat the normalized tool output as authoritative.
## Deliver the result
Confirm:
- The SSID, authentication type, and hidden status.
- Whether a password is embedded, without restating it by default.
- That the widget can be edited and exported.
- That temporary event or visitor credentials should be rotated when they are no longer needed, when appropriate to the user’s scenario.
## Boundaries
Do not claim to create the network, change router settings, connect a device, verify the password, test coverage, or revoke credentials. Do not claim the password is secret merely because it is rendered as a QR image.
Referenced files: 1 — file references are metadata, not package contents.
privacy-first-vcard-qr2.49 KB
View saved version →
---
name: privacy-first-vcard-qr
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.
---
# Privacy-First vCard QR
## Gather the contact details
Use 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.
Classify proposed fields before encoding:
- **Clearly public:** details the user identifies as business, professional, event-facing, or already intended for publication.
- **Potentially sensitive:** personal mobile numbers, personal email addresses, street addresses, free-form notes, or mixed business and personal details.
When 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.
## Prepare the vCard
1. Normalize surrounding whitespace in names, phone numbers, emails, and the website without inventing missing values.
2. Keep multiple approved phone numbers and email addresses as separate entries.
3. Require the website to be supplied explicitly; do not search for one.
4. Use the address and note only when the user clearly wants them encoded.
5. Give the user a concise disclosure summary before or alongside creation when sensitive fields are included.
Call `qr-code` with only `qrCodeInformation` using:
- `kind: "vcard"`
- The approved fields, using empty strings or empty arrays for unused supported fields.
- `encodedText: ""` so the app performs canonical serialization.
Treat the normalized tool output as authoritative.
## Deliver the result
Provide:
- A field-by-field summary of what the QR shares.
- A separate note for any deliberately omitted sensitive information.
- The editable vCard QR widget and a reminder that the exported image contains all approved fields.
Avoid repeating sensitive field values more often than needed.
## Boundaries
Do 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.
Referenced files: 1 — file references are metadata, not package contents.
qr-content-refresh2.62 KB
View saved version →
---
name: qr-content-refresh
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.
---
# QR Content Refresh
## Gather the inputs
Identify:
- The original QR from an attached file, a remote image URL, or the latest model-visible widget payload.
- The requested changes.
- Whether the payload kind should remain the same.
Ask only when a missing choice would materially change the replacement, such as an ambiguous new recipient, date, network, or payload kind.
## Decode the original
1. Reuse the latest model-visible `qrCodeInformation` when the user refers to the current QR widget.
2. Otherwise call `qr-code` with exactly one of `qrCodeFile` or `qrCodeImageUrl`.
3. Stop and report the decode error if the tool does not return `structuredContent.qrCodeInformation`.
4. Summarize the original kind and meaningful fields before constructing the replacement.
## Build the replacement
1. Preserve every unspecified field from the decoded structured payload.
2. Apply only the requested changes.
3. Keep the original kind unless the user explicitly requests or clearly requires another supported kind.
4. When changing kinds, map only fields with an unambiguous meaning and do not carry incompatible fields into notes or raw text without permission.
5. Highlight newly introduced or retained sensitive data such as Wi-Fi passwords, personal addresses, phone numbers, or prefilled message content.
6. Construct a complete supported `qrCodeInformation` object and set `encodedText` to an empty string so the app can normalize and serialize it.
Call `qr-code` with only `qrCodeInformation` to open the replacement QR in a new widget.
## Deliver the result
Provide:
- A short before-and-after list of changed fields.
- Any sensitive fields deliberately retained or added, redacted where practical.
- Confirmation that the new widget contains the replacement rather than modifying the source image.
- A note that the user can make final edits and use the widget’s Export action.
Use the normalized replacement returned by the second tool call as the final authority.
## Boundaries
Do 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.
Referenced files: 1 — file references are metadata, not package contents.
qr-payload-safety-review2.88 KB
View saved version →
---
name: qr-payload-safety-review
description: Decode and review a QR payload before the user acts on it. Use when the user asks what a QR code does, whether its contents look suspicious, what data it exposes, or for a safety check of an attached QR image or remote QR image URL. Do not use for generic QR education, destination reputation checks, or requests to open or follow encoded links.
---
# QR Payload Safety Review
## Gather the input
Require an attached QR image, a remote QR image URL, or an already hydrated model-visible QR payload. If none is available, ask the user to provide one.
Do not ask the user to transcribe an encoded payload when the `qr-code` tool can decode the supplied image.
## Decode the QR code
1. Reuse the latest model-visible `qrCodeInformation` when the user clearly refers to the current widget state.
2. Otherwise call `qr-code` with exactly one source:
- `qrCodeFile` for a ChatGPT-hosted image file.
- `qrCodeImageUrl` for a remote QR image URL.
3. Treat returned `structuredContent.qrCodeInformation` as authoritative. Do not infer a payload if decoding fails.
## Review the payload
Explain the behavior implied by `kind` and the exact meaningful fields:
- For `url`, identify the scheme and destination host. Flag plain HTTP, embedded credentials, raw IP addresses, unusual ports, or visually confusing hostnames as potential concerns.
- For `mailto`, `sms`, and `tel`, identify the recipient and any prefilled content so the user knows what action scanning prepares.
- For `wifi`, state that the QR contains network access details and indicate whether a password is embedded without repeating that password unnecessarily.
- For `vcard`, `calendar`, and `geo`, summarize the personal, scheduling, or location information that would be imported or displayed.
- For `raw`, identify any recognizable scheme conservatively. Treat an unknown scheme as unknown rather than guessing its behavior.
- For plain `text`, distinguish inert text from instructions that try to persuade the user to take a separate action.
Use calibrated language. Say “no obvious structural warning signs” instead of declaring a payload safe. Distinguish facts present in the payload from interpretation.
## Deliver the review
Return four concise sections:
1. **What it does** — the action scanning is expected to prepare.
2. **What it contains** — the relevant decoded fields, with secrets redacted when practical.
3. **Potential concerns** — only payload-based observations.
4. **Safer next step** — a concrete way to verify or proceed cautiously.
Keep the decoded widget available so the user can inspect the exact payload.
## Boundaries
Do not open the encoded destination, submit a message, place a call, join a network, or execute a custom scheme. Do not claim malware scanning, domain reputation, ownership verification, or live destination availability; the app exposes none of those capabilities.
Referenced files: 1 — file references are metadata, not package contents.