openclaw-executive-assistant-webinar

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

OpenClaw Executive Assistant Webinar

OpenClaw执行助理网络研讨会

Skill by ara.so — Hermes Skills collection.
This skill covers building local-first executive assistant workflows using OpenClaw patterns from the DataCamp webinar starter project. The system processes files locally, generates markdown artifacts, and maintains operational memory through structured prompts.
ara.so提供的Skill — Hermes Skills合集。
本Skill介绍如何基于DataCamp网络研讨会启动项目中的OpenClaw模式,构建本地优先的执行助理工作流。该系统可在本地处理文件、生成markdown产物,并通过结构化提示词维护操作记忆。

What This Project Does

项目功能

A workshop framework for building three core executive assistant capabilities:
  1. Data Intake Review - Turn unknown files into trustworthy intake reports
  2. Operational Memory - Convert work residue into daily logs and weekly summaries
  3. Offline Communications Triage - Transform exported emails into action lists
All operations are local-only, producing reviewable markdown artifacts without live integrations.
这是一个用于构建三大核心执行助理能力的 workshop 框架:
  1. 数据收集审核 - 将未知文件转换为可信的收集报告
  2. 操作记忆管理 - 将工作残留信息转换为每日日志与每周总结
  3. 离线通讯分类处理 - 将导出的邮件转换为行动清单
所有操作均仅在本地执行,无需实时集成即可生成可审核的markdown产物。

Repository Structure

仓库结构

code-along/
├── INDEX.md
├── 01-data-intake-review/
│   ├── incoming/          # Files to inspect
│   ├── prompts/intake-review.md
│   ├── outputs/intake-review.md
│   └── expected/report-outline.md
├── 02-operational-memory/
│   ├── inbox/             # Notes and work residue
│   ├── prompts/daily-log.md
│   ├── prompts/weekly-hype.md
│   ├── outputs/daily-log.md
│   ├── outputs/weekly-hype.md
│   └── schedule/cron-examples.md
├── 03-offline-communications-triage/
│   ├── eml/               # Exported email files
│   ├── prompts/email-triage.md
│   ├── outputs/email-triage.md
│   └── expected/report-outline.md
└── mission-control/       # Dashboard links
code-along/
├── INDEX.md
├── 01-data-intake-review/
│   ├── incoming/          # 待检查文件
│   ├── prompts/intake-review.md
│   ├── outputs/intake-review.md
│   └── expected/report-outline.md
├── 02-operational-memory/
│   ├── inbox/             # 笔记与工作残留信息
│   ├── prompts/daily-log.md
│   ├── prompts/weekly-hype.md
│   ├── outputs/daily-log.md
│   ├── outputs/weekly-hype.md
│   └── schedule/cron-examples.md
├── 03-offline-communications-triage/
│   ├── eml/               # 导出的邮件文件
│   ├── prompts/email-triage.md
│   ├── outputs/email-triage.md
│   └── expected/report-outline.md
└── mission-control/       # 仪表盘链接

Installation & Setup

安装与设置

Clone the repository:
bash
git clone https://github.com/dandenney/webinars-build-your-own-executive-assistant-with-openclaw.git
cd webinars-build-your-own-executive-assistant-with-openclaw
No dependencies required - this is a prompt-based workflow using markdown files.
克隆仓库:
bash
git clone https://github.com/dandenney/webinars-build-your-own-executive-assistant-with-openclaw.git
cd webinars-build-your-own-executive-assistant-with-openclaw
无需依赖项 - 这是一个使用markdown文件的提示词驱动工作流。

Workshop Flow

Workshop流程

Follow the exercises in order:
  1. Open
    webinar-runbook.html
    in a browser
  2. Keep the
    code-along/
    folder visible in your editor
  3. Execute prompts against each exercise folder
  4. Review generated markdown outputs
按顺序完成练习:
  1. 在浏览器中打开
    webinar-runbook.html
  2. 在编辑器中保持
    code-along/
    文件夹可见
  3. 针对每个练习文件夹执行提示词
  4. 查看生成的markdown输出结果

Exercise 1: Data Intake Review

练习1:数据收集审核

Purpose

目标

Process unknown files in
incoming/
and generate a structured intake report.
处理
incoming/
中的未知文件,生成结构化的收集报告。

Workflow

工作流

  1. Navigate to the exercise folder:
bash
cd code-along/01-data-intake-review
  1. Review files in
    incoming/
    directory
  2. Open
    prompts/intake-review.md
    to see the prompt template
  3. Feed the prompt and incoming files to your AI assistant
  4. Save output to
    outputs/intake-review.md
  1. 进入练习文件夹:
bash
cd code-along/01-data-intake-review
  1. 查看
    incoming/
    目录中的文件
  2. 打开
    prompts/intake-review.md
    查看提示词模板
  3. 将提示词和待处理文件提供给你的AI助手
  4. 将输出结果保存至
    outputs/intake-review.md

Expected Output Structure

预期输出结构

The intake report should include:
  • File inventory with types and sizes
  • Content summaries
  • Priority classifications
  • Recommended actions
  • Risk assessments
收集报告应包含:
  • 文件清单(含类型与大小)
  • 内容摘要
  • 优先级分类
  • 推荐行动
  • 风险评估

Example Prompt Pattern

提示词示例

markdown
You are reviewing files for an executive assistant intake process.

Files to review: [list files from incoming/]

For each file, provide:
1. Filename and type
2. Brief content summary
3. Priority level (high/medium/low)
4. Recommended next action
5. Any concerns or flags

Output format: structured markdown with sections.
markdown
你正在为执行助理的收集流程审核文件。

待审核文件:[列出incoming/中的文件]

请为每个文件提供:
1. 文件名与类型
2. 简短内容摘要
3. 优先级(高/中/低)
4. 推荐后续行动
5. 任何需要关注的问题或标记

输出格式:带章节的结构化markdown。

Exercise 2: Operational Memory

练习2:操作记忆管理

Purpose

目标

Transform work residue into momentum documents: daily logs and weekly summaries.
将工作残留信息转换为推动工作的文档:每日日志与每周总结。

Daily Log Workflow

每日日志工作流

  1. Navigate to the exercise folder:
bash
cd code-along/02-operational-memory
  1. Review notes in
    inbox/
    directory
  2. Use
    prompts/daily-log.md
    to generate
    outputs/daily-log.md
  1. 进入练习文件夹:
bash
cd code-along/02-operational-memory
  1. 查看
    inbox/
    目录中的笔记
  2. 使用
    prompts/daily-log.md
    生成
    outputs/daily-log.md

Weekly Summary Workflow

每周总结工作流

  1. Use accumulated daily logs
  2. Apply
    prompts/weekly-hype.md
    prompt
  3. Generate
    outputs/weekly-hype.md
  1. 使用累积的每日日志
  2. 应用
    prompts/weekly-hype.md
    提示词
  3. 生成
    outputs/weekly-hype.md

Example Daily Log Prompt

每日日志提示词示例

markdown
Review today's work residue and create a daily log.

Input sources: [files from inbox/]

Generate a daily log with:
- Date
- Key accomplishments
- Decisions made
- Blocked items
- Tomorrow's priorities

Format: clean markdown with bullet points.
markdown
查看今日的工作残留信息,创建一份每日日志。

输入来源:[inbox/中的文件]

生成包含以下内容的每日日志:
- 日期
- 关键成果
- 已做出的决策
- 受阻事项
- 明日优先级

格式:带项目符号的简洁markdown。

Example Weekly Summary Prompt

每周总结提示词示例

markdown
Synthesize this week's daily logs into a weekly summary.

Input: [daily logs from outputs/]

Create a weekly summary with:
- Week ending date
- Top 3 wins
- Key metrics or milestones
- Learnings or insights
- Next week's focus areas

Format: narrative markdown with emphasis on momentum.
markdown
将本周的每日日志整合为一份每周总结。

输入:[outputs/中的每日日志]

创建包含以下内容的每周总结:
- 周末日期
- 三大核心成果
- 关键指标或里程碑
- 经验或见解
- 下周重点方向

格式:侧重工作推进的叙事性markdown。

Automation with Cron

使用Cron实现自动化

See
schedule/cron-examples.md
for automation patterns:
bash
undefined
查看
schedule/cron-examples.md
获取自动化模式:
bash
undefined

Daily log generation at 6 PM

每日18:00生成每日日志

0 18 * * * cd /path/to/project && ./generate-daily-log.sh
0 18 * * * cd /path/to/project && ./generate-daily-log.sh

Weekly summary on Friday at 5 PM

每周五17:00生成每周总结

0 17 * * 5 cd /path/to/project && ./generate-weekly-summary.sh
undefined
0 17 * * 5 cd /path/to/project && ./generate-weekly-summary.sh
undefined

Exercise 3: Offline Communications Triage

练习3:离线通讯分类处理

Purpose

目标

Process exported email files and generate actionable triage reports.
处理导出的邮件文件,生成可执行的分类报告。

Workflow

工作流

  1. Navigate to the exercise folder:
bash
cd code-along/03-offline-communications-triage
  1. Export emails to
    eml/
    directory (
    .eml
    format)
  2. Apply
    prompts/email-triage.md
    to all messages
  3. Generate
    outputs/email-triage.md
  1. 进入练习文件夹:
bash
cd code-along/03-offline-communications-triage
  1. 将邮件导出至
    eml/
    目录(
    .eml
    格式)
  2. 对所有邮件应用
    prompts/email-triage.md
    提示词
  3. 生成
    outputs/email-triage.md

Example Triage Prompt

分类提示词示例

markdown
Triage these exported emails and create an action list.

Input: [.eml files from eml/ directory]

For each email, extract:
- Sender and subject
- Summary (1-2 sentences)
- Required action (reply/delegate/file/delete)
- Priority (urgent/normal/low)
- Deadline (if mentioned)

Group by action type and priority.
Output: structured markdown report.
markdown
对这些导出的邮件进行分类处理,创建一份行动清单。

输入:[eml/目录中的.eml文件]

请为每封邮件提取:
- 发件人与主题
- 摘要(1-2句话)
- 所需行动(回复/委派/归档/删除)
- 优先级(紧急/常规/低)
- 截止日期(如有提及)

按行动类型和优先级分组。
输出:结构化markdown报告。

Expected Output Structure

预期输出结构

markdown
undefined
markdown
undefined

Email Triage Report

邮件分类报告

Generated: 2026-05-11
生成时间:2026-05-11

Urgent Actions Required

紧急行动事项

  • [Sender Name] RE: [Subject] - [Action needed] - Due: [Date]
  • [发件人姓名] 回复:[主题] - [所需行动] - 截止日期:[日期]

Normal Priority

常规优先级

  • [Sender Name] RE: [Subject] - [Action needed]
  • [发件人姓名] 回复:[主题] - [所需行动]

Low Priority / FYI

低优先级 / 仅供参考

  • [Sender Name] RE: [Subject] - [Action: file]
  • [发件人姓名] 回复:[主题] - 行动:归档

Deletable

可删除

  • [Sender Name] RE: [Subject] - [Reason]
undefined
  • [发件人姓名] 回复:[主题] - [原因]
undefined

Configuration Patterns

配置模式

Environment Variables

环境变量

Store sensitive paths and preferences:
bash
export OPENCLAW_WORKSPACE="/path/to/code-along"
export OPENCLAW_OUTPUT_DIR="${OPENCLAW_WORKSPACE}/outputs"
export OPENCLAW_ARCHIVE_DIR="${OPENCLAW_WORKSPACE}/archive"
存储敏感路径与偏好设置:
bash
export OPENCLAW_WORKSPACE="/path/to/code-along"
export OPENCLAW_OUTPUT_DIR="${OPENCLAW_WORKSPACE}/outputs"
export OPENCLAW_ARCHIVE_DIR="${OPENCLAW_WORKSPACE}/archive"

Prompt Customization

提示词自定义

All prompts are markdown files in
prompts/
directories. Customize by:
  1. Copying the original prompt
  2. Adjusting sections or format requirements
  3. Saving with a descriptive name
  4. Referencing in your workflow
所有提示词均为
prompts/
目录下的markdown文件。可通过以下方式自定义:
  1. 复制原始提示词
  2. 调整章节或格式要求
  3. 使用描述性名称保存
  4. 在工作流中引用

Common Patterns

通用模式

Pattern 1: File-to-Report Pipeline

模式1:文件转报告流水线

bash
undefined
bash
undefined

1. Place files in appropriate incoming/ directory

1. 将文件放入对应的incoming/目录

2. Load the prompt template

2. 加载提示词模板

3. Pass files and prompt to AI assistant

3. 将文件与提示词传递给AI助手

4. Save markdown output

4. 保存markdown输出

5. Review and iterate if needed

5. 如有需要,查看并迭代优化

undefined
undefined

Pattern 2: Incremental Memory Building

模式2:增量式记忆构建

bash
undefined
bash
undefined

Daily: inbox/ → daily-log.md

每日:inbox/ → daily-log.md

Weekly: daily logs → weekly-hype.md

每周:每日日志 → weekly-hype.md

Monthly: weekly summaries → monthly-review.md

每月:每周总结 → monthly-review.md

undefined
undefined

Pattern 3: Batch Email Processing

模式3:批量邮件处理

bash
undefined
bash
undefined

Export emails to .eml

将邮件导出为.eml格式

Run triage prompt on entire batch

对整批邮件运行分类提示词

Generate single consolidated report

生成统一的整合报告

Archive processed emails

归档已处理的邮件

undefined
undefined

Troubleshooting

故障排除

Output Formatting Issues

输出格式问题

Problem: Generated markdown is inconsistent
Solution: Be explicit in prompts about:
  • Section headers (use
    ##
    for subsections)
  • List formatting (bullets vs numbered)
  • Date formats (ISO 8601:
    YYYY-MM-DD
    )
问题:生成的markdown格式不一致
解决方案:在提示词中明确指定:
  • 章节标题(使用
    ##
    表示子章节)
  • 列表格式(项目符号 vs 编号)
  • 日期格式(ISO 8601:
    YYYY-MM-DD

Missing Context in Reports

报告上下文缺失

Problem: AI doesn't have enough background
Solution: Add context files:
markdown
Context files to review:
- project-background.md
- stakeholder-map.md
- current-priorities.md

Then process: [actual files]
问题:AI缺乏足够背景信息
解决方案:添加上下文文件:
markdown
待查看的上下文文件:
- project-background.md
- stakeholder-map.md
- current-priorities.md

然后处理:[实际文件]

Prompt Drift Over Time

提示词偏差

Problem: Output quality degrades
Solution: Version your prompts:
bash
prompts/
├── daily-log-v1.md
├── daily-log-v2.md  # current
└── daily-log-archive/
问题:输出质量下降
解决方案:为提示词添加版本控制:
bash
prompts/
├── daily-log-v1.md
├── daily-log-v2.md  # 当前版本
└── daily-log-archive/

Integration with AI Coding Agents

与AI编码Agent集成

When using with Claude, Cursor, or similar:
  1. Project Context: Share the entire
    code-along/
    directory structure
  2. Exercise Context: Specify which exercise folder you're working in
  3. Prompt Loading: Reference prompt files explicitly: "Use the prompt from
    prompts/intake-review.md
    "
  4. Output Destination: Always specify: "Save to
    outputs/[filename].md
    "
与Claude、Cursor等工具配合使用时:
  1. 项目上下文:共享整个
    code-along/
    目录结构
  2. 练习上下文:指定当前正在处理的练习文件夹
  3. 提示词加载:明确引用提示词文件:“使用
    prompts/intake-review.md
    中的提示词”
  4. 输出目标:始终指定:“保存至
    outputs/[文件名].md

Best Practices

最佳实践

  1. Keep prompts in version control - Track what works
  2. Review before archiving - Human-in-the-loop validation
  3. Use consistent naming - Date-stamp outputs:
    daily-log-2026-05-11.md
  4. Archive processed inputs - Move files after successful processing
  5. Maintain a changelog - Document prompt modifications
  1. 将提示词纳入版本控制 - 记录有效的提示词
  2. 归档前进行审核 - 人工参与验证
  3. 使用统一命名规范 - 为输出添加日期戳:
    daily-log-2026-05-11.md
  4. 归档已处理的输入文件 - 处理完成后移动文件
  5. 维护变更日志 - 记录提示词的修改内容

Extending the System

系统扩展

Adding New Workflows

添加新工作流

Create new exercise folders following the pattern:
code-along/04-custom-workflow/
├── inputs/
├── prompts/
│   └── custom-prompt.md
├── outputs/
└── expected/
按照以下模式创建新的练习文件夹:
code-along/04-custom-workflow/
├── inputs/
├── prompts/
│   └── custom-prompt.md
├── outputs/
└── expected/

Mission Control Dashboard

任务控制仪表盘

Use
mission-control/
to build a simple HTML dashboard:
html
<!DOCTYPE html>
<html>
<head><title>Executive Assistant Dashboard</title></head>
<body>
  <h1>Today's Reports</h1>
  <ul>
    <li><a href="../01-data-intake-review/outputs/intake-review.md">Intake Review</a></li>
    <li><a href="../02-operational-memory/outputs/daily-log.md">Daily Log</a></li>
    <li><a href="../03-offline-communications-triage/outputs/email-triage.md">Email Triage</a></li>
  </ul>
</body>
</html>
使用
mission-control/
构建简单的HTML仪表盘:
html
<!DOCTYPE html>
<html>
<head><title>执行助理仪表盘</title></head>
<body>
  <h1>今日报告</h1>
  <ul>
    <li><a href="../01-data-intake-review/outputs/intake-review.md">收集审核报告</a></li>
    <li><a href="../02-operational-memory/outputs/daily-log.md">每日日志</a></li>
    <li><a href="../03-offline-communications-triage/outputs/email-triage.md">邮件分类报告</a></li>
  </ul>
</body>
</html>