🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί File Management (Brian)
πŸ¦€ ClawHub

File Management (Brian)

by @briandavisbikes-code

Organize and maintain AI agent workspaces using structured directories, clear naming, regular audits, and safe cleanup of unused or dead files.

Versionv1.0.0
Downloads617
#legal#productivity
TERMINAL
clawhub install briandavis-file-mgmt

πŸ“– About This Skill

File Management Skill

_A battle-tested approach to keeping your AI agent workspace organized and maintainable._

Overview

This skill documents the file management system developed through real-world use of OpenClaw. It covers workspace structure, naming conventions, dead file detection, and cleanup practices.

When to Use This Skill

  • Onboarding a new agent or setting up a fresh workspace
  • Performing periodic workspace audits
  • Before making significant changes to workspace structure
  • When workspace feels cluttered or disorganized

    • Core Principles

    1. Every File Has a Purpose

  • Active files: Scripts, configs, and data in use by cron jobs or agents
  • Reference files: Documentation, strategies, and notes
  • Archived files: Old versions, completed project artifacts
  • Dead files: Abandoned scripts, old experiments, unused utilities

    • 2. Structure Mirrors Function

    workspace/
β”œβ”€β”€ memory/          # Daily session logs and working context
β”œβ”€β”€ skills/           # Installed skill directories
β”œβ”€β”€ project-1/        # Project-specific directories
β”œβ”€β”€ project-2/
β”œβ”€β”€ ACTIVE.md         # Currently running projects & priorities
β”œβ”€β”€ DREAMS.md         # Background processing notes
└── ARCHIVED/         # Completed or abandoned projects

    3. Naming Conventions

  • Scripts: Use .sh for bash, .py for Python, .js for JavaScript
  • Logs: End with .log
  • Configs: End with .json, .yaml, or .md
  • Daily notes: memory/YYYY-MM-DD.md format

    • 4. Audit Regularly

    Run workspace audits monthly or after major changes. Use the audit script to identify:
  • Dead files (no references from active crons or scripts)
  • Large files consuming storage
  • Outdated documentation

    • Quick Audit Commands

    # Find files not referenced by any cron or script
grep -r "filename" ~/path/to/workspace/ --include="*.sh" --include="*.py" --include="*.js"
    Find recently modified files
    
find ~/path/to/workspace -type f -mtime -7
    Check disk usage by directory
    
du -sh ~/path/to/workspace/*/

    Cleanup Best Practices

    1. Never delete immediately β€” use trash instead of rm 2. Document before deleting β€” note what a file did in memory first 3. Verify before cleanup β€” confirm no active references 4. Commit before major cleanup β€” create a revert point

    Full Documentation

    See FILE-MANAGEMENT.md for the complete reference implementation, including:

  • Directory structure explainer
  • Active vs archived file definitions
  • Dead file detection criteria
  • Example cleanup checklists