Auto-sync: 2026-04-22 20:02
This commit is contained in:
53
wiki/concepts/AI-Driven-Task-Extraction.md
Normal file
53
wiki/concepts/AI-Driven-Task-Extraction.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: "AI-Driven Task Extraction"
|
||||
type: concept
|
||||
tags: [ai, task-management, nlp, automation]
|
||||
sources: [todoist-task-manager, meeting-notes-action-items]
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
AI-Driven Task Extraction(AI 驱动的任务提取)是指利用大语言模型(LLM)从非结构化文本中自动识别并提取任务要素(谁/做什么/何时/何地/优先级),并将其转换为结构化任务数据的过程。核心技术栈:LLM(解析) + Task API(存储) + Cron Job(追踪)。
|
||||
|
||||
## Aliases
|
||||
|
||||
- AI Task Extraction
|
||||
- Task Extraction from Text
|
||||
- 自动任务提取
|
||||
- Natural Language to Task
|
||||
- 任务自动录入
|
||||
|
||||
## How It Works
|
||||
|
||||
1. **输入源**:邮件正文、会议记录、聊天消息、语音转录文本
|
||||
2. **LLM 解析**:Prompt 设计引导模型输出结构化 JSON(含任务描述、截止日期、优先级、标签)
|
||||
3. **任务创建**:调用 Todoist/Jira/Notion 等 API 创建任务
|
||||
4. **确认反馈**:回复用户"已创建:[任务名] @[项目] 🔴 高优先级,截止 [日期]"
|
||||
5. **持续追踪**:Cron Job 扫描逾期任务,主动推送提醒
|
||||
|
||||
## Prompt Example
|
||||
|
||||
```
|
||||
你是一个任务提取助手。从以下文本中提取所有待办事项,
|
||||
输出 JSON 格式:{"tasks": [{"description": "", "due": "", "priority": 1-4, "project": ""}]}
|
||||
原文:
|
||||
"{user_input}"
|
||||
```
|
||||
|
||||
## Use Cases
|
||||
|
||||
- **Email Inbox**:扫描 Gmail 收件箱,提取"需要回复"类任务
|
||||
- **Meeting Notes**:从 Otter.ai/Zoom 转录中提取行动项
|
||||
- **Slack/Discord**:监听频道消息,自动识别任务请求
|
||||
- **Voice Transcription**:SuperCall 电话转录 → 提取待确认/待执行事项
|
||||
- **Newsletter 阅读**:文章中提到的"需要跟进"点 → 创建研究任务
|
||||
|
||||
## Key Relationships
|
||||
|
||||
- [[LLM]] — 核心解析引擎
|
||||
- [[Todoist API]] — 任务存储后端
|
||||
- [[Todoist Task Manager]] — 自然语言→任务提取的完整实现
|
||||
- [[Meeting Notes Action Items]] — 会议场景的任务提取
|
||||
- [[Cron Job]] — 逾期任务主动追踪
|
||||
- [[Preference Learning]] — 从用户反馈中优化提取准确率
|
||||
68
wiki/concepts/Alerting.md
Normal file
68
wiki/concepts/Alerting.md
Normal file
@@ -0,0 +1,68 @@
|
||||
---
|
||||
title: "Alerting"
|
||||
type: concept
|
||||
tags: [Monitoring, Automation, Notification, Threshold]
|
||||
sources: [dynamic-dashboard]
|
||||
last_updated: 2026-04-22
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**Alerting** 是在指标超过预设阈值时,主动通知相关人员的机制。与被动查询仪表盘不同,告警实现"异常来找人"而非"人去查异常"的范式转变。
|
||||
|
||||
## 核心洞察
|
||||
|
||||
> "指标异常不是被看到,而是被通知"
|
||||
|
||||
## 告警生命周期
|
||||
|
||||
```
|
||||
Threshold Exceeded → Alert Triggered → Notification Sent → Acknowledged → Resolved
|
||||
│ │ │ │ │
|
||||
监控规则 事件生成 多渠道推送 用户确认 问题修复
|
||||
```
|
||||
|
||||
## 告警类型
|
||||
|
||||
1. **阈值告警**
|
||||
- 固定阈值: `if cpu > 90% → alert`
|
||||
- 变化率: `if stars_change > 50/hour → alert`
|
||||
|
||||
2. **趋势告警**
|
||||
- 异常检测: Twitter 负面情绪突增
|
||||
- 预测告警: 基于历史趋势预测故障
|
||||
|
||||
3. **复合告警**
|
||||
- 多条件组合: `if cpu > 80% AND disk < 20% → alert`
|
||||
|
||||
## 告警渠道
|
||||
|
||||
| 渠道 | 适用场景 | 优势 |
|
||||
|------|----------|------|
|
||||
| Discord | 团队协作/实时讨论 | 频道分类、@mention |
|
||||
| Email | 正式记录/异步通知 | 归档、可搜索 |
|
||||
| Slack | 企业团队集成 | 频道/线程组织 |
|
||||
| Telegram | 个人/移动优先 | 即时推送 |
|
||||
| SMS | 紧急故障 | 无网络依赖 |
|
||||
|
||||
## 告警疲劳管理
|
||||
|
||||
- **聚合**: 相似告警合并,减少噪音
|
||||
- **静默期**: 维护窗口自动静默
|
||||
- **升级**: 无人响应时升级通知级别
|
||||
- **去重**: 同一问题不重复通知
|
||||
|
||||
## 与 Prometheus Alertmanager 的对比
|
||||
|
||||
| 维度 | 自定义 Alerting | Prometheus Alertmanager |
|
||||
|------|----------------|------------------------|
|
||||
| 触发规则 | 自然语言描述 | PromQL 表达式 |
|
||||
| 数据源 | 任意 API | Prometheus metrics |
|
||||
| 灵活性 | 高(对话式调整) | 中(规则编写) |
|
||||
| 集成成本 | 低 | 中 |
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Dynamic-Dashboard]] — 告警是动态仪表盘的核心输出
|
||||
- [[Scheduled-Task-Flywheel]] — 定时检查是告警的前置条件
|
||||
- [[Prometheus告警规则]] — Prometheus 生态的规则定义方式
|
||||
89
wiki/concepts/Dynamic-Dashboard.md
Normal file
89
wiki/concepts/Dynamic-Dashboard.md
Normal file
@@ -0,0 +1,89 @@
|
||||
---
|
||||
title: "Dynamic Dashboard"
|
||||
type: concept
|
||||
tags: [OpenClaw, Dashboard, Monitoring, Automation]
|
||||
sources: [dynamic-dashboard]
|
||||
last_updated: 2026-04-22
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
**Dynamic Dashboard** 是一种基于 AI Agent 子代理并行执行的多数据源实时监控仪表盘。通过对话式指令驱动子代理同时抓取多个数据源,定时聚合结果并推送告警,实现"免开发、实时、主动"的监控体验。
|
||||
|
||||
## 核心洞察
|
||||
|
||||
> "用对话式描述替代数周的前端开发,立即获得实时洞察"
|
||||
|
||||
## 架构模式
|
||||
|
||||
```
|
||||
┌─────────────────────────────────────────┐
|
||||
│ Dynamic Dashboard │
|
||||
├─────────────────────────────────────────┤
|
||||
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
|
||||
│ │Sub-Agent│ │Sub-Agent│ │Sub-Agent│ │
|
||||
│ │ GitHub │ │ Twitter │ │Polymarket│ │
|
||||
│ └────┬────┘ └────┬────┘ └────┬────┘ │
|
||||
│ │ │ │ │
|
||||
│ └────────────┼────────────┘ │
|
||||
│ ▼ │
|
||||
│ ┌─────────────┐ │
|
||||
│ │ Aggregator │ │
|
||||
│ └──────┬──────┘ │
|
||||
│ ▼ │
|
||||
│ ┌─────────┐ ┌──────────┐ ┌───────┐ │
|
||||
│ │ Discord │ │ PostgreSQL│ │ Alert │ │
|
||||
│ │ Push │ │ History │ │ Check │ │
|
||||
│ └─────────┘ └──────────┘ └───────┘ │
|
||||
└─────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
## 核心能力
|
||||
|
||||
1. **多数据源并行监控**
|
||||
- GitHub: stars, forks, issues, commits
|
||||
- Social Media: Twitter mentions, Reddit discussions
|
||||
- Markets: Polymarket volume, prediction trends
|
||||
- System: CPU, memory, disk health
|
||||
|
||||
2. **子代理并行执行**
|
||||
- 每个数据源由独立子代理处理
|
||||
- 避免顺序轮询导致的阻塞和 API 限流
|
||||
- 聚合器等待所有子代理完成后统一汇总
|
||||
|
||||
3. **定时更新与告警**
|
||||
- Cron Job 驱动的定时抓取(默认 15 分钟)
|
||||
- 阈值告警主动推送(Discord/Email/Slack)
|
||||
- 历史数据存储供趋势分析
|
||||
|
||||
4. **对话式配置**
|
||||
- 无需编写前端代码
|
||||
- 用自然语言定义监控目标和告警规则
|
||||
- 迭代调整只需修改指令文本
|
||||
|
||||
## 典型应用场景
|
||||
|
||||
| 场景 | 监控目标 | 推送渠道 |
|
||||
|------|----------|----------|
|
||||
| 开发者监控 | GitHub stars/commits | Discord |
|
||||
| 社媒追踪 | Twitter mentions/sentiment | Discord |
|
||||
| 市场情报 | Polymarket volume/trends | Telegram |
|
||||
| 系统运维 | CPU/memory/disk | Discord/Email |
|
||||
|
||||
## 与静态仪表盘对比
|
||||
|
||||
| 维度 | 静态仪表盘 | Dynamic Dashboard |
|
||||
|------|------------|-------------------|
|
||||
| 数据时效 | 手动刷新/定时拉取 | 持续更新 |
|
||||
| 开发成本 | 数周前端开发 | 对话式配置 |
|
||||
| 告警机制 | 被动查询 | 主动推送 |
|
||||
| 多数据源 | 需分别集成 | 子代理原生并行 |
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Parallel-Agent-Execution]] — 子代理并行执行是动态仪表盘的核心机制
|
||||
- [[Scheduled-Task-Flywheel]] — Cron Job 驱动定时更新
|
||||
- [[Alerting]] — 阈值告警机制
|
||||
- [[self-healing-home-server]] — 系统健康监控场景
|
||||
- [[earnings-tracker]] — 市场数据监控场景
|
||||
- [[content-factory]] — 社交媒体监控场景
|
||||
53
wiki/concepts/Recurring-Tasks.md
Normal file
53
wiki/concepts/Recurring-Tasks.md
Normal file
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: "Recurring Tasks"
|
||||
type: concept
|
||||
tags: [task-management, automation, productivity]
|
||||
sources: [todoist-task-manager]
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Recurring Tasks(重复任务)是指按照固定周期自动生成新实例的任务机制,如"每週一早上9点提交周报"或"每6个月看牙医"。Todoist 的 repeat_string 字段支持自然语言周期描述(every Monday, every 6 months),极大简化了周期性任务的设置复杂度。
|
||||
|
||||
## Aliases
|
||||
|
||||
- Recurring Tasks
|
||||
- 重复任务
|
||||
- Recurring Reminders
|
||||
- 周期性任务
|
||||
- Repeating Tasks
|
||||
|
||||
## Natural Language Repeat Patterns (Todoist)
|
||||
|
||||
| 用户表述 | Todoist repeat_string |
|
||||
|----------|----------------------|
|
||||
| every Monday | "every monday" |
|
||||
| every weekday | "every weekday" |
|
||||
| every 2 weeks | "every 2 weeks" |
|
||||
| every 6 months | "every 6 months" |
|
||||
| monthly on the 1st | "monthly on the 1st" |
|
||||
| every day at 9am | "every day at 9:00" |
|
||||
| every Tuesday and Thursday | "every tuesday and thursday" |
|
||||
|
||||
## AI Integration Pattern
|
||||
|
||||
```
|
||||
用户:"每6个月提醒我看牙医"
|
||||
↓ Agent 解析为 repeat_string: "every 6 months"
|
||||
↓ Todoist API 创建任务,含 due 和 repeat_string 字段
|
||||
↓ Todoist 自动在每个周期创建新实例
|
||||
```
|
||||
|
||||
## Key Relationships
|
||||
|
||||
- [[Todoist API]] — repeat_string 是 Todoist API 的专属字段
|
||||
- [[Todoist Task Manager]] — 自然语言描述 → 重复任务创建
|
||||
- [[Morning Briefing]] — 重复任务中的周期性提醒(如每周一晨会)
|
||||
- [[AI-Driven Task Extraction]] — 从邮件/消息中识别周期性任务需求
|
||||
|
||||
## Design Considerations
|
||||
|
||||
- **命名规范**:重复任务标题应明确表达"周期性"含义("季度复盘"而非"复盘")
|
||||
- **截止日期 vs 周期**:有明确截止的用 due_date,周期性的用 repeat_string
|
||||
- **逾期容错**:Todoist 逾期后下一个实例会在修复日期创建(不跳跃),可通过 Agent 重新调度
|
||||
59
wiki/concepts/Todoist-API.md
Normal file
59
wiki/concepts/Todoist-API.md
Normal file
@@ -0,0 +1,59 @@
|
||||
---
|
||||
title: "Todoist API"
|
||||
type: concept
|
||||
tags: [api, task-management, integration, automation]
|
||||
sources: [todoist-task-manager, multi-channel-assistant, custom-morning-brief, meeting-notes-action-items]
|
||||
last_updated: 2026-04-21
|
||||
---
|
||||
|
||||
## Definition
|
||||
|
||||
Todoist 官方 API(REST API 和 Sync API),允许第三方应用通过 OAuth2 认证创建、读取、更新、删除 Todoist 中的任务、项目、标签和评论。是 AI Agent 集成 Todoist 的底层技术基础。
|
||||
|
||||
## Aliases
|
||||
|
||||
- Todoist REST API
|
||||
- Todoist Sync API
|
||||
- Todoist REST
|
||||
- Todoist API
|
||||
|
||||
## Core Capabilities
|
||||
|
||||
- **Tasks**:创建任务(含截止日期、优先级、标签、项目)、更新状态、添加评论
|
||||
- **Projects**:创建和管理项目层级结构
|
||||
- **Labels**:创建和管理标签(支持多标签)
|
||||
- **Sections**:项目内的分组(分区)
|
||||
- **Comments**:任务评论
|
||||
- **Sync**:实时双向同步,支持 WebSocket 推送
|
||||
|
||||
## API Integration Pattern (OpenClaw)
|
||||
|
||||
```
|
||||
用户自然语言指令 → OpenClaw Agent → LLM 解析结构化字段
|
||||
→ Todoist REST API POST /tasks → 任务创建
|
||||
→ 确认消息回复用户
|
||||
```
|
||||
|
||||
## Key Endpoints
|
||||
|
||||
| Method | Endpoint | 功能 |
|
||||
|--------|----------|------|
|
||||
| POST | /rest/v2/tasks | 创建任务 |
|
||||
| GET | /rest/v2/tasks | 列出任务 |
|
||||
| POST | /rest/v2/tasks/{id}/close | 完成任务 |
|
||||
| DELETE | /rest/v2/tasks/{id} | 删除任务 |
|
||||
| POST | /sync/v9/sync | 同步变更 |
|
||||
|
||||
## Use Cases
|
||||
|
||||
- [[Todoist Task Manager]]:自然语言 → API 调用
|
||||
- [[Custom Morning Brief]]:拉取今日任务和逾期任务
|
||||
- [[Meeting Notes Action Items]]:自动从会议记录创建任务
|
||||
- [[Phone-Based Personal Assistant]]:语音指令创建任务
|
||||
|
||||
## Key Relationships
|
||||
|
||||
- [[OpenClaw]] — Agent 框架,通过 API 集成 Todoist
|
||||
- [[Todoist]] — API 提供方
|
||||
- [[Natural Language Task Parsing]] — LLM 解析自然语言为 API 参数
|
||||
- [[Cron Job]] — 定时调用 API 检查逾期任务
|
||||
Reference in New Issue
Block a user