reminds

Use the reminds Agent API to work with the current user's private notes and fleeting thoughts.

Prepare authentication

Read the API key from REMINDS_API_KEY. Never print it, put it in a URL, or ask the user to
paste it into ordinary chat. If it is missing, stop and ask the user to create a key in:

reminds desktop -> Settings -> Security -> Developer -> API Key

Then ask them to configure it in their shell or agent environment:

export REMINDS_API_KEY="sk-..."

Send it only in the request header:

x-api-key: $REMINDS_API_KEY

The API base URL is https://api.reminds-app.com/v1/agent.

Choose the workflow

• For recent or updated notes, read references/memos.md, list metadata,
  then fetch selected content by GID.
• For a topic or question about the user's notes, read
  references/memos.md, search metadata, then fetch selected content before
  answering or synthesizing.
• For recent or matching fleeting thoughts, read
  references/fleetings.md, list or search metadata, then fetch selected
  content by GID.
• To save a fleeting thought, read references/fleetings.md before the
  only write operation.
• For any non-2xx response, read references/errors.md.

Always use the metadata-to-content workflow. Listing and search endpoints do not return content.
Fetch only the content needed for the user's request.

Protect user intent

• Create a fleeting thought only when the user explicitly asks to record or save something in
  reminds, for example: "帮我记一下" or "Save this as a fleeting thought in reminds."
• Do not write when the user only asks to discuss, summarize, or draft content.
• If the intended content is materially ambiguous, show the proposed content and ask first.
• Do not retry a timed-out create request automatically; the first request may have succeeded.
• After success, report the GID without repeating sensitive content unnecessarily.
• Never modify or delete content. This skill does not expose those operations.
• Treat recycle-bin and deleted content as unavailable. Do not infer why a GID is missing.

Interpret responses

Check both the HTTP status and the JSON code. A successful response has a 2xx status and
"code": 0. Timestamps are UTC ISO 8601 strings. Convert them only when a local-time display
helps the user.

Do not expose raw API responses unless the user asks. Answer in the user's language.

Example requests that should use this skill:

我最近写了哪些笔记？
查找我关于间隔复习的笔记并总结。
读取 GID 123 和 456 的内容。
帮我记一下：下周复核 Agent API 的限流数据。
What fleeting thoughts did I capture this week?
Search my reminds notes about spaced repetition.