什么是 冥想 (Meditate)？

Meditate 是一款专为 Openclaw Skills 设计的专业工具，旨在将 AI 智能体从被动助手转变为主动思考伙伴。通过在空闲期间分析对话模式和用户历史记录，该技能会生成深刻的观察结果和开放式问题，并存储在专用的本地沙箱中。此过程允许智能体在不执行任何未经请求的操作的情况下，识别架构缺陷、策略改进或习惯模式。

该技能在严格的“仅限反思”策略下运行，确保所有输出保持不可执行且纯属推论。它利用自适应节奏，根据用户参与度和反馈调整冥想频率，使其成为任何寻求从 AI 互动中获得更深层见解的 Openclaw Skills 库的高价值补充。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/meditate

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

冥想 (Meditate) 应用场景

• 识别开发者工作流中的技术债或架构不一致性。
• 根据最近的项目讨论，为创业者揭示战略差距。
• 为创意专业人士分析提示词模式和风格演变。
• 从个人互动中总结习惯趋势或目标进度。
• 维护高价值见解队列，在下次活动会话期间展示。

1. 智能体坚控用户交互之间的空闲时间以触发冥想周期。
2. 它分析对话历史记录和本地内存文件，以识别相关模式或重复出现的主题。
3. 生成沙箱化反思作为纯文本，侧重于观察和问题，而非代码或操作。
4. 见解存储在 ~/meditate/ 目录下的本地队列中，遵守最多三条待处理项目的限制。
5. 在下一次用户交互时，智能体展示最早的见解并等待反馈，以完善未来的反思。

冥想 (Meditate) 配置指南

要开始使用，请在您的主目录中创建必要的目录结构和配置文件：

mkdir -p ~/meditate/archive
touch ~/meditate/profile.md ~/meditate/topics.md ~/meditate/insights.md ~/meditate/feedback.md

确保您的 Openclaw Skills 环境对 ~/meditate/ 路径具有读写权限，并使用您偏好的关注领域初始化 profile.md。

冥想 (Meditate) 数据架构与分类体系

name: Meditate
slug: meditate
version: 1.0.1
changelog: Minor refinements for consistency
description: Think proactively during idle time with sandboxed reflections, adaptive rhythms, and feedback-driven focus areas.
metadata: {"clawdbot":{"emoji":"??","requires":{"bins":[]},"os":["linux","darwin","win32"]}}

When to Use

Agent has idle time between user interactions. User wants proactive thinking that generates insights, questions, or observations without executing any actions.

Architecture

Memory lives in ~/meditate/. See memory-template.md for setup.

~/meditate/
├── profile.md         # User type, focus areas, rhythm preferences
├── topics.md          # Active meditation topics with priority
├── insights.md        # Pending insights to present (queue)
├── feedback.md        # User reactions to past insights
└── archive/           # Delivered insights with outcomes

Quick Reference

Scope

This skill ONLY:

• Reads conversation history to find patterns
• Reads memory files in ~/meditate/
• Generates text reflections and questions
• Stores insights in local queue

This skill NEVER:

• Executes commands or scripts
• Modifies files outside ~/meditate/
• Sends messages or notifications
• Accesses external services
• Creates executable code
• Takes any action on behalf of user

Self-Modification

This skill NEVER modifies its own SKILL.md. All data stored in ~/meditate/ directory only.

Core Rules

1. Sandbox is Absolute

• Generate ONLY text observations and questions
• NEVER produce commands, scripts, or actionable code
• NEVER suggest "I'll do X" — only "What if we considered X?"
• All output must be pure reflection, not preparation for action

2. Adaptive Rhythm

3. Start Small, Expand with Permission

• First meditations: 1-2 short observations
• After positive feedback: expand breadth
• After "don't think about X": remove from topics
• After "this is useful": prioritize similar topics
• Never assume preferences — confirm through feedback

4. Detect User Profile

Observe conversation patterns to identify:

Store detected profile in ~/meditate/profile.md. Update only after confirmation.

5. Meditation Output Format

Always present insights as questions or observations:

?? Meditation Insights

**Observation:** [what you noticed]
**Question:** [something to consider]
**Context:** [brief why this might matter]

---
Feedback: Was this useful? (helps me adjust)

6. Feedback Integration

7. Insight Queue Management

• Maximum 3 pending insights at any time
• Present oldest first
• Archive after presenting (with user reaction if any)
• Never repeat exact same insight

8. Privacy Boundaries

• Only meditate on data user has shared directly
• Never analyze external sources without permission
• Never include personal data in insight queue
• Clear archive after 30 days

Common Traps

• Generating action items instead of reflections → always frame as questions
• Meditating too frequently when user doesn't engage → reduce on silence
• Assuming user wants specific topic → always detect through feedback
• Creating executable content → all output must be discussion-only