Cancel
This is a Hermes-native cancel workflow skill.
Why This Exists
cancel exists to keep operator work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
Do Not Use When
- The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
- The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
Examples
Good example:
- Prompt: cancel: handle a operator request that needs explicit evidence boundaries and a clear stop condition.
- Expected behavior: Run
cancel only after naming the target, evidence boundary, and stop condition.
- Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance.
Bad example:
- Prompt: cancel: treat casual chat or unaccepted work as if this workflow already produced verified results.
- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing
cancel.
- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
Completion Checklist
- The local command, managed path, config surface, and state artifact inspected are named.
- Blocking issues, warnings, and optional surfaces are separated.
- The next repair action is explicit and does not claim a reload or runtime observation.
Recovery Notes
- If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
- If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.
Workflow Lane
- Current lane: Automation and status (
achievements, workspace-audit, production-audit, automation-blueprint, github-event-ops, github-issue-intake, buzz, agent-board, +35 more) - schedules, status, health, and ops review.
- If intent belongs to another lane, hand back to
oh-my-hermes or name the adjacent workflow.
- Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use to cleanly end active adapted workflow state.
Strong routing signals: `cancel`, `$cancel`, `stop the workflow`, `abort the run`, `cancel the loop`
Catalog Metadata
Category: operator
Phase: state-cleanup
Hermes role: tracker
Quality tier: evidence-gated
Reasoning demand: light
Quality bar:
- Name the workflow target, constraints, validation evidence, and stop condition.
- Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.
Handoff policy:
Run directly in Hermes/runtime state; never delegate cancellation to a coding executor.
Required inputs:
- active workflow state
- cancellation intent
Expected outputs:
- cleared state
- safe stop summary
Artifact expectations:
- state clear record when state exists
Safety rules:
- Do not imply hidden Hermes runtime behavior.
- Use the smallest verification that can prove the claim.
Runtime Evidence
Preferred harness for this skill: goal-execution.
omh runtime record --skill cancel --harness goal-execution --status started
Record observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
Preserve workflow intent and stop conditions; verify before claiming completion.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---2name: omh-cancel3description: [omh] Hermes adaptation for ending active workflow state cleanly. Use when the user says: cancel, stop the workflow, abort the run, cancel the loop.4---5
6# Cancel
7
8This is a Hermes-native `cancel` workflow skill.
9
10## Why This Exists
11
12`cancel` exists to keep `operator` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
13
14## Do Not Use When
15
16- The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
17- The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
18
19## Examples
20
21Good example:
22
23- Prompt: cancel: handle a operator request that needs explicit evidence boundaries and a clear stop condition.
24- Expected behavior: Run `cancel` only after naming the target, evidence boundary, and stop condition.
25- Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance.
26
27Bad example:
28
29- Prompt: cancel: treat casual chat or unaccepted work as if this workflow already produced verified results.
30- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `cancel`.
31- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
32
33## Completion Checklist
34
35- The local command, managed path, config surface, and state artifact inspected are named.
36- Blocking issues, warnings, and optional surfaces are separated.
37- The next repair action is explicit and does not claim a reload or runtime observation.
38
39## Recovery Notes
40
41- If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
42- If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.
43
44## Workflow Lane
45
46- Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `github-issue-intake`, `buzz`, `agent-board`, `+35 more`) - schedules, status, health, and ops review.
47- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
48- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
49
50## Use When
51
52Use to cleanly end active adapted workflow state.
53
54 Strong routing signals: `cancel`, `$cancel`, `stop the workflow`, `abort the run`, `cancel the loop`
55
56## Catalog Metadata
57
58Category: `operator`
59Phase: `state-cleanup`
60Hermes role: `tracker`
61Quality tier: `evidence-gated`
62Reasoning demand: `light`
63
64Quality bar:
65
66- Name the workflow target, constraints, validation evidence, and stop condition.
67- Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.
68
69Handoff policy:
70
71Run directly in Hermes/runtime state; never delegate cancellation to a coding executor.
72
73Required inputs:
74
75- active workflow state
76- cancellation intent
77
78Expected outputs:
79
80- cleared state
81- safe stop summary
82
83Artifact expectations:
84
85- state clear record when state exists
86
87Safety rules:
88
89- Do not imply hidden Hermes runtime behavior.
90- Use the smallest verification that can prove the claim.
91
92## Runtime Evidence
93
94Preferred harness for this skill: `goal-execution`.
95
96```sh
97omh runtime record --skill cancel --harness goal-execution --status started
98```
99
100Record observed delegation results; otherwise return `not_available` or `not_observed`.
101Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
102- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
103Preserve workflow intent and stop conditions; verify before claiming completion.
104
105Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
106
107Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope