1---2name: hermes-workspace3description: Use when laying out or cleaning the file workspace shared by a Hermes Agent chief and its managers - inbox, dated dossiers (README / received pieces / internal work / deliverables), clients, admin areas, knowledge, automation, archives and a to-delete area awaiting approval, a mirrored private space, scripts kept apart from documents, scratch outside the workspace, file naming, the end-of-task checklist and a weekly cleanup job that only asks before deleting. Not for context-file resolution rules (hermes-core) or sandboxing (hermes-security).4versions:5 hermes-agent: "0.23.0"6user-invocable: false7references:8 - references/layout.md9 - references/naming-scripts-scratch.md10 - references/checklists.md11 - references/templates/hermes-md-filing.md12 - references/templates/dossier-readme.md13 - references/templates/cleanup-job.md14 - references/templates/knowledge-schema.md15related-skills:16 - hermes-core17 - hermes-cron18 - hermes-chief-of-staff19 - hermes-security20 - hermes-rhythm21metadata:22 source: https://skillmd.com/skills/fusengine/hermes-workspace23---2425<objective>26One filing logic for the chief and every agent, written once in the shared27`.hermes.md`: where each kind of document goes, how files are named, where28scripts and temporary files live (never among documents), what every agent29ticks before closing a task, and a weekly cleanup that tidies what is safe30and asks before deleting anything.31</objective>3233# Hermes Workspace3435## Freshness check3637Before writing or changing any Hermes config, run `hermes --version` and38`hermes update --check`, then read39https://github.com/NousResearch/hermes-agent/releases/latest. If the installed40or latest version is newer than 0.23.0, read every release note since 0.23.041("Upgrade notes" first) and adjust. Never apply guidance from this skill to a42newer version without that check.4344## Hermes facts this skill relies on4546| Fact | Consequence | Owner skill |47|------|-------------|-------------|48| `.hermes.md` is found by walking from the working directory up to the git root | Put the filing rules in `.hermes.md` at each workspace root; make that root the git root (or the cwd) of every agent | hermes-core |49| Cron jobs load project context only with `--workdir` | Every workspace job (cleanup, rituals) passes `--workdir <root>` | hermes-cron |50| `terminal.cwd` per profile | Set each profile's cwd inside its own root | hermes-core |51| Kanban `scratch` workspaces are deleted on task completion; `dir:<abs path>` is preserved | Use `dir:` for dossier work, keep temporary files in scratch | hermes-delegation |52| No native "write only here" policy | Containers / `HERMES_WRITE_SAFE_ROOT` + checklist | hermes-security |5354## Decision map5556| Question | Load |57|----------|------|58| Which folder for what, synced chief root, nested `.hermes.md`, company vs private, transition symlinks | [layout.md](references/layout.md) |59| Knowledge base (`SCHEMA.md`, `index.md`, `log.md`) | [templates/knowledge-schema.md](references/templates/knowledge-schema.md) |60| File names, scripts, temporary files | [naming-scripts-scratch.md](references/naming-scripts-scratch.md) |61| End-of-task checklist, weekly cleanup, who keeps order | [checklists.md](references/checklists.md) |62| Filing block for `.hermes.md` (+ company outbound email block) | [templates/hermes-md-filing.md](references/templates/hermes-md-filing.md) |63| Dossier README | [templates/dossier-readme.md](references/templates/dossier-readme.md) |64| Weekly cleanup cron job | [templates/cleanup-job.md](references/templates/cleanup-job.md) |6566## Critical rules67681. **Documents and scripts never mix.** The workspace holds documents; each69 script has its own folder with a README, outside the document roots.702. **Scratch lives outside the workspace** and is disposable.713. **Received pieces are never modified**; work happens in `travail/`72 (internal notes) and `livrables/` (deliverables).734. **Nothing is deleted by an agent.** Candidates go to the to-delete area;74 the owner approves deletion.755. **Doubt about private vs company → ask the chief**, never create a new76 top-level folder.776. **Same rules for every agent**: full reference in the chief root's78 `.hermes.md`, the applicable part repeated in each root's `.hermes.md`.797. **A synced workspace is the owner's view**: no secrets, no scratch, one80 final version per deliverable.818. **Old paths stay as transition symlinks**; nothing new is created under82 them.8384## Sources8586- https://hermes-agent.nousresearch.com/docs/user-guide/features/context-files87- https://hermes-agent.nousresearch.com/docs/user-guide/features/cron (`--workdir`)88- https://hermes-agent.nousresearch.com/docs/user-guide/features/kanban (workspace kinds)89- https://hermes-agent.nousresearch.com/docs/user-guide/configuration (`terminal.cwd`)90- https://hermes-agent.nousresearch.com/docs/user-guide/security (file write safety)