Menu
Use when adding automation scripts. Requires a caller (CI/cron/hook); watchdog scripts need launchd plist template + deploy.sh install step.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Token-efficient second opinion slash command /advice. Extracts decision point + artifact (≤150 lines), then fans out in parallel: (1) Opus subagent reviewer with fallback chain codex→agy→cursor, (2) /research on the decision topic, (3) /secondo multi-model opinion. Use instead of advisor() which ships the full conversation uncached.
Lazy senior-dev mode — the seven-rung ladder that decides whether to write code at all, whether to reuse code that already exists, and whether to prefer stdlib/platform/installed deps over a new dependency. Use before writing any code, every PR diff, every fix, every feature. Source attribution included.
Use when making any "X is enabled" / "feature X works" / "cache works" claim in a running session — requires runtime probe output from the standard harness startup path, NOT a launchd/cron test that explicitly sets the activation env var.
Pre-flight checklist for self-hosted runner failures. Use when investigating low disk, missing runner, or stuck Green Gate on the jleechanorg/worldarchitect.ai fleet. Always verifies host-level container state, not just GitHub API.
When asked to verify whether a Claude Code feature works (especially slash commands, dialogs, pickers, status indicators), spawn a real interactive TUI session in cmux — never use `claude --print "/feature"` as a test, because --print is non-interactive and will always return "isn't available in this environment" regardless of whether the feature actually works.
Read ~/.hermes/agent-orchestrator.yaml BEFORE declaring an --agent <X> value unsupported. Lists plugin shorthands (wafer, minimax, agy).
| name | automation-completeness |
| description | Use when adding automation scripts. Requires a caller (CI/cron/hook); watchdog scripts need launchd plist template + deploy.sh install step. |
Any PR adding an automation script must also add the trigger. A script with no caller is documentation, not automation.
Red flags (task incomplete if any true): script exists but no CI/cron/hook calls it; only invocation path is manual; PR says "run ./scripts/foo.sh to verify" with no auto-trigger.
Watchdog/monitoring scripts also need: launchd plist committed to repo + deploy.sh step that installs it on every deploy.
