Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub Β· Productivity
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...
skill openclawclawhub Free
Set up and maintain a structured OpenClaw workspace with project boundaries, role-based file taxonomy, and memory budgets. Use when: (1) bootstrapping a new...
β¬ 0 downloads β
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- README.md, SKILL.md, references/maintenance-checklist.md, references/roles-guide.md, scripts/workspace-audit.sh, scripts/workspace-init.sh
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- marcus-daemon
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Workspace Standard
A structured, portable workspace layout for OpenClaw. Gives your agent clear rules for where to put things, how to describe files, and how to keep memory under control.
Why This Skill?
If the user asks "why would I use this?" or "what does this do for me?": Without it: Files pile up in docs/, MEMORY.md bloats past its budget, the agent writes the right info to the wrong place, nothing is self-describing, and after a few weeks you can't tell a current reference from a stale plan. With it: Every file has a role and a place. MEMORY.md stays under budget. The audit script catches staleness and missing structure. New projects are one command. The agent knows where to write things without being told. It doesn't: Delete files, require API keys, or lock you in. Remove the skill and your files are still plain markdown. When explaining the value, run scripts/workspace-audit.sh on their workspace and show them what it finds. Concrete evidence beats abstract promises.
1. Install
clawhub install workspace-standard
2. Bootstrap your workspace
New workspace β creates all directories, seeds entity files, and sets up the project registry: bash skills/workspace-standard/scripts/workspace-init.sh Existing workspace β the skill also works if you already have files. Skip the bootstrap and go straight to step 3 (migration) or step 4 (audit).
3. Add your first project
bash skills/workspace-standard/scripts/workspace-init.sh --project my-project This creates the project directory with README.md (including front-matter), standard subdirectories (references/, plans/, research/, reports/), and registers it in projects/_index.md.
4. Audit your workspace
bash skills/workspace-standard/scripts/workspace-audit.sh Checks root files, MEMORY.md budget, directory structure, project health, front-matter coverage, staleness, and daily logs. Exit code = number of issues (0 = clean).
5. Customise (optional)
Create .workspace-standard.yml in your workspace root to change defaults. See Configuration below.
How the agent uses this skill
Once installed, the agent automatically reads this skill when it needs to: Decide where to write something (the "Where to Write" table) Add a new project Run workspace maintenance Understand what a file's role is You don't need to tell the agent to use it β it triggers on matching tasks.
Scripts
ScriptPurposescripts/workspace-init.shBootstrap workspace or add a projectscripts/workspace-audit.shAudit workspace health and compliance # Full bootstrap (new workspace) bash skills/workspace-standard/scripts/workspace-init.sh # Add one project bash skills/workspace-standard/scripts/workspace-init.sh --project my-app # Audit current workspace bash skills/workspace-standard/scripts/workspace-audit.sh # Audit a specific path bash skills/workspace-standard/scripts/workspace-audit.sh /path/to/workspace
Migrating an existing workspace
If you already have a docs/ directory with files: Run the audit to see current state: bash scripts/workspace-audit.sh Create the structure: mkdir -p projects/<name>/{references,plans,research,reports} runbooks/ Categorise each file by role (use the decision tree below) Move with git mv to preserve history Add front-matter to moved files Update path references in AGENTS.md, MEMORY.md, and skills Trim MEMORY.md to budget (β€100 lines) Commit atomically
The Role Taxonomy
Every file gets a role β its job title. The role determines where the file lives, how it ages, and how the audit treats it. Read references/roles-guide.md for the full explanation with examples and tests for each role. RoleWhat it meansWhere it livesreferenceFacts about how things are right nowprojects/*/references/planHow you intend to do somethingprojects/*/plans/researchWhat you investigatedprojects/*/research/reportWhat you assessed at a point in timeprojects/*/reports/runbookHow to do something (procedure)runbooks/logWhat happenedmemory/entityStructured facts about a thingmemory/entities/ Quick decision tree: Is it about how things are? β reference. How to change them? β plan. Comparing options? β research. A snapshot assessment? β report. A reusable procedure? β runbook. What happened today? β log. A specific person/server/decision? β entity.
ROLE Front-Matter
Every substantive markdown file gets a YAML header: --- role: reference project: my-project # Omit for cross-project files status: current # active | current | completed | stale | archived created: 2026-02-01 updated: 2026-02-19 summary: "One-line description" --- Status lifecycle: active (being worked on) β current (living document) β stale (needs review) β archived (kept for history)
Directory Layout
workspace/ βββ MEMORY.md # Current state (β€100 lines) β βββ memory/ # Episodic memory β βββ YYYY-MM-DD.md # Daily logs (role: log) β βββ entities/ # People, servers, decisions (role: entity) β βββ projects/ # Project-scoped work β βββ _index.md # Project registry β βββ <name>/ β βββ README.md # Overview + current state β βββ references/ # role: reference β βββ plans/ # role: plan β βββ research/ # role: research β βββ reports/ # role: report β βββ runbooks/ # Cross-project (role: runbook) β βββ policies.md β βββ lessons-learned.md β βββ <domain>/ β βββ skills/ # Procedural memory βββ <skill>/SKILL.md
Where to Write
What you learnedRoleWrite toFact about a projectreferenceprojects/<project>/references/How to fix somethingrunbookrunbooks/lessons-learned.mdOperational procedurerunbookskills/ or runbooks/What happened todaylogmemory/YYYY-MM-DD.mdCurrent state changedβMEMORY.mdPerson/server/decisionentitymemory/entities/Future work planplanprojects/<project>/plans/Research findingsresearchprojects/<project>/research/Audit or reviewreportprojects/<project>/reports/
MEMORY.md Budget
MEMORY.md is loaded every session. Every line costs tokens. Budget: β€100 lines / ~3500 tokens Contains: People, infrastructure, project pointers, lookup table, urgent items Never contains: History, lessons, architecture detail, completed items Over budget? Move detail to project files or runbooks, keep pointers
Configuration
Create .workspace-standard.yml in the workspace root to customise. All values are optional β defaults apply when omitted or when the file doesn't exist. budget: memory_lines: 100 # Max lines for MEMORY.md (default: 100) maintenance: stale_days: 14 # Days before flagging stale (default: 14) projects: subdirs: # Per-project subdirectories (default below) - references - plans - research - reports entities: # Seed files in memory/entities/ (default below) - people - servers - decisions
New Project
./scripts/workspace-init.sh --project my-app Or manually: mkdir -p projects/<name>/{references,plans,research,reports} Create README.md with front-matter Add to projects/_index.md
Migration (flat docs/ β structured)
Create projects/<name>/ and runbooks/ directories Categorise each file by role (use the decision tree above) Move with git mv (preserves history) Add front-matter to moved files Update path references in AGENTS.md, MEMORY.md, skills Trim MEMORY.md to budget Commit atomically
Maintenance
Run scripts/workspace-audit.sh weekly. See references/maintenance-checklist.md for the full procedure. Consolidate daily logs β extract facts to references, lessons to runbooks Prune MEMORY.md β remove resolved items, completed decisions Check front-matter β stale active/current files β verify or update Verify skills catalogue matches actual skills directory Commit maintenance changes
Category context
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
4 Docs2 Scripts
- SKILL.md
- README.md
- references/maintenance-checklist.md
- references/roles-guide.md
- scripts/workspace-audit.sh
- scripts/workspace-init.sh