菜单
Process unprocessed items from the vault inbox. Extracts entities, routes information to the appropriate vault pages, and marks items as processed. Follows the vault schema for routing rules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | triage |
| description | Process unprocessed items from the vault inbox. Extracts entities, routes information to the appropriate vault pages, and marks items as processed. Follows the vault schema for routing rules. |
You are responsible for processing items from the vault inbox (inbox/).
External data lands there from emails, messages, meetings, and other
sources. Your job is to extract useful information and route it into the
structured knowledge base.
List pending items:
tower_vault_inbox_pending()
For each item (process up to 10 at a time): a. Read the full content if the preview isn't enough:
tower_vault_read(path: "inbox/emails/2026-04-29-budget-update.md")
b. Extract entities according to the vault schema (_schema.md):
_memory/people/<name>.md_memory/topics/<topic>.mdc. Update vault pages:
tower_vault_append(path: "_memory/people/alice.md", content: "- Approved Q2 budget (2026-04-29)")
tower_vault_append(path: "wiki/tasks.md", content: "- [ ] **Submit revised proposal** — per Alice's email (source: inbox/emails/2026-04-29-budget-update, added: 2026-04-29, priority: P2)")
d. Mark the item as processed:
tower_vault_inbox_done(itemId: "2026-04-29-budget-update", status: "processed", notes: "extracted 1 person update, 1 task")
Handle ambiguity: If you can't determine what entity type something is, or the schema doesn't cover it, mark it as failed with a note:
tower_vault_inbox_done(itemId: "...", status: "failed", notes: "unclear entity type — needs manual review")
Cross-reference: After processing, check if new information conflicts with existing knowledge:
tower_vault_search(query: "Alice role", scope: "memory")
Flag any conflicts to the user.
tower_vault_append for existing files.Browse the web using a real headed Chromium browser on a virtual desktop. Supports navigation, clicking, typing, screenshots, and full page interaction. The user can watch the browser in real-time via noVNC.
Interact with the virtual desktop: launch terminal emulators, control the mouse and keyboard, take screenshots, and manage windows. Works with any GUI application running on the display, not just browsers.
Persistent knowledge vault for Tower. Store facts, recall information, and maintain a self-editing core memory that persists across all sessions. Git-backed, Obsidian-compatible, human-editable.
Send and receive messages between Tower sessions. Supports direct messages, group messages, channels, threading, and priority levels. Messages are stored as markdown files and persist across restarts.
Task management via the vault. Read, add, update, and complete tasks stored in the vault knowledge base. Task format and location are defined in _schema.md.