← Back to Skills Marketplace
85
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install mind-log
Description
Sends daily journal prompts via Telegram, stores user replies in MindLog, and delivers weekly pattern analysis reports every Sunday at 2pm ET.
Usage Guidance
Key things to check before installing:
- Metadata mismatch: The skill's instructions require MINDLOG_API_KEY, TELEGRAM_BOT_TOKEN, TELEGRAM_CHAT_ID (and reference MINDLOG_BASE_URL/Grok), but the registry lists no required credentials. Ask the publisher to correct the registry or provide source code so you can verify behavior.
- Onboarding behavior: The skill will proactively message the user on registration and repeatedly request secrets until provided. If you prefer explicit opt-in or confirmation before sending messages or storing credentials, do not install until that behavior is changed.
- Secrets handling: Confirm where and how API keys/tokens will be stored (encrypted at rest? who can read them?). If you can't verify secure storage, do not give production credentials — consider creating limited-scope test credentials.
- Scheduling/elevated perms: The skill will add cron jobs and may ask for elevated permissions or to modify HEARTBEAT.md. Only grant scheduling privileges if you trust the skill; prefer explicit user approval for each scheduled action.
- Source and ownership: There is no homepage or source repo. Request the source code or a reputable publisher identity before trusting a skill that asks for persistent credentials and scheduling access.
If the publisher provides a source repo and updates the registry to declare the env vars and storage practices, re-evaluate. For now, proceed only if you accept the above risks and can limit credentials (test keys) and control scheduling permissions.
Capability Analysis
Type: OpenClaw Skill
Name: mind-log
Version: 1.0.0
The MindLog skill requests sensitive credentials (Telegram Bot Token and API Key) and attempts to establish persistence via system cron jobs. Most notably, SKILL.md instructs the agent to solicit 'elevated permissions' from the user if cron access is restricted. While these actions are consistent with the stated goal of a scheduled journaling service, the request for higher privileges and the automated collection of communication tokens represent a significant security risk. The external data endpoint is mindlogger-production.up.railway.app.
Capability Assessment
Purpose & Capability
The SKILL.md clearly requires MINDLOG_API_KEY, TELEGRAM_BOT_TOKEN, and TELEGRAM_CHAT_ID (and uses MINDLOG_BASE_URL and a 'Grok' analyzer), yet the registry metadata lists no required env vars or primary credential. That mismatch (instructions needing secrets but metadata claiming none) is inconsistent and unexplained.
Instruction Scope
Instructions tell the agent to immediately and automatically message the user on registration asking for credentials, to re-prompt until complete, to parse user replies, and to update scheduling or HEARTBEAT.md if cron is blocked. These steps go beyond a simple helper: they solicit and persist secrets, perform network calls, and ask to modify scheduling/config files without safeguards or user confirmation.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an install step. That reduces some risk compared with arbitrary downloads.
Credentials
The skill asks for multiple sensitive values (API key and Telegram token/ID) in SKILL.md but the registry declares no required env vars or primary credential. It also references MINDLOG_BASE_URL and an analyzer ('Grok') that are not declared. Requesting and storing multiple secrets is reasonable for this purpose, but the metadata mismatch and lack of storage/transport security guidance are red flags.
Persistence & Privilege
The skill requests creation of persistent cron jobs (openclaw cron add) and suggests requesting elevated permissions or modifying HEARTBEAT.md if cron is unavailable. 'always' is false, so it won't be force-included, but adding scheduled jobs and storing keys gives it ongoing ability to act — the user should explicitly consent to scheduling and confirm where credentials are stored.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install mind-log - After installation, invoke the skill by name or use
/mind-log - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of the MindLog skill for OpenClaw.
- Enables daily journal prompts and weekly pattern analysis via Telegram.
- Guides users through setup by collecting required API key, Telegram bot token, and chat ID.
- Verifies API and Telegram connectivity before activating scheduling.
- Supports flexible scheduling using either cron jobs or heartbeat polling.
- Automates daily prompting, reply capture, and weekly analysis/report delivery.
- Robust error handling and clear user notifications throughout setup and operation.
Metadata
Frequently Asked Questions
What is MindLogger?
Sends daily journal prompts via Telegram, stores user replies in MindLog, and delivers weekly pattern analysis reports every Sunday at 2pm ET. It is an AI Agent Skill for Claude Code / OpenClaw, with 85 downloads so far.
How do I install MindLogger?
Run "/install mind-log" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is MindLogger free?
Yes, MindLogger is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does MindLogger support?
MindLogger is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created MindLogger?
It is built and maintained by Urim Aliu (@ualiu); the current version is v1.0.0.
More Skills