53 lines
2.6 KiB
Markdown
53 lines
2.6 KiB
Markdown
---
|
||
id: habit-tracker-accountability-coach
|
||
title: Habit Tracker & Accountability Coach
|
||
type: source
|
||
tags: [agent-use-case, habit-tracking, accountability, telegram, automation]
|
||
date: 2026-04-17
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Agent/usecases/habit-tracker-accountability-coach.md]]
|
||
|
||
## Summary
|
||
- 核心主题：AI Agent 作为主动式习惯追踪与问责伙伴
|
||
- 问题域：传统习惯追踪应用被动式提醒，用户容易忽略通知，行为改变需要主动问责
|
||
- 方法/机制：通过 Telegram/SMS 定时主动检查、连续打卡追踪、自适应提醒语气、周报分析
|
||
- 结论/价值：主动问责比被动提醒更有效，AI Agent 可实现零社交压力的个人问责系统
|
||
|
||
## Key Claims
|
||
- 习惯追踪应用失败的根本原因是被动式交互，用户主动打开率低
|
||
- 主动式问责（AI 直接询问完成情况）比推送通知更有效
|
||
- 自适应语气（连续成功时鼓励，失败时温和提醒）提升长期坚持率
|
||
- 习惯数量控制在 3-5 个可避免检查疲劳
|
||
|
||
## Key Quotes
|
||
> "What actually works for behavior change is active accountability — someone (or something) that asks you directly, celebrates your wins, and nudges you when you slip."
|
||
|
||
> "A message that says 'Day 15, don't break it now' actually motivates."
|
||
|
||
## Key Concepts
|
||
- [[Cron-Jobs]]：定时任务调度，AI Agent 通过 cron 实现每日定时检查
|
||
- [[Preference-Learning]]：AI 通过交互学习用户偏好，持续优化提醒策略
|
||
- [[工作流自动化]]：预定义自动化流程，AI Agent 定时执行检查并记录结果
|
||
- [[上下文记忆]]：AI Agent 保留对话历史，追踪连续打卡天数和用户响应模式
|
||
|
||
## Key Entities
|
||
- [[Telegram]]：消息推送渠道，通过 Telegram Bot API 实现每日检查
|
||
- [[Twilio]]：SMS 替代渠道，提供短信通知能力
|
||
- [[Google Sheets]]：可选可视化仪表盘，数据导出和可视化展示
|
||
- [[OpenClaw]]：AI Agent 运行环境，支持定时任务和文件存储
|
||
|
||
## Connections
|
||
- [[Health-Symptom-Tracker]] ← combines_with ← [[Habit-Tracker-Accountability-Coach]]
|
||
- [[Custom-Morning-Brief]] ← similar_approach ← [[Habit-Tracker-Accountability-Coach]]
|
||
- [[Cron-Jobs]] ← enables ← [[Habit-Tracker-Accountability-Coach]]
|
||
|
||
## Contradictions
|
||
- 与传统习惯追踪应用（如 Habitica、Streaks）的核心区别在于主动 vs 被动交互模式
|
||
|
||
## Implementation Notes
|
||
1. Telegram Bot API 配置相对简单，无需手机号验证
|
||
2. Twilio 需要美国号码用于 SMS 发送，成本高于 Telegram
|
||
3. 数据存储推荐使用本地 JSON 文件（~/habits/log.json），便于历史查询
|
||
4. Google Sheets 集成可选，适合需要可视化数据的用户 |