Hermes Cron Desk
File-bus cron state machine and Hermes profile isolation rules for PumpGrok. Use when installing profiles, running deskstate.py, or deciding which cron may fire.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Hermes Cron Desk when an AI agent needs a reusable SKILL.md workflow for this job: File-bus cron state machine and Hermes profile isolation rules for PumpGrok. Use when installing profiles, running deskstate.py, or deciding which cron may fire.
When not to use it
Skip Hermes Cron Desk when the task is outside the analysis category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/hermes-cron-desk # Save SKILL.md to ~/.claude/skills/hermes-cron-desk/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/hermes-cron-desk/SKILL.md. For a shared project, commit the folder at .claude/skills/hermes-cron-desk/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Hermes Cron Desk skill for this task: Use Hermes Cron Desk when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
69/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 56/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Hermes Cron Desk
## L1 - Summary Isolation rules and the file-bus state machine for Hermes cron profiles. Each role runs in its own profile with no shared memory; the only shared writable surface is the desk directory.
## L2 - Method 1. Isolation: each role is `~/.hermes/profiles/<role>/` (its own HERMES_HOME). Memory, sessions, SOUL, cron, and `.env` do not cross roles. Bootstrap uses `hermes profile create <role> --no-skills` and writes `.no-bundled-skills`. Never `--clone` or `--clone-all`. 2. File bus: ``` $PUMPGROK_DESK/ desk.md engagement plus Halt leads/ SCOUT briefs/ RISK proposals/ CHIEF tickets positions/ SNIPER/EXIT/RUG (paper) journal/ append-only incidents/ RUG watch/ RUG ``` Ticket IDs are unique across every folder. Briefs and proposals reuse the lead ID. 3. Commands (pre-flight first, then the ticket verbs): ```bash pumpgrok state status --seat <role> pumpgrok ticket next pumpgrok ticket create --mint <MINT> --ticket <LEAD-ID> --status PENDING_HUMAN ``` 4. Cron owners: scout-discover, risk-audit-open-leads, chief-pickup, rug-watch-paper, chief-journal-rollup. NEVER cron SNIPER or EXIT. NEVER raise engagement from cron. If Halt is true or engagement is not `research` or `paper`, print `[SILENT]`. 5. Telegram: only the chief profile may hold TELEGRAM_BOT_TOKEN. Other profiles notify via bot-chat:chief or files.
## Failure modes - Halt true or engagement outside `research`/`paper`: the job prints `[SILENT]` and does nothing. - Cross-profile leakage (shared env or memory): refuse the run; isolation is load-bearing. - Cron attempting SNIPER/EXIT or an engagement change: refused by the job and by the CLI.
## References - State tool: `pumpgrok state status --seat <role>` (ledger halt state); `pumpgrok ticket list` (pending tickets) - CLI pre-flight: `pumpgrok state status` - Jobs: `hermes/cron/jobs.yaml`; prompts: `hermes/cron/prompts/`
Intended uses
- Use Hermes Cron Desk when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.