Skill
This is a Hermes-native skill workflow skill.
Why This Exists
skill 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: $skill list installed OMH skills and show the catalog metadata for each workflow.
- Expected behavior: Manage or inspect the skill catalog without claiming runtime execution or external evidence.
- Why: The request is operator skill management, not a user workflow run.
Bad example:
- Prompt: skill: 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
skill.
- 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 for local skill listing, search, add, remove, or edit tasks.
Strong routing signals: `skill`, `$skill`, `skills`, `manage skills`
Catalog Metadata
Category: operator
Phase: skill-management
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:
Use Hermes for inventory and guidance; delegate only repository code changes to the selected coding executor.
Required inputs:
- skill action
- target skill name or directory
Expected outputs:
- skill inventory or mutation result
- verification note
Artifact expectations:
- manifest update when managed skills change
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: docs-specialist.
omh runtime record --skill skill --harness docs-specialist --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-skill"
3description: "[omh] Hermes adaptation for managing local skills. Use when the user says: skill, skills, manage skills."
4metadata:
5 hermes:
6 tags: [workflow, oh-my-hermes, operator]
7 category: operator
8 phase: skill-management
9 role: tracker
10 quality_tier: evidence-gated
11---
12
13# Skill
14
15This is a Hermes-native `skill` workflow skill.
16
17## Why This Exists
18
19`skill` exists to keep `operator` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
20
21## Do Not Use When
22
23- The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
24- The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
25
26## Examples
27
28Good example:
29
30- Prompt: $skill list installed OMH skills and show the catalog metadata for each workflow.
31- Expected behavior: Manage or inspect the skill catalog without claiming runtime execution or external evidence.
32- Why: The request is operator skill management, not a user workflow run.
33
34Bad example:
35
36- Prompt: skill: treat casual chat or unaccepted work as if this workflow already produced verified results.
37- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `skill`.
38- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
39
40## Completion Checklist
41
42- The local command, managed path, config surface, and state artifact inspected are named.
43- Blocking issues, warnings, and optional surfaces are separated.
44- The next repair action is explicit and does not claim a reload or runtime observation.
45
46## Recovery Notes
47
48- If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
49- If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.
50
51## Workflow Lane
52
53- 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.
54- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
55- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
56
57## Use When
58
59Use for local skill listing, search, add, remove, or edit tasks.
60
61 Strong routing signals: `skill`, `$skill`, `skills`, `manage skills`
62
63## Catalog Metadata
64
65Category: `operator`
66Phase: `skill-management`
67Hermes role: `tracker`
68Quality tier: `evidence-gated`
69Reasoning demand: `light`
70
71Quality bar:
72
73- Name the workflow target, constraints, validation evidence, and stop condition.
74- Separate Hermes guidance from executor or wrapper behavior unless evidence proves the step happened.
75
76Handoff policy:
77
78Use Hermes for inventory and guidance; delegate only repository code changes to the selected coding executor.
79
80Required inputs:
81
82- skill action
83- target skill name or directory
84
85Expected outputs:
86
87- skill inventory or mutation result
88- verification note
89
90Artifact expectations:
91
92- manifest update when managed skills change
93
94Safety rules:
95
96- Do not imply hidden Hermes runtime behavior.
97- Use the smallest verification that can prove the claim.
98
99## Runtime Evidence
100
101Preferred harness for this skill: `docs-specialist`.
102
103```sh
104omh runtime record --skill skill --harness docs-specialist --status started
105```
106
107Record observed delegation results; otherwise return `not_available` or `not_observed`.
108Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
109- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
110Preserve workflow intent and stop conditions; verify before claiming completion.
111
112Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
113
114Shared 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