Shared operating rules for the OpenClaw 100k Posts system. Defines the workspace contract, what files each skill can read or write, and how artifacts move from research to analysis to concept generation to delivery.
This skill is the shared system layer for this repo.
It exists to keep the other skills aligned around one runtime contract:
All persistent state lives under ~/clawd/workspace/.
~/clawd/workspace/brand/voice-profile.md~/clawd/workspace/brand/notes.md~/clawd/workspace/content-radar/config.yaml~/clawd/workspace/content-radar/briefings/~/clawd/workspace/content-dna/outputs/~/clawd/workspace/content-dna-batch/dna-cache/~/clawd/workspace/content-dna-batch/reports/~/clawd/workspace/the-forge/outputs/~/clawd/workspace/monday-drop/outputs/voice-lab owns voice-profile.md.voice-lab may append useful discoveries to notes.md.content-radar owns briefing files in content-radar/briefings/.content-dna owns single-video analysis files.content-dna-batch owns pattern reports and DNA cache.the-forge owns forged concept output.monday-drop owns delivery logs and exported run summaries.voice-lab may read any file in workspace/brand/.content-radar should only read config.yaml.content-dna should read voice-profile.md only when adapting concepts.content-dna-batch should read Content DNA outputs and its own cache.the-forge should read voice-profile.md, pattern reports, and optionally the latest content-radar briefing.monday-drop should read config, reports, and forged outputs. It should not invent missing brand state.voice-profile.md without showing the user what will change.notes.md is append-only.voice-profile.md exists, skills may fall back to the demo voice where supported.