Linko

View saved version →

---
name: capture
description: Save what the user wants to keep to their Linko library as a private note, a web link or a book. Use when the user asks to save, keep, note down or remember something in Linko, or to add a link or a book to Linko.
---

# Save to Linko

Save only what the user asks to keep, once per request. Never save on your own initiative or keep saving in later turns. The user's explicit instructions take priority over this skill.

## Choose what to save

- **A web link** (article, video, podcast, post): call `add_resource` with `link`. A book's page is a book, not a link.
- **A book**: call `add_book` with its `title`, plus `author` or `isbn` when the user gave them.
- **Anything else** is a note.

## Notes

- If the user gave the exact text, or approved text you showed them, call `create_note` with it. Pass a new UUID as `request_id`, and reuse it only to retry that same save after an error.
- Otherwise, for example "save the key points of this chat", call `draft_note` with a proposed `title` and `content`. Tell the user nothing is saved until they choose Save note, and don't also call `create_note` for that note.
- Preserve supplied or approved text when saving it. Don't present invented facts or sources as the user's records.
- New notes created from ChatGPT are always private. Linko looks for suitable topics in the background, so pass tags or topics only when the user names one. If a name is ambiguous, the tool returns candidates: ask which one, and pass its ID next time.
- Use `edit_note` only when the user asks to change a specific note. It replaces the fields you pass and keeps the rest.

## Books

- If `add_book` returns several candidates, a card lets the user choose. Where no card appears, list the candidates (title, author, year) and ask. Then call `add_book` again with the chosen `title` and `book_id`.
- If nothing matches, say so and ask for the author or ISBN. Don't save a web page in place of the book.

## After saving

- Report a save only after the tool or card confirms it. The card shows any topic, tags or related notes found as organizing finishes; these results are not guaranteed.
- If a call fails, say what didn't happen. If Linko needs to be reconnected, ask the user to reconnect it.

View saved version →

---
name: get-started
description: Set up Linko after the plugin is installed. Explain what Linko does in ChatGPT, connect the account, and help the user save a first note and see where Linko files it.
---

# Get started with Linko

Run this when the user sets up the Linko plugin or asks how to start. Keep it short and conversational, in the user's language. The user's own requests come first: if they installed Linko in the middle of a task, help with that task instead and keep setup to one line.

1. In two sentences, say what Linko does here: it keeps the user's notes, links and books in their own Linko library, and it brings them back into a conversation when the user asks.
2. Ask what they'd like to keep first: something they learned recently, or a point from this conversation if there is one. Wait for their answer; don't invent one.
3. Call `draft_note` with a short `title` and their text as `content`, so they can review it. If Linko isn't connected yet, ChatGPT asks them to connect; continue once they have. Tell them nothing is saved until they choose Save note.
   - If the tool says this app can't show Linko's editor, read the exact text back to them. After they confirm it, call `create_note` with that text and a new UUID as `request_id`.
4. Once the save is confirmed, point to the receipt and any topics or related notes it found. Organizing can finish later or find no suitable match.
5. Suggest one way to use it again: ask about saved knowledge, or open Linko beside the chat and add a record. Explain other entrypoints only if asked: desktop's paperclip content-search entry opens the picker directly; Web offers Tab search when indicated in the composer.

Don't list or read the user's existing notes during setup unless they ask. Save only what they asked to keep. If a call fails, say what didn't happen instead of claiming it worked.

View saved version →

---
name: recall
description: Answer from the user's own Linko notes and saved resources, with links. Use when the user asks what they saved, wrote, read or learned about something, asks to find or summarize their notes, or asks to use their Linko notes in the current task.
---

# Recall from Linko

Read only what the question needs, and change nothing. The user's explicit instructions take priority over this skill.

1. **Find.** For a question or topic, call `search` with a short query, then `fetch` the results you need; ids look like `note:abc123`. For lists with filters (a date range, a tag or topic, a resource type, unfinished resources), call `search_notes` or `search_resources`, passing the user's IANA `timezone` with dates. Use `list_tags_and_topics` to look up a tag or topic name.
2. **Read.** `fetch` returns up to eight chunks. If `metadata.truncated` is true and you need the rest, continue with `get_note` or `get_resource` from the cursor it names.
3. **Answer.**
   - Cite each note or resource you use with its Linko link.
   - Keep the user's notes apart from resource text: a resource holds Linko's saved text or description, not necessarily the full article or book. Say so when it matters.
   - If nothing matches, say so plainly. Don't present general knowledge as their notes. You may offer to save something new.
4. **Browse.** If the user would rather look through their library, call `open_linko` with a `query`. Opening Linko shares nothing with the conversation until the user adds a record.

Don't save, edit or reorganize anything while recalling unless the user asks.