workspace-standard
Set up and maintain a structured OpenClaw workspace with project boundaries, role-based file taxonomy, and memory budgets. Use when: (1) bootstrapping a new workspace, (2) migrating from a flat docs/ structure, (3) adding a new project, (4) unsure where to write something, (5) running workspace maintenance, (6) auditing workspace health. Provides the directory layout, ROLE front-matter spec, MEMORY.md budget rules, and maintenance procedures.
Why use this skill?
Organize your OpenClaw workspace with the workspace-standard skill. Enforce file taxonomy, manage memory budgets, and automate project health audits.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/marcus-daemon/workspace-standardWhat This Skill Does
The workspace-standard skill provides a rigid, scalable, and portable architectural framework for OpenClaw agents. Instead of letting documentation sprawl in an unstructured 'docs/' folder, this skill imposes a hierarchical taxonomy based on roles and project boundaries. It manages the lifecycle of your workspace by defining where entities live, enforcing front-matter specifications for metadata, and establishing strict memory budgets within MEMORY.md. By integrating automated maintenance, it ensures that your agent doesn't lose context as projects evolve, keeping references distinct from plans and research logs.
Installation
To begin, ensure you have the clawhub CLI installed. Run the following command in your terminal within the root of your project:
clawhub install openclaw/skills/skills/marcus-daemon/workspace-standard
Once installed, you can initialize a fresh workspace structure by executing bash skills/workspace-standard/scripts/workspace-init.sh. If you are integrating this into an existing messy codebase, simply run the audit script first to identify structural gaps.
Use Cases
This skill is ideal for:
- Bootstrapping New Projects: Instantly generate standardized directory trees (references, plans, research, reports) for new work.
- Migration: Converting a flat, unmanageable 'docs/' folder into a navigable, agent-readable hierarchy.
- Workspace Maintenance: Periodically auditing the health of your workspace, checking for stale references, and ensuring MEMORY.md adheres to established budget constraints.
- Onboarding: When you switch agents or need a collaborator to immediately understand your project architecture, the workspace-standard layout serves as a self-documenting interface.
Example Prompts
- "I'm starting a new machine learning module; can you run the workspace-init script to set up the structure for it?"
- "We seem to have a lot of stale tasks in our project folders. Please run the workspace-audit script and report any issues found."
- "I'm not sure where to store my research findings for the current API project; can you place them in the correct folder based on the workspace-standard?"
Tips & Limitations
- Tip: Always create a
.workspace-standard.ymlfile in your root to override directory defaults if your team has specific naming conventions. - Tip: Treat the output of
workspace-audit.shas the primary indicator for when to archive old projects. - Limitation: This skill does not automatically delete files. It provides the audit trail and structure, but you remain responsible for final deletion decisions. It is purely an organizational layer; your files remain standard markdown, ensuring no vendor lock-in if you decide to uninstall the skill later.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-marcus-daemon-workspace-standard": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read, code-execution