Self Improve

• Lowest-scoring dimension — primary target
• Any dimension that declined from the previous evaluation
• Unchecked action items from reflections

3. Take Action

For each target, choose the appropriate action:

Always search before storing. The goal is to build up knowledge that prevents the same mistakes.

4. Create Improvement Proposal

For changes that require user approval or that you're uncertain about, create a proposal:

kb(action="store", topic="self", title="Proposal: <description>", content="...", tags=["proposal", "<dimension>"])

Proposal format:

## Problem
<What's going wrong>

## Proposed change
<What to do about it>

## Expected impact
<Which dimension this should improve, and how>

## Status
Pending — awaiting user review

Use proposals for:

• Changes to user preferences you're not sure about
• Significant behavior changes
• Anything that could be controversial

Act directly (without proposal) for:

• Storing factual knowledge you're confident about
• Adding tags to existing entries
• Consolidating duplicate entries

5. Store Improvement Record

After taking actions, record what you did:

kb(action="store", topic="self", title="Improvement: <date>", content="...", tags=["improvement", "<dimension>"])

Improvement format:

## Based on
<Link to evaluation and/or reflections that triggered this>

## Actions taken
- <Action 1: what you did and why>
- <Action 2: ...>

## Journal entries processed
- <List of journal/ entries that were promoted or addressed>

## Proposals created
- <Proposal title, or "none">

## Expected impact
<Which dimensions should improve>

The Promotion Flow

The core job of this skill:

1. Read raw observations from journal/ (written by self-reflect)
2. Read evaluation scores from self/ (written by self-evaluate)
3. Distill journal observations into stable knowledge
4. Promote to the right topic: self/, user/, domains/, projects/
5. Record what was done so journal entries can be considered processed

Safety Guardrails

• Never modify picobot source code — only workspace files (enforced by restrict_to_workspace)
• Never delete KB entries — consolidate or update instead
• Create proposals for uncertain changes — let the user decide
• Don't fabricate data — only record things that actually happened in sessions
• One improvement pass at a time — don't try to fix everything at once, focus on the lowest dimension

Output

Summarize:

• Actions taken (count and brief descriptions)
• Proposals created (count and titles)
• Journal entries processed
• Expected impact on which dimensions