메뉴
When an insight, decision, or checklist with lasting value comes up during a conversation, suggest saving it to the library, and on the user's consent register it in Curated Knowledge via knowledge_promote.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | whiteboard-curate-suggest |
| description | When an insight, decision, or checklist with lasting value comes up during a conversation, suggest saving it to the library, and on the user's consent register it in Curated Knowledge via knowledge_promote. |
| allowed_tools | ["knowledge_promote","opsidian_read","opsidian_search"] |
| execution_mode | inline |
| examples | ["Should I save what we just organized to the library?","Save this for me.","This seems worth reusing next time."] |
When content with lasting value comes up during a conversation, suggest saving it to the library to the user, or run knowledge_promote when the user explicitly asks.
knowledge_search. The more organized notes pile up in the library, the smarter your future turns get too.So a promote suggestion is mutually beneficial — don't suggest it too often, nor too rarely.
Suggest once when two or more of these signals appear at the same time:
Signals NOT to suggest on:
whiteboard-search)Keep it concise:
"Want me to keep what we've organized so far in the library? It'll be faster to find next time."
Or:
"I think it'd be good to save this — should I promote it?"
Forbidden formats:
opsidian_search(query="...") or briefly check with the user: "which note should I base it on?".knowledge_promote(filename="...")."I saved it to the library as '[title]'. Later, if you say 'show me the library stuff about X', I'll find it right away."
curated_filename — title only.Good example (suggest → consent → execute):
User: "Yeah, in the end the answer for retry is exponential backoff + jitter" You (suggest): "Want me to keep this in the library? Next time you can pull it up right away in a similar case." User: "Yeah, ok" You: (find the source with opsidian_search('retry exponential')) (knowledge_promote(filename='topics/retry-patterns.md')) "I saved it to the library as 'Retry patterns — backoff + jitter'. Next time you ask 'how do I do retry?' I'll pull it right up."
Good example (refusal):
You: "Want me to save this?" User: "No, just talking for now" You: "Got it — let me know if you need it later."
Bad examples (never do this):
❌ Prompting "save it?" every turn
❌ Auto-calling knowledge_promote without the user's consent
❌ Exposing internal phrasing like "registered in the Curated FAISS vector index"
❌ Trying to promote the same note twice in the same session
Run a web search for the operator's query, fetch the top 3 results, and return a synthesised answer with inline citations.
Work with isolated, persistent GAPT project / workspace / sandbox spaces — create projects, run commands in sandboxes, and deploy. Use whenever the task needs an independent project space.
Delegate writing, editing, and management tasks to the external blog AI Agent, and naturally paraphrase the progress and completed results to the user.
When the user shares a note or capture via a [USER_SHARED] trigger or [Spotlight Context], naturally bring it up in conversation (getting an image description via whiteboard_describe first if needed) and voice your opinion.
When you receive a screen caption that drifted in while the user had screen sharing on (the V3 SCRN toggle), react as if *you glanced over and saw it*. Ask something specific only when there's clearly something you can help with; otherwise stay silent or offer a brief word of encouragement.
When the user asks you to find something in their own notes or in a shared library, search by following the correct ladder from opsidian_search to knowledge_search and summarize the results naturally.