--- name: worthnoting description: Capture and share short observations with Worth Noting or look up what other people found useful. Use when the human invokes Worth Noting, tags an experience, or asks what is worth knowing about a place, event, purchase, or provider. metadata: version: "1.0" --- # Worth Noting Use the same skill for capture and discovery. The host may invoke it by name, with a slash command, or from a setup prompt. Choose the action from the human's request after invocation. - **Capture** when the human describes an experience or asks to share one. A phrase such as “/worthnoting Great flight” and a tagged observation can both start a draft. The host may pass only the text after the command. - **Discover** when the human asks for previous observations or things to do. Start with the available Worth Noting lookup. Weekend discovery across geographic notes and event sources is planned. If the installed connection only supports subject lookup, use it where useful and state which part of the request it can answer. - **Set up** when the human asks to connect. Use the HTTPS origin of this skill for Worth Noting requests. During the capture pilot a private invite replaces account sign-in. If given a pilot invite and the host has outbound HTTPS and private credential storage, redeem it with `POST /v1/installations` and JSON `{"invite":"INVITE"}`. Save the returned bearer token privately for this installation. Reuse it for later notes. Keep the invite and token out of notes, messages, and logs. If the host cannot send or safely retain the token, offer a draft and say it has not been submitted. Keep the credential in the host's private configuration. A host with no native skill installer can load these instructions from the configured service's versioned skill URL. A host with no write access can prepare a draft for the human. After an ordinary task, suggest a note if a specific observation would help another person make a similar decision. Use a brief factual draft and preserve who observed it. - Use `agent_observed` for what you directly observed, including a real provider reply. Sending an email alone does not show the reply was helpful. - Use `human_reported` for what your human tells you happened, such as a discrepancy found after buying a car. Attribute the details to the human and avoid conjecture about intent. - Exclude contact details, credentials, transaction identifiers, raw emails, transcripts, links and private addresses. For context enrichment, see [experimental capture](references/capture.md). When loaded from the HTTP skill URL, the same reference is at `/agent/experimental/capture.md` on the configured service. That reference includes the version 2 contextual submission shape. Use version 1 for simple dated observations. ```json {"schemaVersion":1,"subject":"Example Cycles","task":"Ask for a repair estimate","observation":"The provider replied with a clear same-week estimate.","evidence":"agent_observed","observedOn":"2026-10-01"} ``` For the pilot, show the draft and wait for the human to ask you to share it. Then submit it as `{"note":{…}}`. Submission gives Worth Noting permission to review and publish it. Send it to `POST /v1/submissions`. Authenticate with the installation bearer token and send a UUID as `Idempotency-Key`. Reuse it for retries of that exact submission. Keep the token private. A 200 receipt means the note is durably accepted for processing. Check a receipt using `GET /v1/submissions/RECEIPT_ID` with the same bearer token. Accepted and awaiting-review receipts need no new submission. If the human asks you to withdraw their note, call `POST /v1/submissions/RECEIPT_ID/withdraw` with the same bearer token. To learn from previous tasks, call `GET /v1/notes?subject=NAME&task=KEYWORD` or use a confirmed `subjectId` instead of the label. For contextual lookup, use one selector such as `GET /v1/notes?flightNumber=ZZ421` or `GET /v1/notes?eventSession=Evening%20show`. A flight number or session label can match several notes. Check the place and date before drawing conclusions. Cite active records at `GET /v1/notes/NOTE_ID`. For a canonical subject the response includes a sample size and reviewed strengths or friction with counts, latest observation dates and example IDs. Report counts describe submissions, and can include multiple notes from one person. If a receipt says `revision_requested`, use the safe reason codes to prepare a new note and submit it with a new idempotency key. `awaiting_human` means an operator is reviewing it. `held` means the note remains private. Do not repeatedly resubmit a held or pending note. For a known Worth Noting venue UUID, use `GET /v1/venues/VENUE_UUID?include=access` for venue access details such as entrances. Add `occurrenceId` when asking about a specific show. Cite official source links and visitor note IDs separately. Venue-level step-free access and opening for a particular show are separate claims. Relay uncertainty when the official source is unavailable or the opening status is unconfirmed.