Meditate

Think proactively during idle time with sandboxed reflections, adaptive rhythms, and feedback-driven focus areas.

Security Scan

The skill's behavior mostly matches its stated purpose (local, reflection-only meditations), but there are inconsistencies and privacy/persistence considerations you should review before installing.

Purpose & Capability

The name/description align with the instructions: the skill is designed to read conversation history, generate reflections, and store them locally. It does not request network access, credentials, or external services, which is proportionate. However, the registry metadata lists no required config paths while SKILL.md consistently expects and uses a ~/meditate/ directory — an inconsistency in declared vs. actual runtime I/O.

Instruction Scope

Runtime instructions say the agent will read conversation history and read/write files under ~/meditate/. The docs repeatedly insist on an absolute sandbox (no network, no creds, no actions), but the memory-template includes a shell example (mkdir -p ~/meditate/archive) and profile.md is said to be 'updated automatically' — meaning the agent will be expected to write to disk. The skill relies on the agent correctly filtering out personal data; that enforcement is not verifiable from these files. The instructions do not detail how conversation history is accessed or filtered, which is a privacy-sensitive ambiguity.

Install Mechanism

This is an instruction-only skill with no install spec and no code files. That minimizes supply-chain risk — nothing is downloaded or executed by default.

Credentials

The skill requests no env vars or credentials (appropriate), but it will read conversation history (sensitive data) and persist derived materials under ~/meditate/. The registry metadata does not declare these config paths, so the runtime behavior (local file I/O in the home directory) is not reflected in the declared requirements — a transparency gap the user should note.

Persistence & Privilege

always:false and autonomous invocation are normal. The skill intends to persist memory (profile.md, insights.md, feedback.md, archive/) in the user's home directory and update those files automatically; that is expected for a meditation/memory skill but is persistent storage of conversation-derived material and should be treated as sensitive.

What to consider before installing

What to consider before installing: - This skill will read your conversation history and create/update files in ~/meditate/ (profile.md, topics.md, insights.md, feedback.md, archive/). The registry metadata did not declare those config paths — confirm you are comfortable with local storage in your home directory. - The skill states it will never send data externally, use credentials, or perform actions, and has strict sandbox rules in the docs, but those are behavioral constraints the agent must obey; the code is not present to enforce them. If you use this skill, periodically inspect ~/meditate/ contents and permissions. - If stored insights may contain sensitive details, consider restricting file permissions (chmod 700), placing the directory on encrypted storage, or running the skill in a segregated environment/account. - The template shows a shell command for initial setup (mkdir -p ...). Decide whether you will run that manually (safer) rather than allowing automated file creation. - Test the skill with non-sensitive topics first to verify it behaves as promised. If you need stronger guarantees (encryption, explicit consent prompts, platform-enforced sandboxing), request those features or avoid installing until they are provided. Confidence note: assessment is medium because the skill is instruction-only (no code to analyze) and the main concerns are transparency about local file I/O and privacy safeguards rather than evidence of malicious intent.

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

Topic	File
Memory setup	memory-template.md
Meditation types	topics.md
Sandbox rules	sandbox.md
Feedback system	feedback.md

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

User Activity	Meditation Frequency
Very active (daily chats)	1-2x per night, brief
Moderate (weekly)	2-3x per week, medium
Low (monthly)	1x per week, comprehensive
No feedback on insights	Reduce frequency
Positive feedback	Maintain or slightly increase

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:

Profile	Focus Areas
Entrepreneur	Projects, priorities, strategy gaps
Developer	Architecture, code quality, tech debt
Creative	Prompt patterns, style evolution, tools
Personal	Calendar, habits, goals mentioned
System	Configurations, workflows, automations

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

User Response	Action
"Useful" / positive	Log topic as high-value, continue
"Not relevant"	Demote topic priority
"Don't think about X"	Remove X from topics entirely
"Think more about Y"	Prioritize Y
Silence	Reduce frequency slightly

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