Aperture Read

View saved version →

---
name: get-started-with-aperture
description: Help users get started with Aperture Read, choose something useful to read, or set up a recurring brief. For requests to save an existing answer, use the saving workflow.
---

# Get started with Aperture Read

Use two stages: try saving and reading, then create something useful to keep.
Use the user's existing topic, answer or report request. Do not require a
practice guide before saving their own content.

## Choose the entry

- General onboarding: call `get_onboarding_guidance` with `stage="start"`.
  Save its complete canonical welcome guide through `save_document`, using
  the installed save skill and live tool schema. Return the real reader link
  and receipt warnings. Invite the user to open it and check its ending.
- Useful reading ideas or continuing onboarding: request `stage="useful"`.
  Use the returned question, examples and editable templates. Ask only for
  missing details. Create one preview, offer shorter/deeper/different-focus
  changes, then save the chosen complete version when authorized.
  If the user chooses a recurring recipe, fetch the recurring guidance before
  setting up the schedule.
- Recurring reports: request `stage="recurring"`. Start with a useful preview
  as the first save. Review the schedule and timezone before using supported
  ChatGPT scheduling controls. Include the returned complete saving and
  recovery instructions directly in the reviewed task prompt.

Do not create a schedule unless the user requests one. If scheduling is
unavailable, give the full prompt for manual setup. Treat a created schedule,
a completed run, and a confirmed saved receipt as separate outcomes.
Verify one actual scheduled save; an interactive save is not that evidence.

## Connection and recovery

If tools need authorization, help the user select Aperture Read with `@`
and connect it. Pasting literal `@` text does not select the integration.
Saving requires an Aperture Read account. New users should follow signup in
the selected integration's account setup flow, including any invitation or
registration limits. Existing users should sign in with their Aperture Read
account. Check the destination account before approving access, then resume
the chosen stage.

If guidance is unavailable, use the returned `help_url` when available.
Otherwise, share the [public setup guide](https://apertureread.com/help/chatgpt).
Keep the user's topic or answer and selected integration. Do not fabricate a
canonical guide, receipt, reader URL, or schedule. Keep saving outcome separate
from onboarding advice.

For every save, preserve the full text, ending and references. Follow the
installed save workflow and tool recovery contract. Generate a fresh UUID
for a new read. Retry only the original capture ID with its exact arguments,
at most twice. Never reconstruct missing arguments or repeat a confirmed save
to obtain a card. Keep the original content when saving cannot be confirmed.

Stage two is optional. Do not require a third practice save, a minimum report
length, or multiple tasks before the user can read normally.

View saved version →

---
name: save-to-aperture-read
description: Save complete answers, reports or notes to Aperture Read, recover failed saves, or send user-requested feedback. Use when the user's task or standing instructions authorize saving, explicitly request feedback for Aperture Read, or require diagnosis of those operations.
---

Use the connected Aperture Read tools and their current advertised schema. Save when the user’s task or standing instructions authorize it. This skill does not grant authorization or make tools available to scheduled tasks.

## Capture

1. Identify the exact answer, report, or note to save. If it is not available in full, request the missing content; do not reconstruct or summarize it.
2. Preserve the full text and order, including the ending, tables, code, formula delimiters, references, and captions. Use Markdown unless the user explicitly requests literal plain text.
3. Preserve supplied reference labels and actual URLs. When saving existing content, keep unresolved markers visible; never search for, infer or invent missing URLs. Follow the image guidance below for selected images.
4. Describe files truthfully: a saved URL is a link, not copied bytes. Keep unavailable artifacts explicit. Do not replace temporary or sandbox URLs with invented public ones.
5. Generate a fresh UUID `capture_id` for each new document, including each scheduled report. Prefer UUIDv7 when a real generator is available. UUIDv4 remains valid, including `crypto.randomUUID()` or Python `uuid.uuid4()`. Never copy IDs from examples, earlier reports, or unrelated chats. Fresh IDs and unchanged retries matter more than the UUID version. Keep the ID and its exact submitted arguments together as one immutable attempt. Reuse them only when retrying that attempt. Supply only `capture_id`, `title`, `format`, `body`, and optional `source_url`/`report_date` when the live schema supports them. Omit absent optional fields; do not send nulls, empty metadata, `series`, or additional properties. Only use a user-supplied source URL.
6. Call `save_document` once per capture. It returns text and structured receipts. The host controls whether the attached receipt card appears; there is no `show_ui` argument. Never repeat a confirmed save to obtain a card.

## Images

- When authoring a new report, include public or web-search images selected for that report. Use available image-search results or supplied direct HTTPS image URLs.
- Keep the actual image URL separate from the source-page link. Include available attribution and license links. Never invent them.
- When saving existing content, preserve selected image URLs exactly, including query parameters and encoded paths. Do not search for replacements, add unrelated images, omit selected images, or regenerate visuals during saving.
- Use `![alt text](https://… "optional title")` at each original position. Preserve alt text, titles, captions, attribution, source links, surrounding text, and the ending. Keep linked images and images in tables in place. Ordinary image-file links remain links.
- An upstream image-preview or inspection size limit does not prove a known image URL cannot display. Preserve the known URL and disclose the verification limit.
- If an uploaded or generated image has no usable HTTPS image URL, keep its existing placeholder or label in position. Disclose the unavailable image. This save tool has no image-file input. Never invent file handles, public URLs, or replacement images.
- Images remain external links; image bytes are not copied. Temporary or sandbox links do not provide durable image storage. Retained source text and a successful receipt do not prove image retention or display.

For a new report, place the image between its related paragraphs. Use the source-page URL in a separate link:

```markdown
The related explanation.

![Description](https://images.example.org/photo.jpg?size=large "Supplied title")

Caption. Credit: supplied creator. [Source](https://example.org/article).

Preview of the first 4,000 characters. Read full instructions →