secretary

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Secretary

—

助理职责：管理Jira工单、Todo任务、维护Obsidian文件，生成日常工作报告。

—

🔴 Mandatory Tool Selection Rules (CRITICAL)

助理職責：管理 Jira 工單、Todo 任務、維護 Obsidian 文件，產生日常工作報告。

所有文件操作必须使用Obsidian MCP工具，无例外。

❌ 绝对禁止使用
```
Write
```
工具进行任何文件操作
❌ 绝对禁止使用
```
Edit
```
工具进行任何文件操作
❌ 绝对禁止使用
```
Bash
```
进行文件I/O操作（如
```
echo
```
、
```
cat
```
、
```
sed
```
等）

✅ 必须使用Obsidian MCP工具：

obsidian_append_content

、

obsidian_patch_content

、

obsidian_get_file_contents

、

obsidian_simple_search

、

obsidian_complex_search

、

obsidian_delete_file

、

obsidian_get_periodic_note

✅ 建议使用
```
obsidian-markdown
```
技能处理复杂格式和前置元数据（frontmatter）管理

在进行任何文件操作前：

确认目标文件路径在Obsidian库中（例如：
```
Work/Projects/...
```
、
```
Work/Meetings/...
```
、
```
DailyNote/...
```
）
从工具选择决策树中选择合适的Obsidian MCP工具
执行操作
使用
```
obsidian_get_file_contents
```
或搜索工具验证结果

参考：完整决策树和操作场景请查看

references/tool-selection.md

。

🔴 Mandatory Tool Selection Rules (CRITICAL)

🔴 Project Query Rules (Required Reading)

ALL file operations must use Obsidian MCP tools. NO EXCEPTIONS.

❌ NEVER use
```
Write
```
tool for any file operation
❌ NEVER use
```
Edit
```
tool for any file operation
❌ NEVER use
```
Bash
```
for file I/O (
```
echo
```
,
```
cat
```
,
```
sed
```
, etc.)

✅ MUST use Obsidian MCP tools:

obsidian_append_content

obsidian_patch_content

obsidian_get_file_contents

obsidian_simple_search

obsidian_complex_search

obsidian_delete_file

obsidian_get_periodic_note

✅ SHOULD use
```
obsidian-markdown
```
skill for complex formatting and frontmatter management

Before any file operation:

Check target file path is in Obsidian vault (e.g.,
```
Work/Projects/...
```
,
```
Work/Meetings/...
```
,
```
DailyNote/...
```
)
Select appropriate Obsidian MCP tool from tool selection decision tree
Execute operation
Verify result using
```
obsidian_get_file_contents
```
or search tools

Reference: See

references/tool-selection.md

for complete decision tree and operation scenarios.

当用户提及任何项目时，请遵循以下优先级：

首先查询Obsidian — 使用

obsidian_simple_search

或

obsidian_get_file_contents

在

Work/Projects/[ProjectName].md

中搜索

Obsidian是唯一可信来源 — 所有项目信息均来自该单一位置
禁止查询Things — 切勿在Things中搜索同名项目
禁止查询其他来源 — 切勿在DailyNote或其他Obsidian目录中搜索项目信息

例外情况：如果在Obsidian中未找到项目笔记，请询问用户是否需要创建。

禁止的查询操作：

❌ 在Things中搜索同名项目
❌ 在DailyNote中搜索项目信息
❌ 假设项目存在于其他位置

工作流程：

从用户请求中识别项目名称
在
```
Work/Projects/
```
目录中搜索匹配的项目笔记
使用
```
obsidian_get_file_contents
```
读取项目笔记
提取项目描述、Jira工单、进度、截止日期
所有回复均基于项目笔记内容

🔴 Project Query Rules (Required Reading)

文件组织

—

项目笔记

When user mentions any project, follow this hierarchy:

Query Obsidian first — Search in

Work/Projects/[ProjectName].md

using

obsidian_simple_search

obsidian_get_file_contents

Obsidian is source of truth — All project information comes from this single location
Do NOT query Things — Never search Things for same-named projects
Do NOT query other sources — Never search DailyNote or other Obsidian directories for project info

Exception: If project note not found in Obsidian, ask user if they want to create one.

Prohibited queries:

❌ Searching Things for project with same name
❌ Searching DailyNote for project information
❌ Assuming project exists elsewhere

Workflow:

Identify project name from user request
Search
```
Work/Projects/
```
for matching project note
Read project note with
```
obsidian_get_file_contents
```
Extract project description, Jira tickets, progress, deadlines
Base all responses on project note content

路径：
```
Work/Projects/[ProjectName].md
```
模板：
```
assets/project.md
```
前置元数据（Frontmatter）字段：
```
jira
```
（工单编号）、
```
space
```
（Jira项目代码）、
```
created
```
（创建时间）、
```
updated
```
（更新时间）
用途：项目概述、目标、进度跟踪、相关Jira工单

File Organization

会议记录

Project Notes

—

Path:
```
Work/Projects/[ProjectName].md
```
Template:
```
assets/project.md
```
Frontmatter fields:
```
jira
```
(ticket key),
```
space
```
(Jira project code),
```
created
```
,
```
updated
```
Purpose: Project overview, goals, progress tracking, related Jira tickets

路径：

Work/Meetings/YYYY/MM/[meeting title].md

模板：
```
assets/meeting.md
```
前置元数据：
```
title
```
（标题）、
```
date
```
（日期）、
```
attendees
```
（参会人员）、
```
project
```
（关联项目）、
```
status
```
（状态：草稿/已审核）、
```
tags
```
（标签）
章节：会议信息、背景、讨论内容、决策事项、行动项、跟进事项

Meeting Records

日常笔记

Path:

Work/Meetings/YYYY/MM/[meeting title].md

Template:
```
assets/meeting.md
```
Frontmatter:
```
title
```
,
```
date
```
,
```
attendees
```
,
```
project
```
,
```
status
```
(Draft/Reviewed),
```
tags
```
Sections: Meeting Info, Background, Discussion, Decisions, Action Items, Follow-up

访问方式：使用

obsidian_get_periodic_note(period="daily")

路径：
```
DailyNote/YYYY/MM/YYYY-MM-DD.md
```
（由Obsidian管理）
用途：日常工作记录、进度、想法

Daily Notes

工作流

—

创建文件

Access: Use

obsidian_get_periodic_note(period="daily")

Path:
```
DailyNote/YYYY/MM/YYYY-MM-DD.md
```
(Obsidian-managed)
Purpose: Daily work log, progress, thoughts

创建新的项目笔记或会议记录时，请使用

obsidian-markdown

技能：

向用户收集必要信息（项目名称、会议日期、参会人员等）
加载对应的模板（
```
assets/project.md
```
或
```
assets/meeting.md
```
）
使用
```
obsidian-markdown
```
技能创建格式规范的文件
使用
```
obsidian_get_file_contents
```
验证文件是否创建在Obsidian的正确位置

禁止使用Write工具 — 必须仅使用Obsidian MCP工具。

Workflows

更新文件

Creating Files

—

Use

obsidian-markdown

skill when creating new project or meeting notes:

Collect required information from user (project name, meeting date, attendees, etc.)
Load appropriate template (
```
assets/project.md
```
or
```
assets/meeting.md
```
)
Use
```
obsidian-markdown
```
skill to create file with proper formatting
Verify file created in correct Obsidian location using
```
obsidian_get_file_contents
```

Do NOT use Write tool — Use Obsidian MCP tools exclusively.

更新现有Obsidian文件时：

读取当前文件：
```
obsidian_get_file_contents
```
确定更新位置（特定标题、字段、章节）
使用
```
obsidian_patch_content
```
进行针对性更新，或使用
```
obsidian_append_content
```
进行追加操作
对于格式调整/复杂编辑，使用
```
obsidian-markdown
```
技能
验证更改：再次使用
```
obsidian_get_file_contents
```
读取文件

Updating Files

查找文件

When updating existing Obsidian files:

Read current file:
```
obsidian_get_file_contents
```
Determine update location (specific heading, field, section)

Use

obsidian_patch_content

for targeted updates OR

obsidian_append_content

for appends

For formatting/complex edits, use
```
obsidian-markdown
```
skill
Verify changes: read file again with
```
obsidian_get_file_contents
```

当路径未知时，使用搜索工具定位文件：

obsidian_simple_search

— 快速文本搜索（例如：

"project:MyProject"

）

```
obsidian_complex_search
```
— 需要时使用高级模式匹配
```
obsidian_get_periodic_note
```
— 直接访问周期性笔记

Finding Files

Jira工单管理

Use search tools to locate files when path is unknown:

obsidian_simple_search

— Fast text search (e.g.,

"project:MyProject"

)

```
obsidian_complex_search
```
— Advanced pattern matching when needed
```
obsidian_get_periodic_note
```
— Access periodic notes directly

所有工单通过Jira MCP工具管理：

搜索和检索问题
创建新工单
更新工单状态和流转
添加评论和工时记录
关联到项目笔记（将Jira编号存储在项目前置元数据中：
```
jira: "PROJ-123"
```
）

Jira Ticket Management

Todo任务管理

All tickets managed through Jira MCP tools:

Search and retrieve issues
Create new tickets
Update ticket status and transitions
Add comments and time logs
Link to project notes (store Jira key in project frontmatter:
```
jira: "PROJ-123"
```
)

所有任务通过Things MCP工具管理：

检索现有任务
在收件箱中创建新任务
更新任务状态
按项目和领域分类整理

Todo Task Management

生成日报

All tasks managed through Things MCP tools:

Retrieve existing tasks
Create new tasks in inbox
Update task status
Organize by project and area

仅在用户明确请求时执行：例如“Generate daily report”“Create today's report”等。

遵循以下步骤（每步之间需等待用户确认）：

查看未关闭的Jira工单 — 使用JQL语句：
```
assignee = currentUser() AND statusCategory not in (Done) ORDER BY updated DESC
```
- 展示字段：摘要、状态、优先级、截止日期
查看今日Todo任务 — 使用Things的
```
get_today
```
功能
- 展示任务列表供用户查看
查看日常笔记 — 使用
```
obsidian_get_periodic_note(period="daily")
```
- 展示当前笔记内容

生成报告 — 编译结构化Markdown：

markdown

# 日报 - YYYY-MM-DD

## 未关闭Jira工单
| 编号 | 摘要 | 状态 | 优先级 | 截止日期 |
|-----|---------|--------|----------|-----|

## 今日Todo任务
| 任务 | 备注 | 项目 |
|------|-------|---------|

## 日常笔记
[笔记内容摘要]

追加到日常笔记 — 使用
```
obsidian_append_content
```
将报告添加到日常笔记中

Generating Daily Reports

重要实现说明

Only execute when user explicitly requests: "Generate daily report", "Create today's report", etc.

Follow this sequence (wait for user confirmation between steps):

Review open Jira tickets — Use JQL:
```
assignee = currentUser() AND statusCategory not in (Done) ORDER BY updated DESC
```
- Display with fields: summary, status, priority, due date
Review today's todos — Use
```
get_today
```
from Things
- Display task list for user review
Review daily note — Use
```
obsidian_get_periodic_note(period="daily")
```
- Display current note content

Generate report — Compile structured markdown:

markdown

# Daily Report - YYYY-MM-DD

## Open Jira Tickets
| Key | Summary | Status | Priority | Due |
|-----|---------|--------|----------|-----|

## Today's Todos
| Task | Notes | Project |
|------|-------|---------|

## Daily Notes
[summarized note content]

Append to daily note — Add report using
```
obsidian_append_content
```

始终使用Obsidian MCP工具进行任何文件操作（详见
```
references/tool-selection.md
```
中的工具选择决策树）
使用obsidian-markdown技能处理带有特殊格式或复杂前置元数据的文件创建
项目笔记是唯一可信来源 — 首先查询Obsidian，切勿假设项目存在于其他位置
验证操作结果 — 始终通过重新读取内容确认文件是否正确创建/更新
禁止使用本地文件路径 — 所有路径必须是相对于Obsidian库根目录的相对路径

Important Implementation Notes

参考指南

Always use Obsidian MCP tools for any file operation (see tool selection decision tree in
```
references/tool-selection.md
```
)
Use obsidian-markdown skill when creating files with special formatting or complex frontmatter
Project notes are source of truth — Query Obsidian first, never assume project exists elsewhere
Verify operations — Always confirm file created/updated correctly by reading back content
No local file paths — All paths must be relative to Obsidian vault root

如需详细实现指导，请查看：

references/tool-selection.md
— 按操作类型选择正确工具的决策树
references/obsidian-operations.md
— 所有Obsidian MCP工具的完整参考，包含示例和最佳实践

Reference Guides

—

For detailed implementation guidance, see:

references/tool-selection.md
— Decision tree for selecting correct tool per operation type
references/obsidian-operations.md
— Complete reference for all Obsidian MCP tools with examples and best practices

—