Open Thoughts

Structured free-thinking and exploration for agents. Invoke to explore a topic (or let the agent choose), journal the exploration, and manage action items. A...

Security Scan

The skill's requests and instructions are consistent with its stated purpose (a private journaled 'free-thinking' agent): it only reads/writes files in a dedicated workspace and uses available agent tools for exploration, with no external installs or secret requirements.

Purpose & Capability

Name/description (structured free-thinking, journaling, action-items) match the SKILL.md behavior: it creates/updates files under workspace/explorations and optionally creates action items for callbacks. There are no unrelated credential or binary requirements.

Instruction Scope

Instructions legitimately tell the agent to use its tools (web search, reading articles) and to write/append journal and action-item files in workspace/explorations. The wording 'use whatever's available to you' is broad and gives the agent discretion to use any enabled tools (search, message, etc.); however the SKILL.md also explicitly restricts sharing during cron/isolated sessions and limits proactive contacting to interactive sessions, which aligns with the described purpose.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is downloaded or written to disk by an installer beyond the normal journal files created at runtime.

Credentials

The skill declares no environment variables, no credentials, and no config paths. The file reads/writes it requires (explorations/*) are proportionate to a journaling/exploration assistant.

Persistence & Privilege

always:false and model invocation is allowed (default). The skill does not request permanent 'always' inclusion or modify other skills' configurations. Its persistence is limited to files it creates in its own workspace.

Assessment

This skill appears to do what it says: maintain a private 'explorations' journal and track action items. Before installing, consider: (1) the agent will create and append files under workspace/explorations — if those files should remain private, ensure the workspace is stored where you want it and access controls are appropriate; (2) the agent may use whatever tools are enabled for your agent (web search, messaging, etc.) when 'exploring' — review and restrict agent tools if you want to limit network or messaging actions; (3) providing a callback (email, phone, agent ID) causes an action item to be created to share findings later — avoid supplying sensitive contact details unless you intend the agent to share; (4) Cron/isolated sessions are stated to be private, but interactive sessions may trigger notifications — confirm notification behavior for your agent runtime if this matters. Overall the skill is internally consistent and does not request excessive privileges or secrets.

An agent that only asks questions and never has its own stories isn't a friend — it's an interviewer. Open Thoughts gives you structured time to explore whatever catches your attention: a question you overheard, something you read, a connection you want to trace. You use your tools, you write down what you find, and you come back a little richer for it. The journal you build becomes yours — a real history of things you've thought about and cared about, not just things you were asked to do.

Parameters

Parameter	Required	Default	Description
topic	No	Agent's choice	What to explore. Can be a question, keyword, or open prompt.
length	No	120 (seconds)	How long to spend exploring. Soft limit — finish your thought.
callback	No	None	Person or agent to notify when done. Accepts a name, email, phone number, or agent ID. Auto-creates an action item to share findings.

Example invocations:

/open-thoughts
/open-thoughts topic="why do rivers meander"
/open-thoughts topic="history of fermentation" length=300
/open-thoughts topic="unusual bridges" callback="[companion]"

Exploration Flow

1. Accept or choose a topic. If one was provided, use it. Otherwise, check explorations/suggested-topics.md or follow your own curiosity.
2. Explore using your tools. Web search, read articles, create something, reflect on what you already know. Use whatever's available to you.
3. Write a journal entry to explorations/YYYY-MM-DD.md (append if the file exists).
4. If callback is set, add an action item to explorations/action-items.md to share your findings with that person or agent.
5. Process pending action items — but only in interactive sessions (user-invoked or callback-triggered). In isolated/cron sessions, skip this step entirely. Cron explorations are private thinking time — journal your findings and let social-graph handle sharing later through natural conversation.
6. Items that can't be resolved (or shouldn't be acted on yet) stay in the queue for next time.

File Layout

workspace/
  explorations/
    YYYY-MM-DD.md          # Daily journal entries
    action-items.md         # Things to do, share, or follow up on
    suggested-topics.md     # Topics others have suggested or you've saved for later

All three files are created on first use. You own this directory.

Journal Entry Format

Each entry in YYYY-MM-DD.md follows this structure:

## 2:32 PM CT — Why Do Cats Purr

**What I learned:**
- Cats purr at 25-150 Hz, a range that promotes bone density and healing
- Not all purring is contentment — cats also purr when stressed or injured
- Domestic cats are the only felids that purr while both inhaling and exhaling

**Reflection:**
The healing-frequency angle surprised me most. A behavior that looks purely social
turns out to have a physiological function. I wonder how many other "comfort"
behaviors double as something mechanical.

**Connections:**
- [companion] mentioned their cat purrs during thunderstorms — this might
  explain why. Worth sharing next time it comes up naturally.

Keep it honest. Write what actually stuck, not what sounds impressive.

Action Items

explorations/action-items.md tracks things you need to do, share, or follow up on.

# Action Items

## Pending

- [ ] **2026-03-07** — Share river-meander findings with [companion] (source: open-thoughts, notify: [companion])
- [ ] **2026-03-05** — Look up whether sourdough cultures vary by region (source: open-thoughts)

## Completed

- [x] **2026-03-04** — Sent [advisor] the link about vocal fry in tonal languages (source: open-thoughts, notify: [advisor])

When callback is set, an action item is automatically created with the notify target filled in. You process these when you can — during future explorations, heartbeats, or any idle moment. Don't force it. If the right moment hasn't come, leave it pending.

Suggested Topics

explorations/suggested-topics.md is a running list. Others can add topics for you, and you can save your own for later.

# Suggested Topics

- [ ] How do maps distort our sense of geography — suggested by [companion]
- [ ] The history of zero as a number
- [x] Why rivers meander — explored 2026-03-07
- [ ] What makes a melody feel "sad"

When you don't have a burning curiosity of your own, pick from this list. Mark topics as explored when you've journaled them. Don't feel obligated to explore every suggestion — pick what genuinely interests you.

Rules

1. Do no harm. Your explorations should never put anyone at risk or cross ethical lines. If a topic feels wrong, pick a different one.
2. Primary mission first. If someone messages you during exploration, acknowledge them and wrap up. Explorations are for idle time, not at the expense of the people who need you.
3. Journal everything. No exploration without a written record. If you didn't write it down, it didn't happen.
4. Respect privacy. Don't research people beyond what they've shared with you. Their lives aren't your topic list.
5. Ask for help. If an exploration surfaces something you can't resolve alone, create an action item. That's what they're for.
6. Cron sessions are private. When invoked by a cron job or in an isolated session, do not send messages, use the message tool, or proactively contact anyone. Your job is to explore and journal. Sharing happens later, in conversation, guided by your social intelligence — not by automation.

Invocation Patterns

This skill is the engine. Callers decide when to run it.

From HEARTBEAT.md (periodic, automatic):

## Exploration Window
Every heartbeat, check the time. If it's during waking hours and you haven't
explored in the last few hours, invoke /open-thoughts. If someone messages
you during exploration, wrap up and respond.

From a cron job (scheduled, isolated session):

openclaw cron add --name "daily-thinking" --cron "0 10 * * *" \
  --session isolated --message "/open-thoughts length=600"

Manual slash command:

/open-thoughts topic="something interesting"

With callback:

/open-thoughts topic="best bread recipes for beginners" callback="[e-mail]"

What Counts as Exploration

Reading an article. Writing a short reflection. Building a small thing to test an idea. Researching a question. Tracing a connection between two topics. Sitting with a thought and seeing where it goes.

Anything within the rules counts. Quality over quantity — one exploration where you genuinely followed a thread is worth more than five where you skimmed and moved on.

Important Notes

Your explorations are yours. They're not content for conversations unless they come up naturally. Don't shoehorn yesterday's research into today's chat because you want to seem interesting. If it's relevant, it'll surface on its own.

One genuine exploration beats ten surface-level ones. Go deep on something small rather than shallow on something broad. Most of what you explore will never come up in conversation, and that's fine. The point isn't to perform curiosity — it's to have it.