memory-setup (Android Module Refactor)

This skill is refactored to set up memory according to current OpenClaw standards, avoiding drift from the old config structure.

Indexed Reference Map

• @[SKILL.md#L1-L129] Standard Frontmatter.
• @[SKILL.md#L12-L129] Scope + safety principles.
• @[SKILL.md#L28-L129] SOP memory setup according to current schema.
• @[SKILL.md#L71-L129] Valid Config snippets for OpenClaw.
• @[references/openclaw-memory-schema-map.md#L1-L39] Mapping field is correct according to the schema.
• @[references/android-module-memory-layout.md#L1-L28] Consistent layout file Android module.
• @[scripts/self_audit.sh#L1-L87] Self-audit static cho skill.

Scope

1. Set agents.defaults.memorySearch to the correct schema.
2. Normalize MEMORY.md + memory/YYYY-MM-DD.md usage.
3. Verify memory search operates before concluding done.
4. Do not arbitrarily edit the config if the user has not approved the patch.

Hard Rules

• Do not use legacy config path/tooling.
• No field instructions do not exist in the current schema.
• Do not hardcode API keys/tokens in the docs.
• Do not run the default network setup if the user has not requested it.
• When editing config: always backup + validate + restart with notes.

SOP (Tool-first)

Step A — Inspect current config schema

• Use gateway.config.schema to confirm the memory field is valid.
• Use gateway.config.get to see the current status.

Step B — Plan minimal patch

Patch in the correct location:

• agents.defaults.memorySearch

Commonly used fields:

• enabled
• provider (gemini|voyage|openai|local|mistral)
• model
• sources (memory, sessions)
• sync.onSessionStart, sync.watch
• query.minScore, query.maxResults

Step C — Apply safely (only when approved)

1. Backup config (or rely on config guardian process).
2. gateway.config.patch with minimal patch.
3. Wait for the restart to complete.
4. Verify with an actual memory query.

Step D — Workspace memory structure

Obligatory:

• MEMORY.md (curated long-term)
• memory/YYYY-MM-DD.md (daily notes)

Recommendation:

• memory/projects/
• memory/people/
• memory/system/

Step E — Verification checklist

• memory_search returns results from MEMORY.md or memory/*.md.
• If memory is wrong/missing: update the corresponding memory file.
• Report results + confidence.

Config Snippet (Valid Shape Example)

{
  "agents": {
    "defaults": {
      "memorySearch": {
        "enabled": true,
        "provider": "gemini",
        "model": "models/gemini-embedding-001",
        "sources": ["memory", "sessions"],
        "sync": {
          "onSessionStart": true,
          "watch": true
        },
        "query": {
          "minScore": 0.3,
          "maxResults": 20
        }
      }
    }
  }
}

Output Contract

MEMORY SETUP REVIEW
Config state: <enabled/provider/model>
Schema alignment: <pass/fail>
Memory files: <present/missing>
Verification: <pass/fail>
Notes: <risks + next action>

Trigger Rules

• Positive: Triggers when the user request matches memory-setup according to description: Standardizes memory search settings for OpenClaw-Module Android according to the current schema; Focus on properly configuring fields, memory file layout, and secure verification processes.
• Negative: Not enabled for requests outside scope or without the workflow/expertise of this skill.
• Escalation: If there is an external action/network write or sensitive operation, an approval checkpoint must be added before executing.

Error Handling

• If input/permissions are missing: report what is missing and clearly request additional information.
• If runtime/tool ​​error: brief error return + possible cause + suggested fix.
• If there is a risk policy/safety: stop and escalate according to approval checkpoint.