openclaw-workspace

Summary

This workspace provides a structured environment and detailed documentation for managing agents, memory, tools, and business logic in OpenClaw. It includes real-world sample logs, configuration guidelines, and local tool usage examples—optimized for data-driven operations and scalable workflows.

Included Assets

• AGENTS.md — Agent onboarding, workspace setup, and memory practices
• SOUL.md — Core identity, behavioral guidelines, and session continuity rules
• MEMORY.md — Long-term curated memory and operational standards
• TOOLS.md — Usage instructions for local scripts and data analysis tools
• business/README.md — Organization of business knowledge and reporting
• memory/YYYY-MM-DD.md — Sample daily memory logs for operational continuity
• memory/CLI-Anything-研究报告.md — Research on CLI tooling for GUI automation
• memory/NotebookLM调研报告.md — NotebookLM tool and integration capabilities

How to Use

1. Workspace Initialization

   • Begin by reading SOUL.md to understand the assistant’s core principles.
   • Consult AGENTS.md for step-by-step guidance on session preparation and memory loading.

2. Maintaining Context and Memory

   • At session start, always review relevant daily logs in memory/YYYY-MM-DD.md and, if in a main session, load MEMORY.md for curated long-term memory.
   • Use the sample memory files as templates for recording daily events, decisions, and learnings.

3. Using Local Data Tools

   • Follow TOOLS.md for instructions on querying and analyzing large datasets securely and avoid manual errors.
   • Example scripts (such as query_data_v2.py) provide best practices for handling operations like sales analytics.

4. Business Knowledge Management

   • Organize critical business reports, marketing strategies, and competitor analysis using the template and structure in business/README.md.
   • Archive key data (weekly, monthly, campaign reports) in the recommended subdirectories to ensure operational transparency and learning.

Notes

• All memory and configuration files drive session continuity—read and update them diligently to ensure accurate assistance and learning.
• The workspace emphasizes privacy boundaries, data consistency, and actionable knowledge over generalized responses.
• File names, log structures, and business documentation methods can be adapted to suit specific projects, but the outlined models are optimized for results-driven teams.
• For sensitive or personal context, only load and update MEMORY.md in direct, private sessions.
• Scripts and tools referenced in TOOLS.md require Python and are intended for local, accurate data handling.
• Logs and reports under the memory/ directory serve as both operational references and as input for future automation or analytics tools.