cancel
starsforks
How to install cancel?
rlaope/oh-my-hermes/cancel
$npx -y skills add rlaope/oh-my-hermes --skill cancel[omh] Hermes adaptation for ending active workflow state cleanly.
SKILL.md
| 1 | # Cancel |
| 2 | |
| 3 | This is a Hermes-native `cancel` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `cancel` exists to keep `operator` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. |
| 12 | - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. |
| 13 | |
| 14 | ## Examples |
| 15 | |
| 16 | Good example: |
| 17 | |
| 18 | - Prompt: cancel: handle a operator request that needs explicit evidence boundaries and a clear stop condition. |
| 19 | - Expected behavior: Run `cancel` only after naming the target, evidence boundary, and stop condition. |
| 20 | - Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: cancel: treat casual chat or unaccepted work as if this workflow already produced verified results. |
| 25 | - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `cancel`. |
| 26 | - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. |
| 27 | |
| 28 | ## Completion Checklist |
| 29 | |
| 30 | - The local command, managed path, config surface, and state artifact inspected are named. |
| 31 | - Blocking issues, warnings, and optional surfaces are separated. |
| 32 | - The next repair action is explicit and does not claim a reload or runtime observation. |
| 33 | |
| 34 | ## Recovery Notes |
| 35 | |
| 36 | - If a managed path or config key is missing, route to setup/update repair instead of editing hidden state. |
| 37 | - If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only. |
| 38 | |
| 39 | ## OMH Context Rail |
| 40 | |
| 41 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 42 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 43 | - 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. |
| 44 | - 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. |
| 45 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 46 | - 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. |
| 47 | - Coverage: Every generated workflow skill carries this rail. |
| 48 | - Normal users talk to Hermes; OMH CLI is infra. |
| 49 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 50 | |
| 51 | ## Use When |
| 52 | |
| 53 | Use to cleanly end active adapted workflow state. |
| 54 | |
| 55 | Strong routing signals: `cancel`, `$cancel`, `stop`, `abort` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `operator` |
| 60 | Phase: `state-cleanup` |
| 61 | Hermes role: `tracker` |
| 62 | Quality tier: `evidence-gated` |
| 63 | |
| 64 | Quality 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 | |
| 69 | Handoff policy: |
| 70 | |
| 71 | Run directly in Hermes/runtime state; never delegate cancellation to a coding executor. |
| 72 | |
| 73 | Required inputs: |
| 74 | |
| 75 | - active workflow state |
| 76 | - cancellation intent |
| 77 | |
| 78 | Expected outputs: |
| 79 | |
| 80 | - cleared state |
| 81 | - safe stop summary |
| 82 | |
| 83 | Artifact expectations: |
| 84 | |
| 85 | - state clear record when state exists |
| 86 | |
| 87 | Safety rules: |
| 88 | |
| 89 | - Do not imply hidden Hermes runtime behavior. |
| 90 | - Use the smallest verification that can prove the claim. |
| 91 | |
| 92 | ## Harness Discipline |
| 93 | |
| 94 | - Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes. |
| 95 | - Prefer richer evidence and clearer stop conditions over adding more workflow names. |
| 96 | - Use specialist lanes only when they change the quality of the answer or verification. |
| 97 | |
| 98 | ## Runtime Evidence |
| 99 | |
| 100 | Preferred harness for this skill: `goal-execution`. |
| 101 | |
| 102 | When local shell access or a bot wrapper is available, record metadata-only evidence: |
| 103 | |
| 104 | ```sh |
| 105 | omh runtime record --skill cancel --harness goal-execution --status started |
| 106 | omh runtime delegate --run <run-id> --requested --not-observed --result not_observed |
| 107 | ``` |
| 108 | |
| 109 | Record observed delegation results when Hermes or the wrapper exposes them. If dele |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
