automation-blueprint
starsforks
How to install automation-blueprint?
rlaope/oh-my-hermes/automation-blueprint
$npx -y skills add rlaope/oh-my-hermes --skill automation-blueprint[omh] Hermes Scheduled Ops Blueprint workflow: design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status.
SKILL.md
| 1 | # Automation Blueprint |
| 2 | |
| 3 | This is a Hermes-native `automation-blueprint` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `automation-blueprint` exists so Hermes can make recurring operational work feel native and scheduled without OMH becoming a hidden cron runner, transport bot, source retriever, or executor. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The user needs a one-off report or deck; use `report-package` or `materials-package`. |
| 12 | - The user asks to review incident metrics once; use `reliability-review`. |
| 13 | - The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: automation-blueprint every weekday run an uptime check and send a Slack digest only if status changes. |
| 20 | - Expected behavior: Prepare hermes_ops_blueprint/v1 with schedule intent, Slack delivery policy, silence rule, research/report skills, missing evidence, and next confirmation. |
| 21 | - Why: The request is recurring, delivery-shaped, and must stay prepared until host automation and gateway delivery are observed. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: automation-blueprint prove the Slack digest was delivered this morning. |
| 26 | - Expected behavior: Ask for observed Hermes/gateway delivery evidence or report the delivery as not_observed instead of claiming it happened. |
| 27 | - Why: A blueprint can prepare the scheduled operation, but it cannot prove runtime execution or delivery. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Confirm the workflow target, evidence boundary, and stop condition are named. |
| 32 | - Report which outputs are prepared, observed, blocked, or missing. |
| 33 | - Name the smallest next verification or handoff instead of claiming completion from narration. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If required context is missing, ask one blocking question or route back to the narrower workflow. |
| 38 | - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when Hermes should turn a natural recurring/cron-like request into a scheduled ops blueprint without claiming host automation, platform delivery, source retrieval, or no-agent execution. |
| 55 | |
| 56 | Strong routing signals: `automation-blueprint`, `scheduled ops`, `scheduled operation`, `scheduled operations`, `automation blueprint`, `cron blueprint`, `cron-ready`, `recurring ops`, `recurring workflow`, `every morning`, `every day`, `daily digest`, `weekly digest`, `automate this`, `automate workflow`, `send to slack`, `send to discord`, `post to telegram`, `only if changed`, `silent if nothing changed`, `schedule this`, `매일`, `매주`, `정기`, `예약`, `반복`, `자동화`, `자동화해줘`, `스케줄`, `슬랙`, `디스코드`, `텔레그램`, `보내`, `공유`, `변화 없으면`, `조용히` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `operations` |
| 61 | Phase: `scheduled-ops-blueprint` |
| 62 | Hermes role: `operator` |
| 63 | Quality tier: `ops-blueprint-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name cadence/timezone uncertainty, delivery target, silence/no-change rule, selected skills, and context chain. |
| 68 | - Expose whether a no-agent watchdog is a candidate without claiming it exists or ran. |
| 69 | - List host automation, gateway delivery, source retrieval, and no-agent execution as not evidence until observed. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep schedule intent, delivery policy, silence rules, context-chai |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
