drafts-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Drafts Manager Skill

Drafts Manager 技能

Triage the Drafts inbox using a hybrid AI + human confirmation workflow. Routes content to OmniFocus (tasks) or Obsidian (notes) based on content analysis.

采用AI+人工确认的混合工作流分类整理Drafts收件箱，基于内容分析将内容分配至OmniFocus（任务）或Obsidian（笔记）。

When to Activate

激活场景

Use this skill when user wants to:

Triage or process their Drafts inbox
Route notes to OmniFocus or Obsidian
Check what's captured in Drafts
Clean up old drafts

当用户需要以下操作时，可使用该技能：

分类整理或处理Drafts收件箱
将笔记分配至OmniFocus或Obsidian
查看Drafts中捕获的内容
清理旧的草稿

Architecture

架构

Two-Phase Hybrid Triage:

Export & Analyze - Drafts exports inbox → Geoffrey analyzes → presents suggestions
Confirm & Process - User confirms routing → Drafts processes each draft → archives

┌─────────┐  URL   ┌─────────┐  JSON   ┌─────────┐  Table  ┌──────┐
│Geoffrey │ ────► │ Drafts  │ ─────► │Geoffrey │ ──────► │ User │
│ trigger │       │ export  │        │ analyze │        │review│
└─────────┘       └─────────┘        └─────────┘        └──┬───┘
                                                           │
                                                     Confirmed
                                                           │
┌─────────┐  URL   ┌─────────┐  Routes  ┌──────────┐   ┌───▼────┐
│Geoffrey │ ────► │ Drafts  │ ───────► │OmniFocus │   │Process │
│ trigger │       │ process │         │ Obsidian │   │  list  │
└─────────┘       └────┬────┘         └──────────┘   └────────┘
                       │
                   Archives

两阶段混合分类整理流程：

导出与分析 - Drafts导出收件箱内容 → Geoffrey分析 → 呈现建议
确认与处理 - 用户确认分配路径 → Drafts处理每个草稿 → 归档

┌─────────┐  URL   ┌─────────┐  JSON   ┌─────────┐  Table  ┌──────┐
│Geoffrey │ ────► │ Drafts  │ ─────► │Geoffrey │ ──────► │ User │
│ trigger │       │ export  │        │ analyze │        │review│
└─────────┘       └─────────┘        └─────────┘        └──┬───┘
                                                           │
                                                     Confirmed
                                                           │
┌─────────┐  URL   ┌─────────┐  Routes  ┌──────────┐   ┌───▼────┐
│Geoffrey │ ────► │ Drafts  │ ───────► │OmniFocus │   │Process │
│ trigger │       │ process │         │ Obsidian │   │  list  │
└─────────┘       └────┬────┘         └──────────┘   └────────┘
                       │
                   Archives

Available Scripts

可用脚本

Scripts are in

./scripts/

directory. Run via:

bash

bun ./scripts/script-name.js

脚本位于

./scripts/

目录下，运行方式：

bash

bun ./scripts/script-name.js

trigger_export.js

Triggers the Drafts "Geoffrey Export Inbox" action via URL scheme.

Output: Path to exported JSON file

Use when: Starting triage

通过URL方案触发Drafts的「Geoffrey Export Inbox」动作。

输出： 导出的JSON文件路径

适用场景： 启动分类整理流程

trigger_process.js

Triggers the Drafts "Geoffrey Process Draft" action with routing instructions.

Parameters: uuid, destination, project, tags, folder

Use when: Processing confirmed drafts

结合分配指令触发Drafts的「Geoffrey Process Draft」动作。

参数： uuid, destination, project, tags, folder

适用场景： 处理已确认的草稿

Required Drafts Actions

必备Drafts动作

IMPORTANT: User must install these Drafts actions (found in

./actions/

重要提示： 用户必须安装以下Drafts动作（位于

./actions/

目录）：

Geoffrey Export Inbox

Exports all inbox drafts to a JSON file for Geoffrey to analyze.

Location:

~/Library/Mobile Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

Output format:

json

{
  "exported": "2025-11-23T10:30:00Z",
  "count": 5,
  "drafts": [
    {
      "uuid": "ABC123",
      "title": "First line of draft",
      "content": "Full content...",
      "tags": ["inbox"],
      "createdAt": "2025-11-22T14:00:00Z",
      "modifiedAt": "2025-11-22T14:00:00Z",
      "isFlagged": false
    }
  ]
}

将所有收件箱草稿导出为JSON文件，供Geoffrey分析。

存储位置：

~/Library/Mobile Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

输出格式：

json

{
  "exported": "2025-11-23T10:30:00Z",
  "count": 5,
  "drafts": [
    {
      "uuid": "ABC123",
      "title": "First line of draft",
      "content": "Full content...",
      "tags": ["inbox"],
      "createdAt": "2025-11-22T14:00:00Z",
      "modifiedAt": "2025-11-22T14:00:00Z",
      "isFlagged": false
    }
  ]
}

Geoffrey Process Draft

Processes a single draft based on routing instructions from URL parameters.

URL Parameters:

```
uuid
```
- Draft to process
```
destination
```
- "omnifocus", "obsidian", "archive", or "trash"
```
project
```
- OmniFocus project (if destination=omnifocus)
```
tags
```
- Comma-separated tags (if destination=omnifocus)
```
dueDate
```
- Due date (if destination=omnifocus)
```
folder
```
- Obsidian folder (if destination=obsidian)

基于URL参数中的分配指令处理单个草稿。

URL参数：

```
uuid
```
- 待处理的草稿
```
destination
```
- 目标位置："omnifocus", "obsidian", "archive", 或 "trash"
```
project
```
- OmniFocus项目（当destination=omnifocus时）
```
tags
```
- 逗号分隔的标签（当destination=omnifocus时）
```
dueDate
```
- 截止日期（当destination=omnifocus时）
```
folder
```
- Obsidian文件夹（当destination=obsidian时）

Content Analysis Rules

内容分析规则

When analyzing drafts, look for these signals:

分析草稿时，需关注以下信号：

Route to OmniFocus (Task)

分配至OmniFocus（任务）

Signals:

Starts with action verb: "call", "email", "buy", "schedule", "review", "check"
Contains: "todo", "task", "@due", "@defer"
Short (< 50 words)
Contains person names
Shopping lists or errands

Apply omnifocus-manager routing rules for project/tag assignment

信号：

以动作动词开头："call"（致电）、"email"（发邮件）、"buy"（购买）、"schedule"（安排）、"review"（审核）、"check"（检查）
包含关键词："todo"、"task"、"@due"、"@defer"
内容简短（少于50词）
包含人名
购物清单或跑腿事项

应用omnifocus-manager的项目/标签分配规则

Route to Obsidian (Note)

分配至Obsidian（笔记）

Signals:

Longer content (> 100 words)
Meeting notes: "meeting with", "discussed", "attendees"
Ideas/brainstorms: "idea:", "thought:", "what if"
Reference material: links, quotes, research
Journal entries: "today I", feelings, reflections

信号：

内容较长（超过100词）
会议记录：包含"meeting with"（与...开会）、"discussed"（讨论）、"attendees"（参会者）
想法/头脑风暴：包含"idea:"（想法：）、"thought:"（思考：）、"what if"（如果...）
参考资料：包含链接、引用、研究内容
日志条目：包含"today I"（今天我）、感受、反思

Archive in Drafts

在Drafts中归档

Signals:

Reference that may be needed again
Snippets of code or text
Temporary notes that are now done

信号：

未来可能需要的参考内容
代码或文本片段
已完成的临时笔记

Delete (Trash)

删除（移入回收站）

Signals:

Empty or nearly empty
Test/scratch content
Duplicates
Outdated info no longer needed

信号：

空或接近空的内容
测试/草稿内容
重复内容
不再需要的过时信息

Obsidian Routing Rules

Obsidian分配规则

Content Type	Folder	Frontmatter
Meeting notes	`Meetings/`	date, attendees, topics
Ideas/brainstorms	`Geoffrey/Inbox/`	tags, created
Research	`Reference/`	source, tags, related
Journal	`Journal/`	date
General notes	`Geoffrey/Inbox/`	tags, created

Frontmatter template:

yaml

---
created: {{date}}
source: drafts
tags: [from-drafts]
related: []
---

内容类型	文件夹	前置元数据
会议记录	`Meetings/`	日期、参会者、议题
想法/头脑风暴	`Geoffrey/Inbox/`	标签、创建时间
研究资料	`Reference/`	来源、标签、相关内容
日志	`Journal/`	日期
通用笔记	`Geoffrey/Inbox/`	标签、创建时间

前置元数据模板：

yaml

---
created: {{date}}
source: drafts
tags: [from-drafts]
related: []
---

Main Workflow: Triage Drafts

主工作流：分类整理草稿

Phase 1: Export & Analyze

阶段1：导出与分析

Trigger export:

bash

open "drafts://x-callback-url/runAction?action=Geoffrey%20Export%20Inbox"

Wait for export file (2-3 seconds)

Read exported JSON:

bash

cat ~/Library/Mobile\ Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

Analyze each draft using content signals above

Present suggestions table:

markdown

## Drafts Inbox Triage

Found **5 drafts** to process:

| # | Title | Suggestion | Destination | Details |
|---|-------|------------|-------------|---------|
| 1 | Call John about... | Task | OmniFocus | Project: Meetings, Tags: John, Follow Up |
| 2 | Meeting notes 11/22 | Note | Obsidian | Folder: Meetings/ |
| 3 | [empty] | Delete | Trash | Empty draft |
| 4 | Shopping list | Task | OmniFocus | Project: Single Actions, Tags: Chores |
| 5 | Idea for app... | Note | Obsidian | Folder: Geoffrey/Inbox/ |

**Questions:**
- #4: Should this go to a specific store location tag?

Which numbers need changes? (Or type "process all" to confirm)

触发导出：

bash

open "drafts://x-callback-url/runAction?action=Geoffrey%20Export%20Inbox"

等待导出文件生成（2-3秒）

读取导出的JSON文件：

bash

cat ~/Library/Mobile\ Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

根据上述内容信号分析每个草稿

呈现建议表格：

markdown

## Drafts收件箱分类整理

发现**5份草稿**待处理：

| 序号 | 标题 | 建议 | 目标位置 | 详情 |
|---|-------|------------|-------------|---------|
| 1 | 致电John关于... | 任务 | OmniFocus | 项目：Meetings，标签：John, Follow Up |
| 2 | 11/22会议记录 | 笔记 | Obsidian | 文件夹：Meetings/ |
| 3 | [空] | 删除 | 回收站 | 空草稿 |
| 4 | 购物清单 | 任务 | OmniFocus | 项目：Single Actions，标签：Chores |
| 5 | 应用创意... | 笔记 | Obsidian | 文件夹：Geoffrey/Inbox/ |

**疑问：**
- 第4项：是否需要添加特定商店位置标签？

哪些序号的内容需要调整？（或输入"process all"确认全部处理）

Phase 2: Process & Archive

阶段2：处理与归档

For each confirmed draft, trigger process action:

bash

# OmniFocus task
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=ABC123&destination=omnifocus&project=Meetings&tags=John,Follow%20Up&dueDate=2025-11-30"

# Obsidian note
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=DEF456&destination=obsidian&folder=Meetings"

# Archive
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=GHI789&destination=archive"

# Delete
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=JKL012&destination=trash"

Report results:

markdown

## Summary
Processed 5 drafts from inbox

## Actions
- 2 tasks created in OmniFocus
- 2 notes saved to Obsidian
- 1 draft deleted

## Status
✅ Complete

## Next Steps
- Review tasks in OmniFocus inbox
- Check Obsidian notes in Geoffrey/Inbox/

针对每份已确认的草稿，触发处理动作：

bash

# OmniFocus任务
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=ABC123&destination=omnifocus&project=Meetings&tags=John,Follow%20Up&dueDate=2025-11-30"

# Obsidian笔记
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=DEF456&destination=obsidian&folder=Meetings"

# 归档
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=GHI789&destination=archive"

# 删除
open "drafts://x-callback-url/runAction?action=Geoffrey%20Process%20Draft&uuid=JKL012&destination=trash"

报告处理结果：

markdown

## 总结
已处理收件箱中的5份草稿

## 操作详情
- 在OmniFocus中创建了2个任务
- 向Obsidian中保存了2条笔记
- 删除了1份草稿

## 状态
✅ 完成

## 下一步操作
- 查看OmniFocus收件箱中的任务
- 检查Obsidian中Geoffrey/Inbox/目录下的笔记

Error Handling

错误处理

Drafts not running:

Status: ❌ Failed
Error: Drafts app is not running. Please open Drafts and try again.

Action not installed:

Status: ❌ Failed
Error: Drafts action "Geoffrey Export Inbox" not found.
Please install from: skills/drafts-manager/actions/

Export file not found:

Status: ⚠️ Partial
Error: Export file not created. Drafts may have timed out.
Try running the action manually in Drafts.

OmniFocus not running:

Status: ⚠️ Partial
Warning: OmniFocus not running. Task creation may have failed.
Please verify tasks were created.

Drafts未运行：

状态：❌ 失败
错误：Drafts应用未运行，请打开Drafts后重试。

动作未安装：

状态：❌ 失败
错误：未找到Drafts动作「Geoffrey Export Inbox」。
请从以下路径安装：skills/drafts-manager/actions/

导出文件未找到：

状态：⚠️ 部分完成
错误：未生成导出文件，Drafts可能超时。
请尝试在Drafts中手动运行该动作。

OmniFocus未运行：

状态：⚠️ 部分完成
警告：OmniFocus未运行，任务创建可能失败。
请验证任务是否已创建。

Installation

安装步骤

1. Install Drafts Actions

1. 安装Drafts动作

Import the action files from

./actions/

Option A: Import from file

Open Drafts
Go to Actions → Manage Actions

Import from

actions/geoffrey-export-inbox.draftsAction

Import from

actions/geoffrey-process-draft.draftsAction

Option B: Create manually

Open Drafts
Create new action "Geoffrey Export Inbox"
Add Script step with code from
```
actions/geoffrey-export-inbox.js
```
Repeat for "Geoffrey Process Draft"

从

./actions/

目录导入动作文件：

选项A：从文件导入

打开Drafts
进入「动作」→「管理动作」

从

actions/geoffrey-export-inbox.draftsAction

导入

从

actions/geoffrey-process-draft.draftsAction

导入

选项B：手动创建

打开Drafts
创建新动作「Geoffrey Export Inbox」
添加脚本步骤，粘贴
```
actions/geoffrey-export-inbox.js
```
中的代码
重复上述步骤创建「Geoffrey Process Draft」动作

2. Verify Installation

2. 验证安装

Run:

open "drafts://x-callback-url/runAction?action=Geoffrey%20Export%20Inbox"

Check for export file at:

~/Library/Mobile Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

运行以下命令：

open "drafts://x-callback-url/runAction?action=Geoffrey%20Export%20Inbox"

检查导出文件是否存在于以下路径：

~/Library/Mobile Documents/iCloud~com~agiletortoise~Drafts5/Documents/geoffrey-export.json

Tips for Best Results

最佳实践技巧

Tagging in Drafts

Drafts中的标签使用

Use these tags for manual pre-routing:

```
task
```
- Force route to OmniFocus
```
note
```
- Force route to Obsidian
```
archive
```
- Keep in Drafts archive
```
delete
```
- Trash without review

使用以下标签进行手动预分配：

```
task
```
- 强制分配至OmniFocus
```
note
```
- 强制分配至Obsidian
```
archive
```
- 保留在Drafts归档中
```
delete
```
- 直接移入回收站无需审核

Quick Capture Patterns

快速捕获规则

When capturing to Drafts, these patterns help AI routing:

Start tasks with verbs: "Call", "Email", "Buy"
Start notes with context: "Meeting:", "Idea:", "Note:"
Use @ for OmniFocus hints: "@due(tomorrow)", "@project(Work)"

在Drafts中捕获内容时，以下规则有助于AI自动分配：

任务以动词开头：如"Call"（致电）、"Email"（发邮件）、"Buy"（购买）
笔记以场景开头：如"Meeting:"（会议：）、"Idea:"（想法：）、"Note:"（笔记：）
使用@符号提供OmniFocus提示：如"@due(tomorrow)"（@截止日期(明天)）、"@project(Work)"（@项目(工作)）

Regular Triage

定期分类整理

Best practice: Triage Drafts daily to keep inbox small

Morning: Process yesterday's captures
Evening: Quick review of day's notes

最佳实践：每日分类整理Drafts收件箱，保持收件箱简洁

早晨：处理前一天捕获的内容
晚上：快速回顾当天的笔记

Learned Routing Patterns

已学习的分配规则

These patterns were learned through actual triage sessions with the user.

以下规则来自与用户的实际分类整理会话。

Content Type → Destination

内容类型→目标位置

Content Type	Destination	Obsidian Folder	OmniFocus Details
Meeting notes	Obsidian	`Meetings/2025/`	-
Conference notes	Obsidian	`Meetings/2025/`	-
Development roadmap	Obsidian	`Work/[Project]/Roadmap.md`	Format as checklist
API keys/credentials	Delete	-	Security risk
Error logs/JSON junk	Delete	-	Cruft
Random passwords	Delete	-	Cruft
Contact info	Contacts app	-	Also create follow-up task
Book recommendations	OmniFocus	-	Tags: Reading
Gift ideas	OmniFocus	-	Tags: Chores, Shopping
Action items from meetings	OmniFocus	-	Tags: Follow Up
Reference links (AI, UDL)	Obsidian	`Reference/`	-
Personal project ideas	OmniFocus	-	Tags: Coding
Presentation schedules	Obsidian	`Work/Presentations/`	Future dates → tasks
Survey links	OmniFocus	-	Include links in notes

内容类型	目标位置	Obsidian文件夹	OmniFocus详情
会议记录	Obsidian	`Meetings/2025/`	-
会议记录	Obsidian	`Meetings/2025/`	-
开发路线图	Obsidian	`Work/[Project]/Roadmap.md`	格式化为 checklist
API密钥/凭证	删除	-	安全风险
错误日志/JSON垃圾内容	删除	-	无效内容
随机密码	删除	-	无效内容
联系信息	通讯录应用	-	同时创建跟进任务
书籍推荐	OmniFocus	-	标签：Reading
礼物创意	OmniFocus	-	标签：Chores, Shopping
会议行动项	OmniFocus	-	标签：Follow Up
参考链接（AI、UDL）	Obsidian	`Reference/`	-
个人项目创意	OmniFocus	-	标签：Coding
演示日程	Obsidian	`Work/Presentations/`	未来日期→转换为任务
调查链接	OmniFocus	-	笔记中包含链接

Signals for Each Destination

各目标位置的识别信号

→ OmniFocus Task:

Starts with action verbs: "Submit", "Call", "Email", "Build", "Add"
Contains due date context: "first week of December", "by end of year"
Travel approvals, surveys to send, podcasts to record
Book to read, thing to buy, project to build
Multiple action items → single task with checklist in notes

→ Obsidian Note:

Meeting notes (look for date, attendees, discussion points)
Conference notes (look for session titles, speakers, links)
Development docs with code/commands (wrap in code blocks)
Reference material with links to external resources
Topic brainstorms and idea lists

→ Contacts App:

Contains name + phone/email
Create contact AND follow-up task if there's an action

→ Delete:

Empty or nearly empty
JSON/error logs
API keys (security)
Random strings/passwords
Test data that's no longer needed

→ Archive in Drafts:

Outdated but potentially useful later
Reference that may be needed again

→ OmniFocus任务：

以动作动词开头：如"Submit"（提交）、"Call"（致电）、"Email"（发邮件）、"Build"（构建）、"Add"（添加）
包含截止日期上下文：如"first week of December"（12月第一周）、"by end of year"（年底前）
差旅审批、待发送的调查、待录制的播客
待阅读的书籍、待购买的物品、待构建的项目
多个行动项→转换为单个任务，行动项作为笔记中的checklist

→ Obsidian笔记：

会议记录（包含日期、参会者、讨论要点）
会议记录（包含会话标题、演讲者、链接）
包含代码/命令的开发文档（用代码块包裹）
包含外部资源链接的参考资料
主题头脑风暴和创意列表

→ 通讯录应用：

包含姓名+电话/邮箱
若有行动项，需同时创建联系人与跟进任务

→ 删除：

空或接近空的内容
JSON/错误日志
API密钥（安全考虑）
随机字符串/密码
不再需要的测试数据

→ 在Drafts中归档：

过时但未来可能有用的内容
未来可能需要的参考资料

Project/Folder Mappings

项目/文件夹映射

Obsidian Folders:

```
Meetings/2025/
```
- All meeting and conference notes
```
Work/AI-Studio/
```
- AI Studio development docs
```
Work/Jocular-Kangaroo/
```
- Jocular Kangaroo project
```
Work/Presentations/
```
- Presentation archives
```
Geoffrey/
```
- Geoffrey roadmap and ideas
```
Reference/
```
- Reference materials and links

OmniFocus Projects (go to Inbox if not found):

CoSN Work - CoSN-related tasks
Meetings - Follow-ups with people
Research for Future Plans - Books, research tasks

OmniFocus Tags:

Follow Up - Tasks requiring follow-up
Reading - Books to read
Chores - Shopping, errands
Coding - Development tasks
Geoffrey - AI-assistable tasks
Email - Tasks requiring email

Obsidian文件夹：

```
Meetings/2025/
```
- 所有会议和会议记录
```
Work/AI-Studio/
```
- AI Studio开发文档
```
Work/Jocular-Kangaroo/
```
- Jocular Kangaroo项目
```
Work/Presentations/
```
- 演示文档归档
```
Geoffrey/
```
- Geoffrey路线图和创意
```
Reference/
```
- 参考资料和链接

OmniFocus项目（未找到则进入收件箱）：

CoSN Work - 与CoSN相关的任务
Meetings - 与人跟进的任务
Research for Future Plans - 书籍、研究类任务

OmniFocus标签：

Follow Up - 需要跟进的任务
Reading - 待阅读书籍
Chores - 购物、跑腿事项
Coding - 开发任务
Geoffrey - 可由AI辅助的任务
Email - 需要发送邮件的任务

Special Handling

特殊处理规则

Multi-item notes:

If note contains multiple distinct items, either:
- Create single task with items as checklist in notes
- Split into separate tasks (ask user preference)

Development roadmaps:

Format as Obsidian file with checkboxes
Use
```
- [ ]
```
for pending items
Use
```
- [x]
```
for completed items
Include code blocks for commands

Sensitive data:

API keys → Delete immediately
Student investigation data → Archive carefully, don't expose
Credentials → Delete or move to secure storage

Contact + Task pattern:

Add to Contacts app via add_contact.js
Create follow-up task with contact details in notes
Example: "Send maps to Kim Crowder" with email in notes

多条目笔记：

若笔记包含多个独立条目，可选择：
- 创建单个任务，条目作为笔记中的checklist
- 拆分为多个独立任务（询问用户偏好）

开发路线图：

格式化为Obsidian文件，包含复选框
使用
```
- [ ]
```
表示待完成项
使用
```
- [x]
```
表示已完成项
包含代码块以存放命令

敏感数据：

API密钥→立即删除
学生调查数据→谨慎归档，避免泄露
凭证→删除或移至安全存储

联系人+任务场景：

通过add_contact.js添加至通讯录应用
创建跟进任务，笔记中包含联系人详情
示例："Send maps to Kim Crowder"（向Kim Crowder发送地图），笔记中包含邮箱信息

drafts-manager

Original

Translation

Drafts Manager Skill

Drafts Manager 技能

When to Activate

激活场景

Architecture

架构

Available Scripts

可用脚本

trigger_export.js

trigger_export.js

trigger_process.js

trigger_process.js

Required Drafts Actions

必备Drafts动作

Geoffrey Export Inbox

Geoffrey Export Inbox

Geoffrey Process Draft

Geoffrey Process Draft

Content Analysis Rules

内容分析规则

Route to OmniFocus (Task)

分配至OmniFocus（任务）

Route to Obsidian (Note)

分配至Obsidian（笔记）

Archive in Drafts

在Drafts中归档

Delete (Trash)

删除（移入回收站）

Obsidian Routing Rules

Obsidian分配规则

Main Workflow: Triage Drafts

主工作流：分类整理草稿

Phase 1: Export & Analyze

阶段1：导出与分析

Phase 2: Process & Archive

阶段2：处理与归档

Error Handling

错误处理

Installation

安装步骤

1. Install Drafts Actions

1. 安装Drafts动作

2. Verify Installation

2. 验证安装

Tips for Best Results

最佳实践技巧

Tagging in Drafts

Drafts中的标签使用

Quick Capture Patterns

快速捕获规则

Regular Triage

定期分类整理

Learned Routing Patterns

已学习的分配规则

Content Type → Destination

内容类型→目标位置

Signals for Each Destination

各目标位置的识别信号

Project/Folder Mappings

项目/文件夹映射

Special Handling

特殊处理规则

Future Enhancements

未来增强功能