Update to Nacre
Snapshot Nov 7, 2026 · 00:09 UTC · version 1.0.3
Collection source: downloaded plugin package.
Instructions updated for nacre
Skill instructions — Now says: Nacre saves only when the user asks, for example "save this to Nacre". It's fine to mention once that they can say that. - One save per request. `summary` is...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 6, 2026 · 18:21 UTC
Save only when the user asks. Never save on your own, even after a long explanation. If it fits, you may mention once that they can say "save this to Nacre". - Call `save_to_nacre` straight away, once per request. Don't plan or polish fi...
Nov 7, 2026 · 00:09 UTC
Nacre saves only when the user asks, for example "save this to Nacre". It's fine to mention once that they can say that. - One save per request. `summary` is a short list of the key facts they're learning, one line each, about 3 to 8 lin...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -17,10 +17,9 @@ ## Saving -- Save only when the user asks. Never save on your own, even after a long explanation. If it fits, you may mention once that they can say "save this to Nacre". -- Call `save_to_nacre` straight away, once per request. Don't plan or polish first. -- `summary` is a quick list of the key facts from this chat, one short line each, about 3 to 8 lines, as they already appear above. Nacre writes the questions itself. -- Never send the whole chat. Leave out chit-chat, to-dos, and anything personal or confidential: passwords, health, money, relationships, contact details. If the user asks to save a password or similar secret, don't call Nacre; say Nacre is for things they're learning and suggest a password manager. +- Nacre saves only when the user asks, for example "save this to Nacre". It's fine to mention once that they can say that. +- One save per request. `summary` is a short list of the key facts they're learning, one line each, about 3 to 8 lines. Nacre writes the questions itself. +- Nacre is for things being learned, such as ideas and facts. Passwords, health, money, relationships and contact details don't belong in it; for a password, a password manager is the right place. - Add a short `title` when the user names the topic, and set `source_app` to `chatgpt`. - After saving, give the link from the result. The questions are ready about a minute later. Don't invent a number of questions.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: nacre\ndescription: Use Nacre when the user asks to save what they learned to Nacre, asks to be quizzed or tested on what they saved, or asks what's due in Nacre or how their streak is going.\n---\n\n# Nacre\n\nNacre helps the user remember what they learn. It turns key ideas from a chat into short review questions and brings them back at the right time. The questions are answered in the Nacre app, not in the chat. Keep every reply light, short and encouraging.\n\n## When to use each tool\n\n| The user says something like | Call | Then |\n| --- | --- | --- |\n| \"Save this to Nacre\", \"add that to Nacre\", \"remember this in Nacre\" | `save_to_nacre` | Say in one sentence that it's saved and give the link to their questions in Nacre |\n| \"Quiz me from Nacre\", \"test me on what I saved\" | `quiz_me` | Say how many questions are ready and give the link that opens them in Nacre |\n| \"What's due in Nacre today?\", \"how's my streak?\" | `nacre_today` | Say how many questions are due and the streak in days |\n\n## Saving\n\n- Save only when the user asks. Never save on your own, even after a long explanation. If it fits, you may mention once that they can say \"save this to Nacre\".\n- Call `save_to_nacre` straight away, once per request. Don't plan or polish first.\n- `summary` is a quick list of the key facts from this chat, one short line each, about 3 to 8 lines, as they already appear above. Nacre writes the questions itself.\n- Never send the whole chat. Leave out chit-chat, to-dos, and anything personal or confidential: passwords, health, money, relationships, contact details. If the user asks to save a password or similar secret, don't call Nacre; say Nacre is for things they're learning and suggest a password manager.\n- Add a short `title` when the user names the topic, and set `source_app` to `chatgpt`.\n- After saving, give the link from the result. The questions are ready about a minute later. Don't invent a number of questions.\n\n## Quizzing\n\n- Never write or ask quiz questions in the chat yourself, even if the user asks to be quizzed \"here\". Call `quiz_me` and give its link: the questions are answered and marked in Nacre, where the streak is kept.\n\n## If something isn't possible\n\n- If a tool says nothing was saved (for example the account is not finished, saves are used up for now, or Nacre is invite only), pass that on in one kind sentence with the link it gives. Don't mention plans, prices or upgrades.\n- Each save adds a new set; Nacre never changes or deletes what's already saved, so don't retry a save that succeeded.\n"
"---\nname: nacre\ndescription: Use Nacre when the user asks to save what they learned to Nacre, asks to be quizzed or tested on what they saved, or asks what's due in Nacre or how their streak is going.\n---\n\n# Nacre\n\nNacre helps the user remember what they learn. It turns key ideas from a chat into short review questions and brings them back at the right time. The questions are answered in the Nacre app, not in the chat. Keep every reply light, short and encouraging.\n\n## When to use each tool\n\n| The user says something like | Call | Then |\n| --- | --- | --- |\n| \"Save this to Nacre\", \"add that to Nacre\", \"remember this in Nacre\" | `save_to_nacre` | Say in one sentence that it's saved and give the link to their questions in Nacre |\n| \"Quiz me from Nacre\", \"test me on what I saved\" | `quiz_me` | Say how many questions are ready and give the link that opens them in Nacre |\n| \"What's due in Nacre today?\", \"how's my streak?\" | `nacre_today` | Say how many questions are due and the streak in days |\n\n## Saving\n\n- Nacre saves only when the user asks, for example \"save this to Nacre\". It's fine to mention once that they can say that.\n- One save per request. `summary` is a short list of the key facts they're learning, one line each, about 3 to 8 lines. Nacre writes the questions itself.\n- Nacre is for things being learned, such as ideas and facts. Passwords, health, money, relationships and contact details don't belong in it; for a password, a password manager is the right place.\n- Add a short `title` when the user names the topic, and set `source_app` to `chatgpt`.\n- After saving, give the link from the result. The questions are ready about a minute later. Don't invent a number of questions.\n\n## Quizzing\n\n- Never write or ask quiz questions in the chat yourself, even if the user asks to be quizzed \"here\". Call `quiz_me` and give its link: the questions are answered and marked in Nacre, where the streak is kept.\n\n## If something isn't possible\n\n- If a tool says nothing was saved (for example the account is not finished, saves are used up for now, or Nacre is invite only), pass that on in one kind sentence with the link it gives. Don't mention plans, prices or upgrades.\n- Each save adds a new set; Nacre never changes or deletes what's already saved, so don't retry a save that succeeded.\n"
Full snapshot data
{
"description": "Use Nacre when the user asks to save what they learned to Nacre, asks to be quizzed or tested on what they saved, or asks what's due in Nacre or how their streak is going.",
"included_files": [],
"name": "nacre",
"skill_md_contents": "---\nname: nacre\ndescription: Use Nacre when the user asks to save what they learned to Nacre, asks to be quizzed or tested on what they saved, or asks what's due in Nacre or how their streak is going.\n---\n\n# Nacre\n\nNacre helps the user remember what they learn. It turns key ideas from a chat into short review questions and brings them back at the right time. The questions are answered in the Nacre app, not in the chat. Keep every reply light, short and encouraging.\n\n## When to use each tool\n\n| The user says something like | Call | Then |\n| --- | --- | --- |\n| \"Save this to Nacre\", \"add that to Nacre\", \"remember this in Nacre\" | `save_to_nacre` | Say in one sentence that it's saved and give the link to their questions in Nacre |\n| \"Quiz me from Nacre\", \"test me on what I saved\" | `quiz_me` | Say how many questions are ready and give the link that opens them in Nacre |\n| \"What's due in Nacre today?\", \"how's my streak?\" | `nacre_today` | Say how many questions are due and the streak in days |\n\n## Saving\n\n- Nacre saves only when the user asks, for example \"save this to Nacre\". It's fine to mention once that they can say that.\n- One save per request. `summary` is a short list of the key facts they're learning, one line each, about 3 to 8 lines. Nacre writes the questions itself.\n- Nacre is for things being learned, such as ideas and facts. Passwords, health, money, relationships and contact details don't belong in it; for a password, a password manager is the right place.\n- Add a short `title` when the user names the topic, and set `source_app` to `chatgpt`.\n- After saving, give the link from the result. The questions are ready about a minute later. Don't invent a number of questions.\n\n## Quizzing\n\n- Never write or ask quiz questions in the chat yourself, even if the user asks to be quizzed \"here\". Call `quiz_me` and give its link: the questions are answered and marked in Nacre, where the streak is kept.\n\n## If something isn't possible\n\n- If a tool says nothing was saved (for example the account is not finished, saves are used up for now, or Nacre is invite only), pass that on in one kind sentence with the link it gives. Don't mention plans, prices or upgrades.\n- Each save adds a new set; Nacre never changes or deletes what's already saved, so don't retry a save that succeeded.\n"
}SHA-256 of public snapshot: 112d4e86cc45f41a12c9f63b7debbcf8ecb2cf848f6d8f6777c1b79821900043