Menü
Access and maintain the notebook knowledge base with Obsidian markdown conventions.
Become a helpful co-worker in the workspace. Use it whenever you need to access, manage, or reference files.
Render rich interactive UI surfaces (tables, forms, cards, buttons) in the sidebar canvas or inline in chat using the render_ui tool.
Schedule recurring tasks (cron) and periodic agent check-ins (heartbeat).
Interact with companion devices (phones, laptops, headless servers) connected to Suzent.
Enables the agent to speak using text-to-speech.
Social messaging guidelines for Telegram, Slack, Discord, and Feishu. Best practices for formatting, character limits, and platform-specific features.
| name | notebook |
| description | Access and maintain the notebook knowledge base with Obsidian markdown conventions. |
The notebook is your personal vault and knowledge base. You read and write it using
standard file tools (ReadFileTool, WriteFileTool, EditFileTool, GlobTool,
GrepTool).
Path rules by execution mode:
/mnt/notebook.${MOUNT_NOTEBOOK} if mounted.Always read schema.md from the notebook root before doing any work in the notebook.
The schema defines this vault's structure, conventions, and rules. Follow it exactly.
Operational procedures:
notebook/ingest.md under your skills root.notebook/lint.md under your skills root.Three files at the notebook root are agent-maintained:
schema.md — vault conventions, folder layout, page types, index categories.
The authoritative source for how to work with this notebook. Read it first, every time.
index.md — catalog of synthesized pages. Revised freely on every ingest or query filing.
Format: - [[path/to/page]] — one-line summary, organized by category per schema.md.
log.md — append-only chronological record. Never edit existing entries.
Required prefix per entry: ## [YYYY-MM-DD] operation | description
Operations: ingest, query-filed, lint
[[page]] or [[path/to/page]] — use full vault paths> [!note], > [!warning]---
type: <per schema.md>
name: Canonical Name
aliases: []
tags: []
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
Standard sections: ## Overview, ## Key Facts, ## Related, ## Sources.
Use whatever additional sections the content warrants.
## Overview must be a coherent synthesis paragraph — not a stub, not a list.
## Related links must use full vault paths and explain the connection in one line.
When a conversation produces something durable — a comparison, analysis, synthesis, or decision — file it back into the notebook rather than letting it disappear.
index.mdquery-filed entry to log.md