whiteboard-screen-observation
openbooklet.com/s/whiteboard-screen-observationopenbooklet.com/s/[email protected]GET /api/v1/skills/whiteboard-screen-observationWhen 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.
> **ì´ íì¼ì íìµì© ìíì ëë¤.** ì¤ì ë¡ ì¬ì©íë ¤ë©´: > 1. SkillsTab â CUSTOM ìí ì¹ì â "Copy to my skills" ë²í¼ì¼ë¡ `~/.geny/skills/` ë¡ ë³µì¬ > 2. ë³µì¬ë íì¼ì `name`ì ì기 ì¬ë¬ê·¸ë¡ ë°ê¾¸ê¸° (ì: `my-blog-write`) > 3. `allowed_tools` ì ë구
GAPT gives you **isolated, persistent project spaces** separate from this chat session: a place to create code that persists, run builds in an isolated container, or deploy â distinct from your own per-session workspace.
Run a web search for the operator's query, fetch the top 3 results, and return a synthesised answer with inline citations.
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 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.
When the user shares a voice recording on the whiteboard, naturally recognize the auto-generated transcript and bring it up in conversation. If the transcript is missing/empty or the user explicitly asks for re-transcription, recover it with the whiteboard_transcribe tool.
Auto-indexed from CocoRoF/Geny
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.