workspace-archiver

name	workspace-archiver
description	Govern OpenClaw workspace document architecture by enforcing executable rules for naming, archive layers, index files, and cross-directory references. Use whenever users ask to organize workspace docs, normalize structure, or align files with OpenClaw conventions.

Workspace Archiver 🗂️

workspace-archiver is an internal documentation-governance skill for OpenClaw.

Scope: enforce documentation structure and naming conventions. Out of scope: package compression, backup archives, restore workflows.

Trigger conditions

Use this skill when the user asks to:

• 整理 OpenClaw 工作区文档结构
• 规范目录命名/归档层级
• 统一索引文件布局
• 修复跨目录引用路径
• 基于 OpenClaw 文档规范更新本地规则

Core contract

This skill must output and apply only these four rule domains:

1. 目录命名规则 (naming)
2. 归档层级规则 (archive layers)
3. 索引文件规则 (index files)
4. 跨目录引用规则 (cross-directory references)

Do not add unrelated features unless explicitly requested.

Execution workflow

Step 1 — Load executable rules

Read:

• rules/openclaw-doc-governance.yaml

This file is the single source of truth for rule enforcement.

Step 2 — Collect workspace evidence

Inspect target scope (usually OpenClaw workspace root) and produce facts:

• existing directory tree
• file naming mismatches
• missing index files
• broken or non-normalized references

Step 3 — Apply rule-driven normalization

Normalize only what is required by rules:

• rename/move non-compliant files and directories
• enforce archive layer placement
• ensure required index files exist in required locations
• rewrite references to canonical relative paths

Step 4 — Docs-RAG coupling refresh (pattern sync)

Refresh the local rule baseline from OpenClaw docs sources on schedule:

• run scripts/sync_rules_from_docs_rag.sh
• update rules/docs-rag-sync.json
• if source guidance changed, update rules/openclaw-doc-governance.yaml

Default cadence: every 14 days (or before major restructuring tasks).

Step 5 — Return compact governance report

Return:

• applied rule IDs
• changed paths
• unresolved conflicts (if any)
• next scheduled Docs-RAG sync date

Ruleset design requirements

When editing rules:

• keep rule IDs stable (N-*, A-*, I-*, R-*)
• keep each rule machine-readable (type, target, matcher, action)
• include rationale and source URL for each rule group

Safety guardrails

• Do not perform destructive deletion by default.
• Prefer move/rename over delete.
• If operation risks losing context, stop and request confirmation.

References

• rules/openclaw-doc-governance.yaml
• rules/docs-rag-sync.json
• scripts/sync_rules_from_docs_rag.sh
• references/openclaw-skill-architecture.md