mobile-inbox-triage

分类: 文档与知识管理 | 上传者: originalrgsec | 下载: 0 | 版本: v1.0（最新）

将移动设备上捕获的笔记处理并分类到黑曜石知识库中。每当用户说出“检查移动收件箱”、“处理移动笔记”、“分类收件箱”、“来自移动设备的内容”、“同步我的移动笔记”或任何对研究/移动收件箱文件夹的引用时，请使用此技能。还会在用户离开办公桌的任何会话开始时触发，或者当用户说“我在移动设备上捕获了一些想法”或“我从手机发送了一些笔记”时触发。如果研究/移动收件箱/包含未处理的笔记，此技能会将它们路由到正确的保管库位置。 --- # 移动收件箱分类此技能处理通过移动捕获（Claude 移动对话、语音备忘录或手动黑曜石移动输入的 iOS 快捷方式）到达黑曜石保险库的“research/mobile-inbox/”文件夹的笔记。每条笔记都会被读取、分析并传送到适当的保管库位置，然后进行存档。 ## 当此运行时用户显式触发此（“处理我的移动收件箱”、“分类收件箱”等），或者可以将其作为会话启动例程的一部分进行调用。该技能旨在批量处理 1 到 20 个音符。 ## 保管库位置黑曜石保管库（名为“Vault”）位于相对于工作空间根目录的“Obsidian/”。移动收件箱位于“Obsidian/research/mobile-inbox/”。处理后的笔记将移至“Obsidian/research/mobile-inbox/archive/”。 ## 处理步骤 ### 1. 扫描收件箱列出 `research/mobile-inbox/` 中的所有 `.md` 文件，不包括 `_index.md` 和 `archive/` 中已有的任何内容。如果没有找到文件，则告诉用户收件箱为空并停止。 ### 2. 阅读每个注释并对每个注释进行分类对于每个注释，请阅读完整内容并根据内容和任何 frontmatter 提示确定其类型： |分类|路线至 |描述 | |---|---|---| | **项目更新** | `projects/<tier>/<project>/status.md` |作为带日期的条目附加到相关项目的状态文件 | | **新想法或概念** | `项目/<层>/<项目>/` o

更新日志: Source: GitHub https://github.com/originalrgsec/open-workspace-builder

目录结构

当前层级: tree/main/content/skills/mobile-inbox-triage/

📄 SKILL.md 5.1 KB

SKILL.md

---
name: mobile-inbox-triage
description: >
  Process and triage notes captured on mobile into the Obsidian knowledge vault.
  Use this skill whenever the user says anything like "check the mobile inbox",
  "process mobile notes", "triage inbox", "what came in from mobile", "sync my
  mobile notes", or any reference to the research/mobile-inbox folder. Also trigger at
  the start of any session where the user has been away from their desk, or when
  the user says "I captured some ideas on mobile" or "I sent some notes from my
  phone." If research/mobile-inbox/ contains unprocessed notes, this skill handles
  routing them to the correct vault locations.
---

# Mobile Inbox Triage

This skill processes notes that arrived in the Obsidian vault's `research/mobile-inbox/` folder via mobile capture (iOS Shortcut from Claude mobile conversations, voice memos, or manual Obsidian mobile entry). Each note gets read, analyzed, and routed to the appropriate vault location, then archived.

## When This Runs

The user triggers this explicitly ("process my mobile inbox", "triage inbox", etc.) or it can be invoked as part of a session startup routine. The skill is designed to handle anywhere from 1 to 20 notes in a batch.

## Vault Location

The Obsidian vault (named "Vault") lives at `Obsidian/` relative to the workspace root. The mobile inbox is at `Obsidian/research/mobile-inbox/`. Processed notes get moved to `Obsidian/research/mobile-inbox/archive/`.

## Processing Steps

### 1. Scan the inbox

List all `.md` files in `research/mobile-inbox/` excluding `_index.md` and anything already in `archive/`. If no files are found, tell the user the inbox is empty and stop.

### 2. Read and classify each note

For each note, read the full content and determine its type based on the content and any frontmatter hints:

| Classification | Route To | Description |
|---|---|---|
| **Project update** | `projects/<tier>/<project>/status.md` | Append to the relevant project's status file as a dated entry |
| **New idea or concept** | `projects/<tier>/<project>/` or `research/inbox/` | Create a new note in the appropriate project folder, or research inbox if no project match |
| **Decision** | `decisions/` | Create a decision record using the `_templates/decision-record.md` template |
| **Research finding** | `research/inbox/` | Create a research note using the `_templates/research-note.md` template |
| **Action item only** | Report to user | Surface as a task to be created (in Asana if connected, otherwise just reported) |
| **Session continuation** | `sessions/` | If the note is a continuation of desktop work, create a session log entry |
| **Ambiguous** | Ask the user | Present the note content and ask where it should go |

The `projects:` frontmatter field is the primary routing key. If it contains a project name, route there first. If empty or missing, infer from content. If you cannot confidently classify, ask the user rather than guessing wrong.

### 3. Route the content

When routing, follow these rules:

- Preserve the original voice and content. Do not rewrite or summarize unless the note is clearly raw dictation that needs light cleanup (remove filler words, fix obvious transcription errors, but keep the substance intact).
- Use existing vault templates when creating new notes. Read the relevant template from `_templates/` before creating.
- When appending to an existing file (like a project status.md), add a dated section header: `### YYYY-MM-DD — Mobile capture` followed by the content.
- When creating new notes, use frontmatter consistent with the vault's conventions. Check a sibling note in the target folder if unsure about the expected frontmatter fields.
- Wiki-link to related notes where connections are obvious.

### 4. Archive processed notes

After successfully routing a note:
1. Update its frontmatter to set `processed: true`
2. Add a `routed_to:` field recording where the content went
3. Move the file to `research/mobile-inbox/archive/`

### 5. Report results

After processing all notes, give the user a brief summary: how many notes were processed, where each one was routed, and whether any need manual attention. Keep the summary tight — one line per note is sufficient.

## Edge Cases

- **Duplicate content:** If a mobile note contains content that already exists in the vault (the user captured the same idea twice), flag it and skip rather than creating duplicates.
- **Multiple topics in one note:** If a single note clearly covers two unrelated topics, split it into separate notes before routing. This is common with stream-of-consciousness mobile capture.
- **Empty notes:** Notes with only frontmatter and no real content should be deleted, not archived.
- **Notes referencing projects that don't exist yet:** Ask the user whether to create a new project folder or file the note under research.

## Obsidian MCP

If the Obsidian MCP server is available and responsive, use it for note operations (create-note, edit-note, move-note, read-note, search-vault). If it times out or is unavailable, fall back to direct filesystem operations — the vault is accessible at the filesystem path noted above.

登录后下载/点赞/收藏 ❤ 7 | ★ 0

mobile-inbox-triage

目录结构

SKILL.md

举报内容

提示