Skill: eugene9d/openclaw-workspace-pro (version 1.0.0)

--- name: openclaw-workspace-pro description: Production-ready workspace setup for OpenClaw agents. Implements artifact workflows, secrets management, memory compaction, and long-running agent patterns based on OpenAI's Shell + Skills best practices. One-command installation transforms your workspace into a production-ready environment. version: 1.0.0 author: Eugene Devyatyh repository: https://github.com/Eugene9D/openclaw-workspace-pro metadata: openclaw: install: - id: setup kind: script script: ./install.sh label: Install Workspace Pro enhancements --- # OpenClaw Workspace Pro Enterprise workspace setup for long-running OpenClaw agents. ## What It Does Transforms your OpenClaw workspace with production-ready patterns: - **🗂 Artifact Workflow** - Standardized output structure for reports, code, data, and exports - **🔒 Secrets Management** - Secure .env pattern, removes plaintext credentials - **🧠 Memory Compaction** - Prevents context bloat with systematic archival workflow - **📦 Long-Running Patterns** - Container reuse, checkpoint strategy, continuity protocols - **🛡 Security Baseline** - Network allowlists, safe credential handling Based on OpenAI's [Shell + Skills + Compaction](https://developers.openai.com/blog/skills-shell-tips) best practices. ## Installation ```bash clawhub install openclaw-workspace-pro ``` Or manual: ```bash cd /data/.openclaw/workspace git clone https://github.com/Eugene9D/openclaw-workspace-pro.git cd openclaw-workspace-pro ./install.sh ``` ## What Gets Installed ### Directory Structure ``` workspace/ ├── artifacts/ # Standardized output location │ ├── reports/ # Analysis, summaries, documentation │ ├── code/ # Generated scripts, apps, configs │ ├── data/ # Cleaned datasets, processed files │ └── exports/ # API responses, database dumps ├── memory/ │ └── archive/ # Compressed memory summaries ├── .env # Secrets (gitignored) └── .gitignore # Security ``` ### Documentation Added - **AGENTS.md enhancements** - Artifact workflow, long-run patterns, secrets management - **MEMORY-COMPACTION.md** - Weekly/monthly maintenance workflow - **TOOLS.md additions** - Network security allowlist ### Templates - `.env.example` - Secrets template - `.gitignore` - Protect credentials ## Usage ### Artifacts Pattern When producing deliverables: ```bash # Reports /data/.openclaw/workspace/artifacts/reports/YYYY-MM-DD-project-name.md # Code /data/.openclaw/workspace/artifacts/code/YYYY-MM-DD-script-name.py # Data /data/.openclaw/workspace/artifacts/data/YYYY-MM-DD-dataset.csv ``` **Benefits:** - Clear review boundaries - Easy retrieval - Version tracking - Prevents file sprawl ### Secrets Management **Before Workspace Pro:** ```markdown # TOOLS.md [REDACTED_SECRET] ❌ Plaintext, exposed in git ``` **After Workspace Pro:** ```bash # .env (gitignored) [REDACTED_SECRET] # TOOLS.md API Key: $API_KEY ✅ Reference only ``` ### Memory Compaction Prevents context bloat in long-running agents: **Weekly (when needed):** 1. Review daily logs from past 7-14 days 2. Extract key insights → update MEMORY.md 3. Remove outdated info **Monthly:** 1. Archive daily logs >30 days to `memory/archive/YYYY-MM-summary.md` 2. Delete raw files after archival See `MEMORY-COMPACTION.md` for full workflow. ## Why Use This? ### The Problem Default OpenClaw workspaces: - ❌ Files scattered everywhere (no structure) - ❌ API keys in plaintext (security risk) - ❌ Memory grows indefinitely (context limits) - ❌ No artifact review boundaries - ❌ Manual maintenance (prone to drift) ### The Solution Workspace Pro implements OpenAI's recommended patterns: - ✅ Standardized artifact workflow - ✅ Secure secrets management - ✅ Systematic memory compaction - ✅ Long-running agent patterns - ✅ Clear operational workflows ### Real Impact **Security:** Eliminates credential exposure **Organization:** Clear deliverable handoff points **Scalability:** Handles months of continuous operation **Maintenance:** Defined schedules prevent drift Based on production patterns from: - OpenAI's long-running agent recommendations - Glean's enterprise skill deployments - OpenClaw community best practices ## Configuration ### Environment Variables (.env) After installation, populate `.env`: ```bash # Example: YouTube API YOUTUBE_API_KEY=your_key_here YOUTUBE_OAUTH_CLIENT_ID=your_id_here # Example: Task Management VIKUNJA_API_TOKEN=your_token_here ``` ### Network Security Edit `TOOLS.md` network allowlist: ```markdown ### Approved Domains - *.googleapis.com (YouTube API) - api.brave.com (search) - tasks.playrockets.com (Vikunja) ``` Add new domains with security review. ## Requirements - OpenClaw 2026.2.9+ - Workspace directory: `/data/.openclaw/workspace` - Shell access (for installation) ## Upgrading ```bash cd /data/.openclaw/workspace/openclaw-workspace-pro git pull ./install.sh ``` ## Uninstall Workspace Pro is non-destructive. To remove: ```bash # Remove added files (safe, preserves your data) rm -rf artifacts/ memory/archive/ rm .env .gitignore MEMORY-COMPACTION.md # Restore AGENTS.md, TOOLS.md from backup cp AGENTS.md.backup AGENTS.md cp TOOLS.md.backup TOOLS.md ``` ## Support - **Issues:** https://github.com/Eugene9D/openclaw-workspace-pro/issues - **Discussions:** https://discord.com/invite/clawd - **ClawHub:** https://clawhub.ai/skills/openclaw-workspace-pro ## License MIT License - See LICENSE file ## Credits Based on patterns from: - [OpenAI Shell + Skills + Compaction](https://developers.openai.com/blog/skills-shell-tips) - OpenClaw community practices - Glean enterprise skill deployments Built by Eugene Devyatyh for the OpenClaw ecosystem. --- **Version:** 1.0.0 **Updated:** 2026-02-13 **Compatibility:** OpenClaw 2026.2.9+

path: CHANGELOG.md
content: # Changelog

All notable changes to OpenClaw Workspace Pro will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [1.0.0] - 2026-02-13

### Added
- Initial release of OpenClaw Workspace Pro
- Artifact workflow with standardized `/artifacts/` structure
- Secrets management with `.env` pattern
- Memory compaction workflow (`MEMORY-COMPACTION.md`)
- Long-running agent patterns in `AGENTS.md`
- Network security allowlist in `TOOLS.md`
- Automated installation script (`install.sh`)
- Comprehensive documentation (README, SKILL.md)
- Template files for easy setup
- MIT License
- ClawHub package configuration

### Features
- **Artifacts:** `reports/`, `code/`, `data/`, `exports/` subdirectories
- **Security:** `.gitignore` protects `.env` from git commits
- **Memory:** `memory/archive/` for compacted summaries
- **Documentation:** Inline AGENTS.md and TOOLS.md enhancements
- **Non-destructive:** Installation preserves existing files with backups

### Inspired By
- OpenAI's Shell + Skills + Compaction recommendations
- Glean enterprise skill deployments
- OpenClaw community best practices

---

## [Unreleased]

### Planned
- Interactive setup wizard
- Pre-commit hooks for secret detection
- Automated memory compaction cron job
- Integration tests
- Docker compose example
- Video tutorials

---

For full details, see [GitHub Releases](https://github.com/Eugene9D/openclaw-workspace-pro/releases).


path: CONTRIBUTING.md
content: # Contributing to OpenClaw Workspace Pro

Thank you for considering contributing! This document provides guidelines for contributing to the project.

## Code of Conduct

Be respectful, inclusive, and constructive. We're building tools for the OpenClaw community.

## How to Contribute

### Reporting Bugs

1. **Check existing issues** - Someone might have already reported it
2. **Create a detailed issue** with:
   - Clear title and description
   - Steps to reproduce
   - Expected vs actual behavior
   - OpenClaw version
   - Environment details (OS, Docker, etc.)

### Suggesting Features

1. **Search existing feature requests**
2. **Open a new issue** with:
   - Clear use case
   - Why it's valuable
   - Proposed implementation (optional)

### Pull Requests

1. **Fork the repository**
2. **Create a feature branch**: `git checkout -b feature/your-feature-name`
3. **Make your changes**:
   - Follow existing code style
   - Add tests if applicable
   - Update documentation
4. **Commit with clear messages**: 
   - `feat: Add artifact validation`
   - `fix: Resolve .env overwrite issue`
   - `docs: Update memory compaction guide`
5. **Push to your fork**: `git push origin feature/your-feature-name`
6. **Open a Pull Request** with:
   - Clear description of changes
   - Link to related issues
   - Screenshots (if UI changes)

## Development Setup

```bash
# Clone your fork
git clone https://github.com/YOUR_USERNAME/openclaw-workspace-pro.git
cd openclaw-workspace-pro

# Test installation
./install.sh

# Make changes
# ...

# Test your changes
./install.sh
```

## Guidelines

### Code Style
- Use clear, descriptive variable names
- Comment complex logic
- Keep functions focused and small
- Follow existing patterns

### Documentation
- Update README.md for user-facing changes
- Update SKILL.md for skill behavior changes
- Add inline comments for complex logic
- Update CHANGELOG.md

### Testing
- Test installation on clean workspace
- Test upgrades from previous versions
- Verify backups are created correctly
- Test on different OpenClaw versions (when possible)

## Project Structure

```
openclaw-workspace-pro/
├── SKILL.md              # Skill manifest + documentation
├── README.md             # GitHub homepage
├── install.sh            # Installation script
├── templates/            # Template files for installation
│   ├── gitignore
│   ├── env.example
│   ├── MEMORY-COMPACTION.md
│   ├── AGENTS-additions.md
│   └── TOOLS-additions.md
├── docs/                 # Detailed documentation (future)
├── LICENSE               # MIT License
├── CHANGELOG.md          # Version history
└── package.json          # ClawHub metadata
```

## Release Process

1. Update `CHANGELOG.md` with changes
2. Bump version in `SKILL.md`, `package.json`, `install.sh`
3. Create git tag: `git tag v1.x.x`
4. Push tag: `git push origin v1.x.x`
5. Create GitHub release
6. Publish to ClawHub (maintainers only)

## Questions?

- **GitHub Discussions:** https://github.com/Eugene9D/openclaw-workspace-pro/discussions
- **OpenClaw Discord:** https://discord.com/invite/clawd
- **Issues:** https://github.com/Eugene9D/openclaw-workspace-pro/issues

---

Thank you for contributing to OpenClaw Workspace Pro! 🚀


path: README.md
content: # OpenClaw Workspace Pro

> **Production-ready workspace setup for long-running OpenClaw AI agents**

Transform your OpenClaw workspace from basic to production-ready in minutes. Implements battle-tested patterns for artifact management, secrets security, memory optimization, and continuous operation.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![OpenClaw](https://img.shields.io/badge/OpenClaw-2026.2.9%2B-blue)](https://openclaw.ai)
[![ClawHub](https://img.shields.io/badge/ClawHub-Published-green)](https://clawhub.ai/skills/openclaw-workspace-pro)

---

## 🎯 Why Workspace Pro?

**Default OpenClaw workspaces struggle with:**
- ❌ Files scattered across directories (no standardization)
- ❌ API keys exposed in plaintext (security vulnerability)
- ❌ Memory grows indefinitely (context limit crashes)
- ❌ No clear artifact handoff boundaries
- ❌ Manual maintenance prone to drift

**Workspace Pro solves this with:**
- ✅ **Artifact workflow** - Standardized output structure
- ✅ **Secrets management** - Secure .env pattern, git-safe
- ✅ **Memory compaction** - Systematic archival prevents bloat
- ✅ **Long-running patterns** - Container reuse, checkpointing
- ✅ **Security baseline** - Network allowlists, safe credentials

Based on [OpenAI's Shell + Skills + Compaction](https://developers.openai.com/blog/skills-shell-tips) recommendations and proven in production environments.

---

## 🚀 Quick Start

### Installation

**Via ClawHub (recommended):**
```bash
clawhub install openclaw-workspace-pro
```

**Manual:**
```bash
cd /data/.openclaw/workspace
git clone https://github.com/Eugene9D/openclaw-workspace-pro.git
cd openclaw-workspace-pro
./install.sh
```

**Post-install:**
1. Edit `.env` with your API credentials
2. Review `AGENTS.md` additions
3. Read `MEMORY-COMPACTION.md` for maintenance workflow
4. Start using `artifacts/` for all deliverables

---

## 📦 What Gets Installed

### Directory Structure
```
workspace/
├── artifacts/           # 📁 Standardized output location
│   ├── reports/        # Analysis, summaries, documentation
│   ├── code/           # Generated scripts, apps, configs
│   ├── data/           # Cleaned datasets, processed files
│   └── exports/        # API responses, database dumps
├── memory/
│   └── archive/        # 🗄 Compressed memory summaries
├── .env                # 🔒 Secrets (gitignored)
├── .gitignore          # 🛡 Security
├── MEMORY-COMPACTION.md # 🧠 Maintenance workflow
├── AGENTS.md           # 📝 Enhanced with pro patterns
└── TOOLS.md            # 🔧 Network security additions
```

### Core Components

#### 1. Artifact Workflow
Standardized location for all agent outputs:

```bash
artifacts/reports/2026-02-13-analysis-report.md
artifacts/code/2026-02-13-data-processor.py
artifacts/data/2026-02-13-cleaned-dataset.csv
```

**Benefits:**
- Clear review boundaries
- Easy artifact retrieval
- Automatic version tracking
- Prevents workspace sprawl

#### 2. Secrets Management
Moves credentials from documentation to secure `.env`:

**Before:**
```markdown
# TOOLS.md
[REDACTED_SECRET]  ❌ Plaintext, exposed
```

**After:**
```bash
# .env (gitignored)
[REDACTED_SECRET]

# TOOLS.md
API Key: $API_KEY  ✅ Reference only
```

#### 3. Memory Compaction
Prevents context bloat in long-running agents:

**Weekly (when needed):**
- Review daily logs (past 7-14 days)
- Extract key insights → `MEMORY.md`
- Remove outdated info

**Monthly:**
- Archive logs >30 days → `memory/archive/YYYY-MM-summary.md`
- Delete raw files after archival

**Impact:** Agents can run for months without context issues.

#### 4. Long-Running Patterns
Container reuse, checkpointing, continuity protocols:

```
Day 1: Research → log in daily memory
Day 2: Read yesterday's memory → continue work
Day 3: Checkpoint to artifacts/ → update Vikunja
Day N: Reference workspace files, not chat history
```

#### 5. Security Baseline
Network allowlists, credential handling, audit practices:

```markdown
### Approved Domains
- *.googleapis.com (Google APIs)
- api.brave.com (Search)
- github.com (Code repos)

### Blocked
- Pastebin services (exfiltration risk)
- Anonymous shells (security risk)
```

---

## 💡 Use Cases

### For AI Developers
- **Long-running agents** that operate for days/weeks/months
- **Production deployments** requiring security + reliability
- **Multi-step workflows** with artifact handoffs
- **Enterprise environments** with compliance requirements

### For Researchers
- **Data analysis pipelines** with clear artifact boundaries
- **Reproducible research** with version-tracked outputs
- **Collaborative work** with safe credential sharing
- **Long-term projects** without memory degradation

### For Automation
- **Business process automation** with audit trails
- **Report generation** with standardized output
- **API integrations** with secure credential management
- **Scheduled workflows** with continuity across runs

---

## 🎓 Documentation

### Core Guides
- **[Installation Guide](docs/installation.md)** - Step-by-step setup
- **[Artifact Workflow](docs/artifacts.md)** - How to structure outputs
- **[Secrets Management](docs/secrets.md)** - Secure credential handling
- **[Memory Compaction](docs/memory.md)** - Maintenance workflow
- **[Security Best Practices](docs/security.md)** - Network & access control

### References
- **[SKILL.md](SKILL.md)** - Complete skill documentation
- **[MEMORY-COMPACTION.md](templates/MEMORY-COMPACTION.md)** - Full compaction workflow
- **[FAQ](docs/faq.md)** - Common questions

---

## 🔧 Configuration

### Environment Variables

Edit `.env` after installation:

```bash
# Google APIs
YOUTUBE_API_KEY=your_key_here
YOUTUBE_OAUTH_CLIENT_ID=your_id_here

# Task Management
VIKUNJA_API_TOKEN=your_token_here

# Search
BRAVE_SEARCH_API_KEY=your_key_here
```

### Network Security

Edit `TOOLS.md` to customize allowed domains:

```markdown
### Approved Domains
- your-api.example.com (Your service)
- *.trusted-service.com (Trusted partner)
```

---

## 📊 Comparison

| Feature | Default Workspace | Workspace Pro |
|---------|------------------|---------------|
| **Artifact Structure** | Ad-hoc | Standardized `/artifacts/` |
| **Secrets Security** | Plaintext in docs | Secure `.env` + gitignore |
| **Memory Management** | Manual, no plan | Automated compaction workflow |
| **Long-running Support** | Limited | Full continuity patterns |
| **Network Security** | Unrestricted | Allowlist + audit |
| **Production Ready** | ❌ No | ✅ Yes |
| **Git Safe** | ❌ No | ✅ Yes |
| **Maintenance Overhead** | High | Low (documented workflows) |

---

## 🧪 Battle-Tested

**Based on patterns from:**
- [OpenAI's Shell + Skills + Compaction](https://developers.openai.com/blog/skills-shell-tips) recommendations
- Glean's enterprise AI skill deployments
- OpenClaw community production environments
- Months of continuous agent operation

**Proven to handle:**
- ✅ Multi-month continuous operation
- ✅ 100+ artifacts generated per day
- ✅ Dozens of API integrations
- ✅ Memory growth from MB → GB
- ✅ Security audits & compliance reviews

---

## 🛠 Requirements

- **OpenClaw:** 2026.2.9 or later
- **Workspace:** `/data/.openclaw/workspace` (standard location)
- **Shell Access:** For installation
- **Git:** Optional, for updates

---

## 🔄 Upgrading

```bash
cd /data/.openclaw/workspace/openclaw-workspace-pro
git pull
./install.sh
```

Backward compatible. Non-destructive upgrades preserve your data.

---

## 🗑 Uninstalling

Workspace Pro is non-destructive. To remove:

```bash
# Remove added directories
rm -rf artifacts/ memory/archive/

# Remove added files
rm .env .gitignore MEMORY-COMPACTION.md

# Restore originals from backups
cp AGENTS.md.backup.* AGENTS.md
cp TOOLS.md.backup.* TOOLS.md
```

Your data and customizations are preserved in backups.

---

## 🤝 Contributing

Contributions welcome! Please:

1. Fork the repository
2. Create a feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines.

---

## 📝 License

MIT License - see [LICENSE](LICENSE) file for details.

---

## 🙏 Credits

**Created by:** Eugene Devyatyh ([Eugene9D](https://github.com/Eugene9D))

**Inspired by:**
- [OpenAI Shell + Skills + Compaction](https://developers.openai.com/blog/skills-shell-tips)
- Glean enterprise skill patterns
- OpenClaw community best practices

**Special thanks to:**
- OpenClaw team for the framework
- Early testers and contributors
- OpenAI for publishing long-running agent patterns

---

## 🔗 Links

- **GitHub:** https://github.com/Eugene9D/openclaw-workspace-pro
- **ClawHub:** https://clawhub.ai/skills/openclaw-workspace-pro
- **OpenClaw:** https://openclaw.ai
- **Documentation:** https://github.com/Eugene9D/openclaw-workspace-pro/wiki
- **Issues:** https://github.com/Eugene9D/openclaw-workspace-pro/issues
- **Discussions:** https://github.com/Eugene9D/openclaw-workspace-pro/discussions

---

## 📈 Stats

![GitHub stars](https://img.shields.io/github/stars/Eugene9D/openclaw-workspace-pro?style=social)
![GitHub forks](https://img.shields.io/github/forks/Eugene9D/openclaw-workspace-pro?style=social)
![GitHub watchers](https://img.shields.io/github/watchers/Eugene9D/openclaw-workspace-pro?style=social)

---

<div align="center">

**⭐ Star this repo if Workspace Pro helped you!**

Made with ❤️ for the OpenClaw community

[Report Bug](https://github.com/Eugene9D/openclaw-workspace-pro/issues) · [Request Feature](https://github.com/Eugene9D/openclaw-workspace-pro/issues) · [Documentation](https://github.com/Eugene9D/openclaw-workspace-pro/wiki)

</div>


path: install.sh
content: #!/bin/bash
set -e

# OpenClaw Workspace Pro - Installation Script
# Version: 1.0.0

WORKSPACE_DIR="${WORKSPACE_DIR:-/data/.openclaw/workspace}"
SKILL_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"

echo "🚀 Installing OpenClaw Workspace Pro..."
echo ""

# Backup existing files
backup_if_exists() {
    local file=$1
    if [ -f "$WORKSPACE_DIR/$file" ]; then
        echo "📦 Backing up existing $file..."
        cp "$WORKSPACE_DIR/$file" "$WORKSPACE_DIR/$file.backup.$(date +%Y%m%d-%H%M%S)"
    fi
}

# Create directory structure
echo "📁 Creating directory structure..."
mkdir -p "$WORKSPACE_DIR/artifacts/"{reports,code,data,exports}
mkdir -p "$WORKSPACE_DIR/memory/archive"
echo "   ✅ artifacts/ created"
echo "   ✅ memory/archive/ created"

# Install .gitignore
echo ""
echo "🛡 Installing .gitignore..."
if [ ! -f "$WORKSPACE_DIR/.gitignore" ]; then
    cp "$SKILL_DIR/templates/gitignore" "$WORKSPACE_DIR/.gitignore"
    echo "   ✅ .gitignore created"
else
    echo "   ⚠️  .gitignore exists, skipping (see templates/gitignore for reference)"
fi

# Install .env template
echo ""
echo "🔒 Installing .env template..."
if [ ! -f "$WORKSPACE_DIR/.env" ]; then
    cp "$SKILL_DIR/templates/env.example" "$WORKSPACE_DIR/.env"
    echo "   ✅ .env created (populate with your secrets)"
else
    echo "   ⚠️  .env exists, preserving (see templates/env.example for reference)"
fi

# Install MEMORY-COMPACTION.md
echo ""
echo "🧠 Installing memory compaction workflow..."
cp "$SKILL_DIR/templates/MEMORY-COMPACTION.md" "$WORKSPACE_DIR/MEMORY-COMPACTION.md"
echo "   ✅ MEMORY-COMPACTION.md installed"

# Update AGENTS.md
echo ""
echo "📝 Updating AGENTS.md..."
backup_if_exists "AGENTS.md"
if [ -f "$WORKSPACE_DIR/AGENTS.md" ]; then
    # Check if already has Workspace Pro markers
    if grep -q "## 📦 Artifact Workflow" "$WORKSPACE_DIR/AGENTS.md"; then
        echo "   ⚠️  AGENTS.md already has Workspace Pro sections, skipping"
    else
        # Append Workspace Pro sections
        cat "$SKILL_DIR/templates/AGENTS-additions.md" >> "$WORKSPACE_DIR/AGENTS.md"
        echo "   ✅ AGENTS.md updated"
    fi
else
    echo "   ⚠️  AGENTS.md not found, skipping (create workspace first)"
fi

# Update TOOLS.md
echo ""
echo "🔧 Updating TOOLS.md..."
backup_if_exists "TOOLS.md"
if [ -f "$WORKSPACE_DIR/TOOLS.md" ]; then
    if grep -q "### Network Security - Approved Domains" "$WORKSPACE_DIR/TOOLS.md"; then
        echo "   ⚠️  TOOLS.md already has network security section, skipping"
    else
        cat "$SKILL_DIR/templates/TOOLS-additions.md" >> "$WORKSPACE_DIR/TOOLS.md"
        echo "   ✅ TOOLS.md updated"
    fi
else
    echo "   ⚠️  TOOLS.md not found, skipping (create workspace first)"
fi

# Summary
echo ""
echo "✨ Installation complete!"
echo ""
echo "📋 Next Steps:"
echo "   1. Populate .env with your API credentials"
echo "   2. Review AGENTS.md additions (artifact workflow, secrets management)"
echo "   3. Read MEMORY-COMPACTION.md for maintenance workflow"
echo "   4. Start using artifacts/ for all deliverables"
echo ""
echo "📚 Documentation: $SKILL_DIR/SKILL.md"
echo "🐛 Issues: https://github.com/Eugene9D/openclaw-workspace-pro/issues"
echo ""
echo "Happy building! 🚀"


path: package.json
content: {
  "name": "openclaw-workspace-pro",
  "version": "1.0.0",
  "description": "Production-ready workspace setup for long-running OpenClaw AI agents",
  "keywords": [
    "openclaw",
    "workspace",
    "agent",
    "ai",
    "automation",
    "memory-management",
    "secrets",
    "security",
    "artifact-workflow",
    "production-ready",
    "long-running-agent"
  ],
  "author": "Eugene Devyatyh <[REDACTED_SECRET]>",
  "license": "MIT",
  "homepage": "https://github.com/Eugene9D/openclaw-workspace-pro#readme",
  "repository": {
    "type": "git",
    "url": "https://github.com/Eugene9D/openclaw-workspace-pro.git"
  },
  "bugs": {
    "url": "https://github.com/Eugene9D/openclaw-workspace-pro/issues"
  },
  "openclaw": {
    "skill": {
      "name": "openclaw-workspace-pro",
      "version": "1.0.0",
      "compatibility": ">=2026.2.9",
      "category": "workspace",
      "tags": [
        "workspace",
        "security",
        "memory",
        "artifacts",
        "production"
      ]
    }
  }
}


path: templates/AGENTS-additions.md
content: 

## 📦 Artifact Workflow

When producing deliverables (reports, code, datasets, exports):

**Standard Output Location:** `/data/.openclaw/workspace/artifacts/`

**Structure:**
- `artifacts/reports/` — analysis reports, summaries, documentation
- `artifacts/code/` — generated scripts, apps, configuration files
- `artifacts/data/` — cleaned datasets, processed files
- `artifacts/exports/` — exports from tools (database dumps, API responses)

**Pattern:**
1. Write all deliverables to the appropriate artifacts subdirectory
2. Use descriptive filenames with dates: `YYYY-MM-DD-project-name-description.ext`
3. Log artifact location in daily memory
4. **Treat artifacts as review boundaries** — don't auto-deploy or auto-send without approval

**Example:**
```
artifacts/reports/2026-02-13-jigsaw-compliance-analysis.md
artifacts/code/2026-02-13-youtube-transcript-fetcher.py
artifacts/data/2026-02-13-task-export.csv
```

**Why:** Clean handoff boundary, easy retrieval, version tracking, explicit review point.

## 🔄 Long-Running Work Pattern

For multi-step tasks that span multiple messages or sessions:

**Container Reuse:**
- You're already in a persistent Docker container — use it!
- Install dependencies once, reuse across steps
- Write intermediate outputs to workspace files
- Don't restart from scratch each time

**Continuity Protocol:**
1. **Log progress** in daily memory after each major step
2. **Use Vikunja** for task tracking across sessions (create tasks, update status)
3. **Checkpoint artifacts** before major transitions (write to `/artifacts/`)
4. **Document decisions** in MEMORY.md for long-term recall
5. **Reference previous work** by reading workspace files, not relying on chat history

**Multi-Day Work:**
- Day 1: Research, plan, document in daily memory
- Day 2: Read yesterday's memory, continue where you left off
- Day 3+: Same pattern — memory files are your continuity

**Example Flow:**
```
1. Task starts: Create Vikunja task, log in daily memory
2. Step 1 done: Write intermediate output to workspace, log progress
3. Step 2 done: Write artifact to /artifacts/, update Vikunja
4. Final: Mark Vikunja task complete, summarize in MEMORY.md
```

## 🔒 Secrets Management

**Rule:** Never store API keys, tokens, or passwords in plaintext in committed files.

**Pattern:**
- Secrets live in `.env` file (gitignored)
- Reference as `$VARIABLE_NAME` in documentation
- Load from environment variables at runtime
- TOOLS.md documents what secrets exist, not their values

**Current .env secrets:**
- (List your secrets here as you add them)

**Never:**
- Commit `.env` to git
- Paste raw secrets in chat logs
- Include secrets in artifacts meant for sharing


path: templates/MEMORY-COMPACTION.md
content: # Memory Compaction Workflow
**Purpose:** Keep long-term memory manageable and prevent context bloat

## Memory Structure

### Daily Logs (Raw)
- **Location:** `memory/YYYY-MM-DD.md`
- **Purpose:** Raw chronological log of events, decisions, learnings
- **Retention:** 30 days
- **Format:** Timestamped entries, unedited stream of consciousness

### Long-Term Memory (Curated)
- **Location:** `MEMORY.md`
- **Purpose:** Distilled wisdom, important patterns, key decisions
- **Retention:** Permanent (but updated/refined over time)
- **Format:** Organized sections, curated insights

### Archives (Compressed)
- **Location:** `memory/archive/YYYY-MM-summary.md`
- **Purpose:** Compressed summaries of old daily logs
- **Retention:** Indefinite (small footprint)
- **Format:** Weekly or monthly summaries

---

## Compaction Schedule

### Weekly Compaction (Every Sunday during heartbeat)
**Process:**
1. Review daily logs from 7-14 days ago
2. Extract:
   - Key decisions made
   - New patterns learned
   - Important context for future
   - Tool/skill discoveries
3. Update MEMORY.md with distilled insights
4. Create weekly summary if significant events occurred

**Time estimate:** 5-10 minutes

### Monthly Archival (First of each month)
**Process:**
1. Review all daily logs >30 days old
2. Create monthly summary in `memory/archive/`
3. Delete raw daily logs >30 days (after archival confirmation)
4. Update MEMORY.md index if structure changed

**Time estimate:** 15-20 minutes

---

## What to Extract to MEMORY.md

### ✅ Keep Long-Term:
- **Patterns:** Recurring issues, successful workflows, failure modes
- **Decisions:** Major architectural choices, tool selections, rejected alternatives
- **Context:** Background info needed to understand why things are the way they are
- **Preferences:** Eugene's stated preferences about communication, tools, workflows
- **Relationships:** Connections between different parts of the system
- **Lessons:** "Don't do X because Y" type insights

### ❌ Don't Keep:
- Ephemeral task updates ("Started X", "Finished Y")
- Routine operations (daily heartbeat acks, simple queries)
- Temporary states that are no longer relevant
- Debug logs from resolved issues
- Duplicated information already in MEMORY.md

---

## Compaction Checklist

### Weekly (Sundays)
- [ ] Read daily logs from last 7-14 days
- [ ] Identify 2-3 key insights worth keeping
- [ ] Update relevant sections in MEMORY.md
- [ ] Note if any old info in MEMORY.md is now obsolete
- [ ] Log compaction completion in today's daily log

### Monthly (1st of month)
- [ ] Create archive summary for previous month
- [ ] Move summary to `memory/archive/`
- [ ] Delete daily logs >30 days old (after archival)
- [ ] Review MEMORY.md structure — is it still organized?
- [ ] Update this checklist if workflow needs adjustment

---

## Memory Sections in MEMORY.md

**Current structure:**
1. Identity (who I am, who Eugene is)
2. Setup (technical configuration, tools, access)
3. Model Routing (cost optimization, model selection)
4. Working Style Lessons (proactive behavior, communication)
5. Security Rules
6. TODO (active tasks, pending items)

**Review these sections during compaction:**
- Is info still accurate?
- Are there duplicates?
- Is anything missing?
- Does structure make sense?

---

## Automation

### Cron Job (Optional - Phase 3)
Create a weekly cron job that sends a reminder:
```
Every Sunday 10:00 AM: "Weekly memory compaction time. Review last week's daily logs and update MEMORY.md."
```

**Implementation:** Use OpenClaw cron with isolated session + announce delivery

---

## Metrics to Track

- **Daily log size:** Avg lines per day (track bloat)
- **MEMORY.md size:** Total lines (should grow slowly)
- **Archive count:** Number of monthly summaries
- **Compaction frequency:** Actual vs. planned
- **Time spent:** Minutes per compaction session

**Goal:** Keep MEMORY.md under 500 lines, daily logs under 200 lines avg, compaction time under 10 min.

---

## Status

- **Last weekly compaction:** Never (workflow just created)
- **Last monthly archival:** N/A
- **Next weekly:** 2026-02-16 (Sunday)
- **Next monthly:** 2026-03-01
- **Current MEMORY.md size:** ~100 lines
- **Oldest daily log:** 2026-02-12 (2 days old)


path: templates/TOOLS-additions.md
content: 

### Network Security - Approved Domains
**Only access these domains without asking first:**
- `*.googleapis.com`, `oauth2.googleapis.com` (Google APIs)
- `api.brave.com` (search)
- `api.telegram.org` (messaging)
- `github.com`, `*.github.com` (code repos)
- `clawhub.com`, `*.clawhub.com` (skills)
- Standard package managers (Homebrew, npm, pip official registries)

**For new domains:** Ask first with brief reason.

**Never access without security review:**
- Pastebin-type services (data exfiltration risk)
- Ngrok/remote shells
- Anonymous/temporary services


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: suspicious (CRITICAL)