#277 by GitHub stars
rlaope/oh-my-hermes
⚚ The coding harness with Hermes Agent wired into IDE.
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
agent-skills/omh-accessibility-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-adversarial-consensus/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-agent-debug/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-agent-instructions/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-agent-ops-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-ai-job-search/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-ai-slop-cleaner/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-app-debugging/SKILL.md
Week of Nov 2, 2026 · +11 / −5 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-apple-design/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-application-threat-model/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-apps/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-ask/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-award-bar-score/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-backend/SKILL.md
Week of Nov 2, 2026 · +5 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-biomedical-evidence/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-build-failure-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-cancel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-code-review/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-codebase-onboarding/SKILL.md
Week of Nov 2, 2026 · +10 / −5 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-codebase-uml/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-codegraph-refresh/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-commit-pr-authoring/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-content-operator/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-context-budget-review/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-cto-loop/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-curriculum-design/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-data-analysis/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-data-pipelines/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-data-share-review/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-decide/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-decision-prototype/SKILL.md
Week of Nov 2, 2026 · +2 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-decision-recall/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-deliverable-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-deploy-and-monitor/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-design-orchestration/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-design-quality-gate/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-docs/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-external-connector-readiness/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-failure-signal-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-feedback-triage/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-files/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-finance-analysis/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-frontend/SKILL.md
Week of Nov 2, 2026 · +8 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-frontend-refactor/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-geospatial-analysis/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-git-workflow/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-github-event-ops/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-github-issue-intake/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-harness-session-inventory/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-iac-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-idea-to-deploy/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-image-cards/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-inference-serving/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-instinct-ledger/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-internal-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-jit-learn/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-legal-compliance-review/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-lifecycle-growth/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-live-incident-response/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-live-info/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-llm-app-dev/SKILL.md
Week of Nov 2, 2026 · +5 / −4 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-localization-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-market-research/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-materials-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-media-input/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-meeting-brief/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-memory-new/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-mobile-release/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-model-finetuning/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-molecular-docking/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-native-debugging/SKILL.md
Week of Nov 2, 2026 · +2 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-operating-rhythm/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-ops-observability-card/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-ops-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-paper-learning/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-people-ops/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-physical-device-readiness/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-plan/SKILL.md
Week of Nov 2, 2026 · +9 / −4 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-product-brief/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-product-discovery-validation/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-production-audit/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-provider-profile-posture/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-refactor-plan/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-relational-db/SKILL.md
Week of Nov 2, 2026 · +2 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-release-cut/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-reliability-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-report-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-repro-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-research-brief/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-rules-distill/SKILL.md
Week of Nov 2, 2026 · +9 / −7 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-run-efficiency/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-running-work-board/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-rust/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-sales-development/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-sales-pipeline-review/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-security-event-response/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-security-safety-review/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-show-reel/SKILL.md
Week of Nov 2, 2026 · +1 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-skill-health/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-skill-scout/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-source-finder/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-spend-gate/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-sprite-forge/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-support-operations/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-systematic-review/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 98284f305f6a
No earlier version was observed for comparison.
agent-skills/omh-tech-debt-audit/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-terminal/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-toolbelt-readiness/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-verification-gate/SKILL.md
Week of Nov 2, 2026 · +5 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-visual-qa/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-voice-input/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-web-research/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-wiki/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/omh-workspace-audit/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-context/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 60 - If the user moves from terminology to implementation, summarize confirmed understanding and hand off to `ralplan`, `ulw-plan`, or the selected coding owner only after a separate go-ahead.
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-interview/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-loop/SKILL.md
Week of Nov 2, 2026 · +1 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-perf/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-plan/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 65 - If current-source evidence is missing, route a `research` step before accepting the plan.
This preview is limited. See the complete change on GitHub.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-qa/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 49 - If the expected behavior is unclear, route back to plan before running adversarial checks.
- 50 - If verification fails, return to fix or research with the failed signal instead of advancing.
+ 49 - If a scenario needs a real install or external service the harness cannot reach, retain other observed pass/fail evidence, mark that scenario not_observed, and hand back its manual test guide with setup, do, expect, and broken signals.
+ 50 - If a hostile browser scenario would submit, buy, send, or delete on a live target without approval, retain read-only scenario results, mark that action not_observed, and hand back the target and exact action for user approval.
+ 51 - If a failing browser scenario has no screenshot or console readback, keep its observed failure, mark diagnosis tentative, and hand back the scenario, target, and missing capture for a bounded rerun.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-research/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 93 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`). Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. Use parent-only serialized writes: lanes return observed source entries and quote refs; the parent registers URLs, attaches quotes, and remaps lane ids before drafting. Lanes never write the shared ledger. When a human briefing is written, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`. It is a citation check, not fact verification, and it never stands in for the contested-claim gate. Without the skill, keep each source's URL and retrieval date in the research notes and report the citation check as `not_observed`.
+ 93 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`). Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. Use parent-only serialized writes: lanes return observed source entries and quote refs; the parent registers URLs, attaches quotes, and remaps lane ids before drafting. Lanes never write the shared ledger. When a human briefing is written, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`. It is a citation check, not fact verification, and it never stands in for the contested-claim gate. After that verify, run `omh research receipts verify --citations <ledger> --draft <draft>` and report its fetched coverage from the run, or as `not_observed`; a receipt proves only that the page was opened in this session tree, never that it supports the claim. Without the skill, keep each source's URL and retrieval date in the research notes and report the citation check as `not_observed`.
- 96 - Decompose the question into orthogonal research axes and disambiguate named entities before any deep reading.
+ 96 - Decompose the question into orthogonal research axes and disambiguate named entities before any deep reading. Before answering from a source, confirm it studies the exact entity the question names; a different name is a different entity unless a source says they are the same, so a source on a related one is a lead, not an answer.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
agent-skills/ulw-work/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/dag-ulw/SKILL.md
Week of Nov 2, 2026 · +7 / −5 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 27 - Plan the graph and call `omh_dag action=define` with the complete run `goal` and each node's id, label, category, prompt, depends_on and write_scope; fix every refusal and read the lint before going on. Never `delegate_task` before `define` returns its calls. The saved goal reaches every native task; local VERIFY does not replace goal acceptance.
+ 27 - When the conversation holds a plan the user accepted (from `plan`, `ralplan` or `refactor-plan`), build the graph from it instead of re-planning: each task becomes a node with its id, depends_on and write scope, its done check goes into VERIFY and STOP WHEN, and its closing verification task becomes the `role: verify` node; plan only what it leaves open.
+ 28 - Plan the graph and call `omh_dag action=define` with the complete run `goal` and each node's id, label, category, prompt, depends_on, write_scope and role (`build` by default; `baseline`, `verify`, `review`); fix every refusal and read the lint before going on. Never `delegate_task` before `define` returns its calls. The saved goal reaches every native task; local VERIFY does not replace goal acceptance.
- 91 - Climb the difficulty ladder `quick` -> `unspecified-low` -> `unspecified-high` with a one-line reason per climb; use `ultrabrain` at most once, and a graph whose every node is `deep` or `deep-work` is a routing failure.
+ 92 - Climb the difficulty ladder `quick` -> `unspecified-low` -> `unspecified-high` with a one-line reason per climb; use `ultrabrain` at most once, and a graph whose every node is `deep` or `deep-work` is a routing failure. A `role=review` node takes category `review` where your routes serve it; a `role=baseline` node stays `quick` or `unspecified-low`; a `role=verify` node judges the run goal and baseline exemptions, so climb the ladder for it as for any judgement.
- 95 - End every run with a verification node that depends on every producer, runs the real command, and is never the node that built the work.
- 96 - Completion is a claim: before reporting the goal met, check each node against its SCOPE in both directions, nothing owed missing and nothing beyond it done.
- 97 - Goal loop: verify, repair, extend, verify. A failed check gets repair nodes (`omh_dag action=repair`, two cycles per node); when every node passed but the goal check finds work missing, add it to the same run (`omh_dag action=extend`, two rounds per run). Past either limit, report what is still open.
+ 96 - End every run with a `role: verify` node that depends on every producer, runs the real command, and is never the node that built the work.
+ 97 - Completion is a claim: report the goal met only when `omh_dag` says `verdict: verified`, and first check each node against its SCOPE in both directions, nothing owed missing and nothing beyond it done.
+ 98 - Goal loop: verify, repair, extend, verify. A failed check gets repair nodes (`omh_dag action=repair`, two cycles per node, the last re-plans); when every node passed but the goal check finds work missing, add it to the same run (`omh_dag action=extend`, two rounds per run). Past either limit, report what is still open.
+ 99 - Unknown path: scout first; see 'When the path is unknown' in `references/run-loop.md`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-accessibility-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-achievements/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 51 - If provider metrics are unavailable, report only local metadata and mark provider truth not_observed.
- 52 - If cost or latency looks risky, surface a warning plus the next measurement rather than a completion claim.
+ 51 - If neither active-profile nor legacy hermes-achievements files are available, no badge result stands; mark the summary not_observed and hand back the missing local-file evidence needed for hermes_achievements_observation/v1.
+ 52 - If the snapshot is older than the plugin's rescan window, retain its badge list as of generated_at, mark current progress tentative, and hand back the timestamp and stale-snapshot warning.
+ 53 - If supplied session_activity_receipt/v1 lacks a metric, retain the available badge and activity metadata, mark that metric not_observed, and hand back the gap without replacing it with zero.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-adversarial-consensus/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 57 - If the proposal under review cannot be stated in one paragraph, route back to `deep-interview` before opening round one.
+ 57 - If the proposal under review cannot be stated in one paragraph, route back to `ulw-interview` before opening round one.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-agent-board/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-agent-debug/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 107 - agent_debug_report/v1 from `omh quality-evidence agent-debug --hermes-session <id|latest> --observable <kind> --json` (or `--session-record <jsonl>`, `--turns N:M`): tool errors, identical retries after an error, background processes started without notify_on_complete, and compaction boundaries, each cited by session and message id or record line; treat a kind listed unavailable as unchecked
+ 107 - agent_debug_report/v1 from `omh quality-evidence agent-debug --hermes-session <id|latest> --observable <kind> --json` (or `--session-record <jsonl>`, `--turns N:M`): tool errors, identical retries after an error, background processes started without notify_on_complete, compaction boundaries, and silent turn ends (an empty assistant row right after a tool result that ended the turn), each cited by session and message id or record line; treat a kind listed unavailable as unchecked, and when a silent turn end leads, read the host's agent.log `Turn ended: reason=` line for its timestamp before changing anything
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-agent-evaluation/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 54 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 53 - If observed_at lacks receipt-authenticated provenance, retain the task set, rubric, and input digests, mark the comparison not_observed, and hand back paired_run_decision/v1 with the provenance gap rather than a pass or fail.
+ 54 - If candidate inputs or success criteria differ outside the variable under test, retain the observed runs, mark executor selection tentative, and hand back the mismatched digests or criteria and a matched rerun budget.
+ 55 - If a judge has no measured agreement against human labels, retain the prewritten rubric and observed executable checks, mark judgment unresolved and unqualified, and hand back the missing agreement measurements instead of a correctness claim.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-agent-instructions/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-agent-ops-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If a managed path or config key is missing, route to setup/update repair instead of editing hidden state.
- 52 - If a reload or plugin load was not observed, keep the diagnostic result as local health evidence only.
+ 51 - If only a prepared handoff exists, mark coding progress not_observed; hand back the missing stage.
+ 52 - If P0 capture fails its audit, keep the tier checks, mark readiness unresolved; hand back quick wins.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-ai-job-search/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
- 69 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 69 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-ai-slop-cleaner/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 55 - If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying.
- 56 - If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action.
+ 55 - If baseline regression checks cannot run, retain the categorized smell inventory, mark the behavior lock unresolved, and hand back the cleanup plan and missing before-checks without starting risky edits.
+ 56 - If verification fails between single-smell passes, retain the last verified pass's evidence, mark the new pass unresolved, and hand back its small diff and failed check for a fix or revert before the next pass.
+ 57 - If the cleanup has no runtime record, retain its observed diff and before/after checks, mark the cleaner run not_observed, and hand back the four-part closing report for recording before an AC-SLOP checkpoint.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-app-debugging/SKILL.md
Week of Nov 2, 2026 · +11 / −5 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 57 - The fix handoff carries the reproduction as a regression test that fails before and passes after.
+ 57 - The fix handoff carries the reproduction as a regression test that fails before and passes after, or records `regression_seam: none_correct` with the reason, with the reproduction loop observed red before the fix and green after it.
+ 58 - An observed search for the session's probe tag returns nothing, and every throwaway harness file is deleted or listed.
- 61 - If the fault does not reproduce, make reproduction the first hypothesis and plan the loop, seed, or ordering that would establish it.
+ 62 - If the fault does not reproduce, make reproduction the first hypothesis and plan the loop, seed, or ordering that would establish it; when no test reaches the fault, choose a loop from the method reference's loop table; if none can be built, the record stays not_observed with each attempt and what stopped it, and the request to the user is for an environment, a redacted capture, or permission for tagged temporary instrumentation.
+ 89 - A reproduction counts for this bug only when its `symptom_match` shows the failure the user reported; a different failure near the same code is another bug, and this record stays not_observed.
+ 90 - `minimised` is filled before `competing_hypotheses/v1`: an input, caller, config value, or step leaves the reproduction only when the loop rerun without it still shows the symptom (for an intermittent fault, the same rate at the same N), and the record lists what left and what stayed; `fix_handoff/v1` builds the regression test from what stayed.
+ 95 - Before the fix handoff names a regression test, load `skill_view(name='omh-verification-gate', file_path='references/test-authoring.md')` for the seam, the shapes of tests that guard nothing, fakes only at system boundaries, and the no-correct-seam outcome.
- 117 - reproduction_record/v1 names the exact command, the input, the observed output, the expected output, and the hit rate over N runs; it reads observed or not_observed and nothing between
+ 121 - reproduction_record/v1 names the exact command, the input, the observed output, the expected output, and the hit rate over N runs, plus `symptom_match` (the observed failure quoted beside the reported one), `loop_cost` (wall time per run, and what was pinned or, for an intermittent fault, how the rate was raised), and `minimised` (the cuts made and the load-bearing form left); it reads observed or not_observed and nothing between
- 120 - root_cause_record/v1 cites the observation that demonstrated the cause and the one that ruled out each rival
- 121 - fix_handoff/v1 carries the reproduction as the regression test that must fail before the fix and pass after it
+ 124 - root_cause_record/v1 cites the observation that demonstrated the cause and the one that ruled out each rival, and the fix's commit or pull-request body states that confirmed hypothesis and the rivals it eliminated, because the next debugger reads history, not this record
+ 125 - fix_handoff/v1 carries the reproduction as the regression test that must fail before the fix and pass after it, or records `regression_seam: none_correct` with the reason, with the reproduction loop observed red before the fix and green after it
+ 126 - fix_handoff/v1 names the seam the regression test drives and how it runs the pattern that produced the bug (callers, ordering, call chain); when the pattern cannot run at any reachable seam, it records `regression_seam: none_correct` with the reason and what was tried, keeps the reproduction loop as the fix's verification, and reports the missing seam as an `omh-refactor-plan` candidate instead of a shallow test that passes before and after the fix
+ 135 - Redact before recording: reproduction commands read credentials from environment variables by name, quoted output keeps only the lines that carry the signal with each secret replaced by `<redacted>`, and a capture too redacted to diagnose is reported as such, never recorded unredacted.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-apple-design/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-application-threat-model/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 59 - If the request turns out to be about the agent's own prompts, tools, or credentials, stop and hand it to `security-safety-review`.
+ 59 - If the request turns out to be about the agent's own prompts, tools, or credentials, stop and hand it to `omh-security-safety-review`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-apps/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-ask/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If the reviewed target is missing, inspect the requested artifact or ask one target question.
- 53 - If independent verification is unavailable, report the gap and avoid an approval-style claim.
+ 52 - If no advisor is configured, retain the question and context summary, mark external advice not_observed, and hand back the agent's own answer without choosing a default advisor.
+ 53 - If the named advisor returns no response, retain the prepared advisor prompt, mark external advice not_observed, and hand back the question and context summary for a later consultation.
+ 54 - If advisor claims lack file, artifact, command, or source evidence, retain the captured advice as advice only, mark those conclusions tentative, and hand back accepted/rejected points and unresolved questions in the decision note.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-automation-blueprint/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 55 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 56 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 55 - If a stop condition is missing, retain the recurring request and cadence, mark the choice among cron, heartbeat, loop, and native goal unresolved, and hand back recurring_surface_comparison/v1 with the stop-condition question.
+ 56 - If overlap, missed-run, retry, backfill, or failure-pause decisions remain open, retain prepared_native_blueprint/v1, mark activation unresolved, and hand back the missing policy choices and native-runtime limits before activation.
+ 57 - If no run reference exists for the saved intent revision, retain hermes_recurring_intent/v1, mark execution and delivery not_observed, and hand back `hermes cron runs` and `hermes cron incidents` as the next status checks.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-award-bar-score/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-backend/SKILL.md
Week of Nov 2, 2026 · +5 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 90 - Name the guard on every write two requests can reach at once — a unique constraint, a stored idempotency key, a lost-update guard — and send side effects only after commit; the pagination-cursor, integrity, timeout, and cache rules are in sections 4 to 6 of the service-contract reference.
+ 91 - When the surface receives webhooks, consumes a queue, or sizes a connection pool, load `references/inbound-and-async.md`: verify a webhook over its raw body before parsing, and treat every queued message as one that can arrive more than once.
+ 93 - When the handoff asks for tests, load `references/contract-tests.md` and derive the test plan in backend_implementation_handoff/v1 from the contract: one negative test per auth_boundary_map/v1 row, one per error_path_table/v1 row, stand-ins chosen by dependency category with the same database engine, and migrations run on populated data.
- 120 - backend_service_contract/v1 names each endpoint or job, its caller class, request and response shapes, and its idempotency and pagination rules
+ 123 - backend_service_contract/v1 names each endpoint or job, its caller class, request and response shapes, its idempotency and pagination rules, and its expected rate, latency target, and payload bound (or `unknown`)
+ 136 - Treat an inbound webhook handler that does not verify the signature over the raw body before parsing as a blocker, not a follow-up.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-biomedical-evidence/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
- 70 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 70 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-browser/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-build-failure-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-buzz/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-cancel/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-capability-toggle/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-code-review/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 63 - For maintainability judgement calls, load `omh-code-review/references/smell-baseline.md`; it names the twelve baseline smells with their fixes and the repo-standards-override rule.
+ 63 - For maintainability judgement calls, load `omh-code-review/references/smell-baseline.md`; it finds the repository's standards files first, then names the twelve baseline smells with their fixes and the repo-standards-override rule.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-codebase-onboarding/SKILL.md
Week of Nov 2, 2026 · +10 / −5 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 46 - The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
- 47 - Draft recommendations, accepted decisions, and executor handoffs are separate states.
- 48 - Rejected options or unresolved tradeoffs are recorded before handoff.
+ 46 - repo_map/v1 cites an observed path for every directory, entrypoint, generated surface, and test location it names; what was inferred is marked inferred, and what was never opened is listed as unread.
+ 47 - reading_path/v1 is an ordered list of real files, each with why it comes at that point and what the reader knows after it.
+ 48 - Every domain_glossary/v1 term points to where it is defined or used; a term with no source is an open question, not an entry.
+ 49 - risk_and_unknowns_map/v1 keeps observed risks, each with the file or command that shows it, apart from unknowns, each with how it would be resolved.
+ 50 - Every first_task_runway/v1 task names the files it touches and its verification command, and says whether that command was run during onboarding.
+ 51 - The stop condition named at the start is met, or the reply names what was left unread.
- 52 - If acceptance criteria or verification are missing, route back to clarification before handoff.
- 53 - If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.
+ 55 - If the repository is too large for the stated depth, narrow to the entrypoint the audience touches first and record the rest as unread rather than summarizing it from file names.
+ 56 - If a build, test, or setup command could not run (read-only mode, missing toolchain, secrets), list it in first_task_runway/v1 as not run with the reason, never as a known-good command. A command that installs or syncs dependencies as a side effect (`npm ci`, `uv sync`, and `uv run`, which syncs first) counts as setup and stays not run.
+ 57 - If docs and code disagree, report what the code does, cite both, and add the disagreement to risk_and_unknowns_map/v1 instead of trusting the docs.
+ 58 - If the user names a concrete task mid-tour, stop at the current reading_path/v1 entry and hand the runway so far to `omh-plan`, or to `ulw-work` or `omh-idea-to-deploy` when the task already has acceptance criteria.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-codebase-uml/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-codegraph-refresh/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-commit-pr-authoring/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-content-operator/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-context-budget-review/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If provider metrics are unavailable, report only local metadata and mark provider truth not_observed.
- 53 - If cost or latency looks risky, surface a warning plus the next measurement rather than a completion claim.
+ 52 - If the previous must-keep pack has no item classes, retain its recorded contents, mark the class delta unresolved, and hand back must_keep_item_class_delta/v1 as comparison unavailable, never as zero items.
+ 53 - If a checkpoint is due but no Hermes /compress reply is observed, retain the must-keep context pack and checkpoint plan, mark compaction not_observed, and hand back /compress <focus> with the reply needed to verify continuity.
+ 54 - If the session has no published context_budget_plan/v1, retain the proposed budget plan, mark inherited capacity unresolved, and hand back the capacity_unknown_hold and session reference for publication or rebinding.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-cto-loop/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 50 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 51 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 50 - If operating signals do not support an architecture tradeoff, retain the cited signals, mark that tradeoff tentative, and hand back the decision note with assumptions and delivery risks.
+ 51 - If the decision owner has not accepted implementation follow-ups, retain the priority frame and risk ranking, mark follow-up authority unresolved, and hand back the decision note and handoff candidates for acceptance.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-curriculum-design/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If acceptance criteria or verification are missing, route back to clarification before handoff.
- 54 - If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.
+ 53 - If an outcome lacks acceptable assessment evidence, retain curriculum_learner_outcome_brief/v1, mark curriculum_alignment_map/v1 tentative, and hand back the orphan outcomes or assessment mismatches for revision.
+ 54 - If an access or technology barrier has no equivalent demonstration path, retain the aligned outcomes and assessments, mark curriculum_sequence_design/v1 unresolved, and hand back the barrier and required adaptation.
+ 55 - If learner review or pilot evidence is absent, return the alignment and sequence as unvalidated drafts, mark validation unresolved, and hand back curriculum_validation_disposition/v1 with required reviews and revalidation checks.
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-data-analysis/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-data-pipelines/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-data-share-review/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 67 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 67 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-decide/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If evidence is mostly assumption, label it and recommend a research or feedback-triage pass.
- 53 - If the decision owner is missing, keep the output as options rather than accepted strategy.
+ 52 - If demand and capacity cannot be compared in one unit or hiring ramp lag is unknown, retain the stated constraints and options, mark the recommendation tentative, and hand back the missing capacity and timing inputs.
+ 53 - If a drafted decision record lacks write approval, retain the options, tradeoffs, and proposed decision note, mark persistence not_observed, and hand back the draft for approval without writing docs/adr/.
- 57 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 57 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-decision-prototype/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 18 Required: one decision, a bounded experiment, an isolated scratch boundary, and a measurement method. Output: a decision record, prepared handoff, observation ledger, and receipt. When Hermes' bundled `spike` skill is loaded for the same question, build the way it says and keep these records: `references/spike-composition.md`.
+ 18 Required: one decision, a bounded experiment, an isolated scratch boundary, and a measurement method. Output: a decision record, prepared handoff, observation ledger, and receipt. When Hermes' bundled `spike` skill is loaded for the same question, build the way it says and keep these records: `references/spike-composition.md`. For a logic, state, or layout question, or prototype code a later plan may reference, load `references/artifact-shapes.md`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-decision-recall/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 52 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 51 - If the query, scope, tags, stale policy, or match limit is unspecified, no rejected-decision match stands yet; mark recall unresolved and hand back one question fixing the missing filter.
+ 52 - If a candidate's reviewed-rejected status or expiry cannot be checked, retain only matches that passed those checks, mark remaining recall unresolved, and hand back rejected_decision_recall/v1 with the claim boundary and missing checks.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-deliverable-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If generation tooling is missing, prepare a prompt or package handoff and mark file output not_observed.
- 52 - If QA or attachment evidence is missing, keep generated/delivered states separate and show the next check.
+ 51 - If rendered images do not match slide_count or remain uninspected, retain the observed slide_count, mark render_screenshot unresolved, and hand back the exact file and outstanding image checks.
+ 52 - If the person's approval names no final file, retain each generated version's read-back, mark approval unresolved, and hand back the stable id and version choices without selecting by modification time.
+ 53 - If a publication URL resolves to a different content hash, retain the approved file and any archive evidence already read back, mark publication unresolved, and hand back the URL and expected sha256 for destination read-back.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-deploy-and-monitor/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 53 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 52 - If a monitor has only its first baseline tick or a silent tick, retain the checklist and watchlist, mark release health not_observed, and hand back the recorded cron runs and open incidents needed to assess health.
+ 53 - If the rollback owner is missing, retain the release scope and health signals, mark the deploy decision gate unresolved, and hand back the rollback criteria with the owner question before advancing.
+ 54 - If a canary lacks host_deployment_observation/v1 or a pre-deploy production baseline, retain the checklist, mark the comparison unresolved and BLOCK, and hand back the missing observation or baseline without authorizing rollback.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-design-orchestration/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-design-quality-gate/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-docs/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-doctor/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-executor-runtime-readiness/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying.
- 54 - If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action.
+ 53 - If the scratch-edit probe is denied, keep the denial, mark permission unresolved; hand back the grant needed.
+ 54 - If a dispatch result has no session_id or thread_id, mark resumability unresolved; hand back the JSON flag.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-external-connector-readiness/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-failure-signal-audit/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-feedback-triage/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If feedback lacks source or severity, ask for the missing signal before coding handoff.
- 55 - If the item is actually a plan or research request, route to that workflow instead of triage.
+ 54 - If no feedback items are supplied, no cluster stands; mark triage not_observed and hand back the request for feedback items or a summary, source boundary, and product area.
+ 55 - If bug and feature signals cannot be separated from the supplied reports, retain source-bounded clusters, mark their classification and ranking tentative, and hand back the missing evidence with research or strategy follow-up options.
+ 56 - If a triaged cluster has no explicit coding intent or accepted-plan evidence, retain the clusters and ranking, mark the coding handoff unresolved, and hand back the next workflow recommendation with product_evidence_loop/v1 still prepared-only.
- 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-files/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-finance-analysis/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 55 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 56 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 55 - If period, currency, basis, or comparator version conflicts, retain the supplied source provenance, mark comparability unresolved, and hand back finance_scope_source_record/v1 with the conflicting attributes.
+ 56 - If totals or account mappings do not tie out, retain the confirmed scope and source record, mark reconciliation unresolved, and hand back finance_reconciliation_analysis_schedule/v1 with unreconciled gaps.
+ 57 - If recalculation fails at brief validation, retain supported calculations and finance_risk_register/v1, mark finance_decision_brief/v1 unresolved with HOLD, and hand back the failed calculation and escalation owner.
- 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 61 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-frontend/SKILL.md
Week of Nov 2, 2026 · +8 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - The frontend_route_state_matrix/v1 covers pages, 375/768/1280-style breakpoints, empty/loading/error, interaction, and CJK/locale risks.
+ 51 - The frontend_route_state_matrix/v1 covers pages, 375/768/1280-style breakpoints, empty/loading/error, interaction, and CJK/locale risks, plus submitting, submit-failed, optimistic-pending, stale/refetching, and conflict rows for remote writes.
+ 95 - When the surface reads or writes remote data, load the frontend-refactor skill's `omh-frontend-refactor/references/state-discipline.md` (sections 1 and 4-6) before writing the component: server state lives in a query cache, each mutation names the query keys it invalidates, and an optimistic write ships with its rollback.
+ 96 - When the surface has a form, a text composer, or a dialog, load `references/forms-and-input.md` before writing it: labelled controls, errors shown after the user commits a value, server field errors mapped onto their fields, one submit in flight, an Enter-to-send that waits for IME composition, and focus returned when a dialog closes.
+ 97 - Check the browser-support target before using a newer platform feature: a feature newer than the target (by default, anything only Baseline Newly available) needs feature detection plus a fallback, or a deliberate target change; suggest recording the target in the repository's agent instruction file (`omh-agent-instructions` owns that file).
+ 104 - When the handoff asks for component or interaction tests, load `skill_view(name='omh-verification-gate', file_path='references/test-authoring.md')` and name the seam each test drives: assert through what a user perceives (role, accessible name, visible text) across the frontend_component_state_inventory/v1 states, never class names or component-internal state, and fake only at the boundaries the shared page lists (network, clock, randomness).
+ 121 - browser-support target (default: Baseline Widely available, in every core browser for 30+ months)
- 140 - frontend_route_state_matrix/v1 with pages, states, viewports, CJK/locale, empty/loading/error, and interaction states
- 141 - frontend_component_state_inventory/v1 with default, hover, focus, active, disabled, loading, empty, and error states for reusable primitives
+ 145 - frontend_route_state_matrix/v1 with pages, states, viewports, CJK/locale, empty/loading/error, and interaction states, plus submitting, submit-failed, optimistic-pending, stale/refetching, and conflict (409) rows wherever the surface writes remote data
+ 146 - frontend_component_state_inventory/v1 with default, hover, focus, active, disabled, loading, empty, and error states for reusable primitives, and each primitive's interface: props, events, slots, and the invariants a caller must know; a wrapper earns a row only when deleting it would push its complexity into its callers
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-frontend-refactor/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 84 - Gate macro changes on characterization tests written before the refactor; snapshot tests lock markup, not behavior, and do not count.
+ 84 - Gate macro changes on characterization tests written before the refactor; snapshot tests lock markup, not behavior, and do not count. A change that alters DOM nesting, element type, or class composition also needs a before/after capture at one viewport, because green tests do not prove the render is unchanged.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-gateway-intent-card/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If platform metadata is missing, keep the card platform-neutral and ask for the target surface.
- 52 - If send or registration evidence is unavailable, show the adapter-owned action instead of claiming delivery.
+ 51 - If silent update conflicts with a status notice, keep the thread; hand back the silent-or-notify choice.
+ 52 - If an action would touch a thread other than the named one, mark it unresolved; hand back the target.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-geospatial-analysis/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
- 69 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 69 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-git-workflow/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-github-event-ops/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-github-issue-intake/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 55 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 54 - If reproduction evidence is still missing after three questions, retain the report classification and observed facts, mark the direction unresolved, and hand back the missing steps, versions, or logs without filing.
+ 55 - If duplicate search cannot finish, retain the scoped report summary, mark duplicate status unresolved, and hand back the explicit repository and pending search; do not confirm or dispatch creation.
+ 56 - If connector read-back lacks request binding or issue fields, retain the confirmed direction and duplicate status, mark creation not_observed, and hand back the idempotency key and missing read-back fields without redispatching.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-harness-session-inventory/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-iac-change/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-idea-to-deploy/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 52 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 51 - If the success metric or release scope is missing, retain the supplied idea and user value, mark delivery planning unresolved, and hand back the stage rail with the missing decision before an executor handoff.
+ 52 - If plan acceptance or executor choice is absent, retain the prepared decision gates and stage rail, mark the coding handoff unresolved, and hand back the acceptance or runtime-choice question.
+ 53 - If deploy evidence is missing after verification, retain the observed verification results, mark deploy and monitoring not_observed, and hand back the stage rail with the deploy evidence gate still open.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-image-cards/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If a renderer or file tool is missing, keep the package prepared and expose the generation handoff.
- 53 - If render QA is unavailable, mark the artifact unverified and request the smallest visual/file check.
+ 52 - If image_generation_capability/v1 is unknown or prompt_only, retain visual_prompt_card/v1, mark generation not_observed, and hand back image_generation_setup/v1 with the question of which image tool to use.
+ 53 - If an edit lacks the supplied image reference or preserve/remove constraints, retain only the supplied edit intent, mark transformation unresolved, and hand back the missing inputs for the image transformation brief.
+ 54 - If visual_generation_receipt/v1 reports a failed or partial attempt, retain visual_prompt_card/v1 and the receipt's failure stage, mark generation not_observed, and hand back the failed attempt without claiming an image.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-inference-serving/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
- 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-instinct-ledger/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-internal-audit/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-action-check/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-ask/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-done-check/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-failure-triage/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-review-gate/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jev-route/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-jit-learn/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-legal-compliance-review/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If the reviewed target is missing, inspect the requested artifact or ask one target question.
- 55 - If independent verification is unavailable, report the gap and avoid an approval-style claim.
+ 54 - If an authority's pinpoint or effective status cannot be verified, retain the established document scope, mark authority-dependent issues unresolved, and hand back legal_scope_authority_record/v1 with the missing citations for counsel.
+ 55 - If a contested clause has an open counsel hold or no cited playbook position, retain its issue row, mark that redline row unresolved, and hand back the counsel question rather than proposed language.
+ 56 - If mandatory counsel triggers remain open at final review, retain the issue matrix and hold register, mark legal_review_disposition/v1 unresolved with HOLD, and hand back the exact triggers and counsel owner without a final determination.
- 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-lifecycle-growth/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-live-incident-response/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 59 - If the incident turns out to be closed, hand the postmortem to `reliability-review` and leave this record as the timeline it reads.
+ 59 - If the incident turns out to be closed, hand the postmortem to `omh-reliability-review` and leave this record as the timeline it reads.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-live-info/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-llm-app-dev/SKILL.md
Week of Nov 2, 2026 · +5 / −4 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 53 - The client boundary has a deterministic fake adapter, the code around the model is unit-tested against it without a network call, and a streamed call is cancelled upstream when its client goes away.
- 91 - Route every provider call through one client boundary module that owns the model ID, credentials, timeout, retry policy, and rate-limit backoff. A second call site that builds its own client is how a model pin, a timeout, and a retry policy quietly diverge.
+ 92 - Route every provider call through one client boundary module that owns the model ID, credentials, timeout, retry policy, and rate-limit backoff. A second call site that builds its own client is how a model pin, a timeout, and a retry policy quietly diverge. Give that boundary a deterministic fake adapter beside the real one, so the code around the model is unit-tested offline; evals against the real model are a separate suite.
- 93 - Take structured output from a declared schema - a JSON schema, a typed parser, or the provider's structured-output mode - and validate every response against it. A response that fails validation is repaired by one bounded re-ask that shows the validation error, then fails loudly; it is never regex-scraped out of prose.
+ 94 - Take structured output from a declared schema - a JSON schema, a typed parser, or the provider's structured-output mode - and validate every response against it. Read the stop reason first: a response cut off at the output cap is truncated, not invalid, and is never re-asked under the same cap. A response that fails validation is repaired by one bounded re-ask that shows the validation error, then fails loudly; it is never regex-scraped out of prose.
- 98 - Give every agentic loop its budgets as product features, not prompt advice: step, time, token, cost, and tool-call budgets each with a recorded termination reason, and for recursive delegation the budgets bind the whole tree, not each node separately.
+ 99 - Give every agentic loop its budgets as product features, not prompt advice: step, time, token, cost, and tool-call budgets each with a recorded termination reason, and for recursive delegation the budgets bind the whole tree, not each node separately. Tool arguments are validated before the tool runs, and an invalid call or a tool failure returns to the model as a tool result, never thrown past the loop and never swallowed.
- 132 - Do not catch provider failures broadly; classify timeout, rate limit, transient server error, invalid request, and content refusal separately, because only some of them are safe to retry.
+ 133 - Do not catch provider failures broadly; classify timeout, rate limit, transient server error, invalid request, content refusal, and truncation at the output cap separately, because only some of them are safe to retry.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-localization-review/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If the reviewed target is missing, inspect the requested artifact or ask one target question.
- 54 - If independent verification is unavailable, report the gap and avoid an approval-style claim.
+ 53 - If the source version cannot be established, retain supplied strings and the locale/audience brief, mark terminology and cultural-fit choices tentative, and hand back the source-version question before treating the glossary as approved.
+ 54 - If rendered UI evidence is missing, retain glossary choices and the string issue matrix, mark rendered validation not_observed, and hand back locale QA criteria and review owners for an accepted `omh-visual-qa` handoff.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-long-document-reading/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-market-research/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 68 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 68 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-materials-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If a renderer or file tool is missing, keep the package prepared and expose the generation handoff.
- 54 - If render QA is unavailable, mark the artifact unverified and request the smallest visual/file check.
+ 53 - If source metrics needed by an outline section are missing, retain the verified source facts and outline, mark that section unresolved, and hand back material_artifact/v1 with its missing inputs and output owner.
+ 54 - If xlsx_recalc.py reports recalculated false, retain the observed sheet_schema, mark formula_recalculation not_observed, and hand back its missing tools and the --out <copy> recalculation and cached-value read-back steps.
+ 55 - If DOCX package validation passes without a rendered converted PDF, retain observed section_structure and required_clause_check, mark appearance and page_count not_observed, and hand back the converted-PDF preview checks.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-media-input/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-meeting-brief/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.
- 54 - If minutes or decisions were not observed, keep the output as prep rather than record.
+ 53 - If decision topics lack known context, retain the supplied meeting goal and audience, mark the agenda tentative, and hand back discussion prompts and the decisions-needed list with its open questions.
+ 54 - If action owners, due dates, or acceptance conditions are absent from a meeting record, retain the prepared agenda and prompts, mark action ownership not_observed, and hand back the action-item template with those columns marked unknown.
+ 55 - If follow-up coding lacks observed decisions or an accepted plan, retain the meeting brief, mark the coding handoff unresolved, and hand back the decisions needed rather than an implementation claim.
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-memory-new/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 52 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 51 - If project versus user scope or lasting versus temporary retention is ambiguous, retain the bounded summary as a candidate, mark capture unresolved, and hand back one scope-or-durability question without claiming a write.
+ 52 - If omh_memory returns error, retain memory_new_candidate/v1 as prepared only, mark the write not_observed, and hand back the bounded summary, record_type, tags, scope, and retention_class for the omh memory capture fallback.
+ 53 - If capture returns pending_review, retain the staged memory_new_candidate/v1, mark approval not_observed, and hand back the stated review reason without treating an unsafe or relative-time phrase as an approved record.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-memory-sync/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 53 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 52 - If entry-by-entry confirmation stops before the assembled diff is approved, retain the reviewed claim decisions, mark the diff unresolved, and hand back reviewed indexes, remaining candidates, and the next entry to resume.
+ 53 - If the native memory tool is unavailable after diff approval, retain the approved before/after diff, mark the native write not_observed, and hand back that diff without editing MEMORY.md or USER.md directly.
+ 54 - If a native write returns staged: true with a pending_id, retain the approved diff and pending_id, mark saving not_observed, and hand back /memory approve <id> for the person without repeating the write.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-meta-router/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 50 - If routing signals conflict, show the compact picker or ask one clarifying question.
- 51 - If wrapper metadata is unavailable, keep the recommendation advisory and avoid runtime claims.
+ 50 - If bounded recommend queries cannot run through CLI, plugin, or wrapper, retain only the imperative task, mark catalog selection not_observed, and hand back the workflow picker instead of a memorized recommendation.
+ 51 - If recommendation output contains only `omh-meta-router`, retain the consulted catalog evidence, mark workflow selection unresolved, and hand back the task remainder for a bounded re-query rather than selecting this skill.
+ 52 - If stage re-queries still leave a multi-stage task low-confidence, retain the consulted catalog evidence, mark the proposed chain tentative, and hand back a clarification question about the unresolved stage.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-mobile-release/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-model-finetuning/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-model-optimization/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-model-setup/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-molecular-docking/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
- 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 65 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-morning-brief/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-native-debugging/SKILL.md
Week of Nov 2, 2026 · +2 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 53 - Any print-and-rebuild probe carried the session's probe tag, and an observed search for that tag returns nothing.
- 112 - native_fault_statement/v1 separates the observed symptom from the assumed cause and names the reproduction command
+ 113 - native_fault_statement/v1 separates the observed symptom from the assumed cause, names the reproduction command, quotes the observed failure beside the reported one (`symptom_match`), and records the `minimised` reproduction
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-operating-rhythm/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 53 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 52 - If source notes are missing, retain the cadence, audience, and time-window scaffold, mark minutes and decisions not_observed, and hand back operation_artifact/v1 with the explicit missing-notes boundary.
+ 53 - If notes leave an action item's owner or due date unstated, retain its source-linked outcome and dependencies, mark follow-up readiness unresolved, and hand back the action item history with unknown fields for confirmation.
+ 54 - If a retro proposal has no decision or owner acknowledgement, retain the source notes, mark acceptance unresolved, and hand back the proposal outside the decision log for explicit confirmation before an implementation handoff.
- 57 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-ops-observability-card/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If provider metrics are unavailable, report only local metadata and mark provider truth not_observed.
- 53 - If cost or latency looks risky, surface a warning plus the next measurement rather than a completion claim.
+ 52 - If the metric window is missing, keep supplied payloads, mark quality unresolved; hand back the next measure.
+ 53 - If a budget threshold is missing, keep the observed cost, mark advice tentative; hand back the gaps.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-ops-review/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 52 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 51 - If status evidence covers only part of the requested time window, retain the dated observations in the status summary, mark uncovered status not_observed, and hand back the missing periods and affected priorities.
+ 52 - If a blocker needs a code fix but no follow-up is accepted, retain the observed blocker and risk, mark remediation unresolved, and hand back the follow-up action for acceptance before delegation.
- 56 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 56 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-paper-learning/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 64 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-parallel-tools/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-people-ops/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 54 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 53 - If interview evidence cannot support a candidate debrief, retain the role outcomes, must-have versus trainable criteria, and scorecard, mark the recommendation unresolved, and hand back the missing evidence to the decision owner.
+ 54 - If policy constraints need a jurisdiction-specific ruling, retain the role brief and interview scorecard, mark the policy conclusion unresolved, and hand back the flagged questions to `omh-legal-compliance-review`.
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-physical-device-readiness/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-plan/SKILL.md
Week of Nov 2, 2026 · +10 / −5 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 47 - When the plan describes code changes, it has a `Review Focus` section with at most 5 uncovered inputs and their owning tasks, or one stating the check found none.
+ 47 - When the plan describes code changes, it has a `Review Focus` section with at most 5 uncovered inputs and their owning task ids, or one stating the check found none.
+ 48 - When the plan describes code changes, every task has an id, its dependencies, the files it may write, and a done check, and the last task is the closing gate.
+ 49 - When the plan describes code changes, each code task is a vertical slice whose done check exercises its behavior end to end, or a prefactor ordered before the slices, or a wide change handed to `refactor-plan`, or the one task that writes a file every slice only appends to; the closing gate and fix tasks aside.
- 52 - If acceptance criteria or verification are missing, route back to clarification before handoff.
- 53 - If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.
+ 54 - If no acceptance answer comes, keep the draft unaccepted, hand back the question, prepare no handoff.
+ 55 - If a verification step has no outside judge, mark it unresolved and hand back the missing judge.
- 81 - When the plan describes code changes, add a `Review Focus` section listing at most 5 inputs or failure modes the requirements imply that no planned test covers, likeliest first, each with its expected behavior and the owning task that will add the test; an input the requirements do not mention must still leave the result intact, and when the check turns up nothing the section says it found none.
+ 83 - When the plan describes code changes, add a `Review Focus` section listing at most 5 inputs or failure modes the requirements imply that no planned test covers, likeliest first, each with its expected behavior and the id of the owning task that will add the test; an input the requirements do not mention must still leave the result intact, and when the check turns up nothing the section says it found none.
+ 85 - When the plan describes code changes, give each task a stable id (`T1`, `T2`, ...), the ids it depends on, the files it may write, and its done check (a checkable step as above; for a code task, a command with the result that counts as passing - the test's run command, a gate, or a grep for the signature - while a task that is not code may keep an observable check); when two tasks write the same file, one lists the other directly among its dependencies, since an order through a third task does not count. These carry a `dag-ulw` node's id, depends_on and write_scope, and the done check feeds its VERIFY and STOP WHEN; converting still adds each node's label, category and full prompt, and a baseline node before a full-suite check.
+ 86 - When the plan describes code changes, cut the code tasks as vertical slices: each delivers one behavior through every layer it needs, and its done check drives that behavior through the surface a user or caller reaches, so an integration failure shows in the task that caused it rather than first in the closing gate. Do not split by layer to keep write scopes apart: slices that write the same file are ordered, each later slice listing every earlier slice that writes it directly among its dependencies, since an order through a slice between them does not count; a file every slice only appends to (a changelog, a generated index) may instead be written by one task after the slices; when that file is generated and drift-gated (a generated index), each slice's done check excludes that file's gate and the later task runs it. A layer-only task is either a prefactor that makes the later slices easy and comes before them, or a wide mechanical change across many callers, handed to `refactor-plan` (the new form beside the old, callers moved in groups while both stay green, the old form deleted last) instead of a split by layer.
+ 87 - When the plan describes code changes, its last task is the closing gate, named as the verification task (in `dag-ulw`, a node with `role: verify`): it depends on every other task, runs the real verification commands with the result that counts as passing, is run by someone other than the agent that built the work, and ends with a review. The plan states that a review that is not clean adds a fix task with its own id and done check and then reruns the gate instead of ending the plan - at most two fix rounds, or fewer when the engine running the plan stops sooner, after which the open findings are reported.
- 88 - Plan acceptance approves the plan content, not execution: after acceptance, recommend the follow-on path that fits the work's shape — `ultrawork` durable checkpoints for progress that must survive sessions as a checkpointed ledger, `ultrawork` coordinated lanes for an accepted plan split into disjoint parallel lanes, `ultrawork` single-owner persistence for one already-scoped task with a single owner, `ultrawork` for one bounded delivery cycle, or a direct selected executor/runtime handoff for a single prepared coding change — state the fit reason in one line, and start it only after the user's explicit go-ahead.
+ 93 - Plan acceptance approves the plan content, not execution: after acceptance, recommend the follow-on path that fits the work's shape — `dag-ulw` for an accepted plan whose tasks form a graph (several tasks with disjoint write scopes or an order between them, handing work on through files, plus a separate verification task), `ultrawork` durable checkpoints for progress that must survive sessions as a checkpointed ledger, `ultrawork` coordinated lanes for an accepted plan split into disjoint parallel lanes, `ultrawork` single-owner persistence for one already-scoped task with a single owner, `ultrawork` for one bounded delivery cycle, or a direct selected executor/runtime handoff for a single prepared coding change — state the fit reason in one line, and start it only after the user's explicit go-ahead.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-product-brief/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 55 - If acceptance criteria or verification are missing, route back to clarification before handoff.
- 56 - If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.
+ 55 - If the problem gate has not returned validated, retain supplied product evidence as unvalidated, mark PRD readiness unresolved, and hand back the problem and user context to `omh-product-discovery-validation`.
+ 56 - If the decision owner has not resolved prioritization tradeoffs, retain the drafted PRD and roadmap options, mark roadmap commitment unresolved, and hand back the tradeoffs and open questions for that owner.
+ 57 - If Jira or Linear updates lack an explicit target and approval, retain the prepared PRD, mark roadmap-system mutation not_observed, and hand back the target and approval questions for `omh-apps`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-product-discovery-validation/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-production-audit/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If the reviewed target is missing, inspect the requested artifact or ask one target question.
- 53 - If independent verification is unavailable, report the gap and avoid an approval-style claim.
+ 52 - If build or CI evidence is missing for the target release, retain the evidenced readiness_matrix/v1 rows, mark readiness unresolved, and hand back release_gate_verdict/v1 on HOLD with the missing evidence list.
+ 53 - If rollback owner, health thresholds, or recovery path is missing, retain the evidenced readiness_matrix/v1 rows, mark rollback readiness unresolved, and hand back rollback_and_monitoring_plan/v1 with the exact gaps.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-prompt-import-readiness/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-provider-profile-posture/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 52 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 51 - If provider ID or profile ID is missing, retain the supplied capability requirements, mark provider_profile_posture/v1 unresolved, and hand back a request for the missing ID without reading any secret.
+ 52 - If secret-presence metadata is absent, retain the named provider, profile, and requested capabilities, mark secret presence not_observed, and hand back metadata-only secret requirements plus allowed and prohibited actions.
+ 53 - If only a host observation reference is supplied, retain it as metadata, mark provider connectivity not_observed, and hand back provider_profile_posture/v1 without claiming credential validation or making a provider call.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-refactor-plan/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
- 57 - If reconnaissance finds the direction itself is unsettled, route back to `ralplan` before ordering phases.
+ 57 - If reconnaissance finds the direction itself is unsettled, route back to `ulw-plan` before ordering phases.
+ 58 - If the module to deepen is chosen but its interface is not, shape it under contrasting constraints and recommend one design before phase 1; that is not a contested direction.
- 86 - Stop at the approval gate and hand the user the go/no-go, whole plan or first phase.
+ 87 - Stop at the approval gate and hand the user the go/no-go, whole plan or first phase; when the approved phases split into groups with disjoint files plus a verification step, a whole-plan go may also name `dag-ulw` with the fit reason in one line, started only on the user's explicit go-ahead: the phase order becomes `depends_on` and each phase's verification command its node's VERIFY. `dag-ulw` runs without pausing between phases and neither commits nor rolls back, so say the per-phase commits are cut after the run and the rollback points stay with the user, or take the first-phase path.
- 94 - the decided target shape (what moves where), or a pointer to the accepted plan that decided it
+ 95 - the decided target shape (what moves where), or a pointer to the accepted plan that decided it; for a chosen deepening candidate whose interface is still open, shape it first per `omh-refactor-plan/references/interface-shaping.md`
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-relational-db/SKILL.md
Week of Nov 2, 2026 · +2 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 89 - For a read-modify-write, an upsert, a queue table, or a deadlock, use the concurrency section of the lock tables: name the isolation level, the row lock and its order, and which error codes retry the whole transaction.
+ 90 - Give non-transactional DDL such as `CREATE INDEX CONCURRENTLY` its own migration marked non-transactional; never drop `CONCURRENTLY` to satisfy the migration tool.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-release-cut/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-reliability-review/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 54 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 53 - If metrics do not cover the named service and time window, retain the cited incident notes, mark SLO and error-budget conclusions unresolved, and hand back the evidence and missing-evidence list with the uncovered window.
+ 54 - If remediation closure has no supporting reference, retain the source-backed reliability review, mark closure not_observed, and hand back the remediation follow-ups and missing closure evidence without claiming the fix completed.
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-report-package/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If input evidence is incomplete, mark the section as pending rather than fabricating a report claim.
- 53 - If delivery or attachment is unavailable, keep the report package prepared_not_observed.
+ 52 - If no presentation tool can produce a binary deck, retain the PPT-ready Markdown or JSON outline, mark binary export not_observed, and hand back the outline, assumptions, and missing-input list for separate deck generation.
+ 53 - If the tool returns "rendered": false (it still exits 0) or its image count differs from slide_count, keep the deck's outline read-back, leave render QA not observed, and hand back the missing-tool or image-count gap for that file.
+ 54 - If the requested achievements export fails, retain the rest of the report package, mark the badge section not_observed, and hand back the missing output from omh achievements export --format md instead of inventing badges.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-repro-audit/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 66 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 66 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-research-brief/SKILL.md
Week of Nov 2, 2026 · +5 / −4 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 53 - If sources cannot be accessed, state the retrieval gap and use only observed local context.
- 54 - If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary.
+ 53 - If ledger verification cites zero distinct sources, retain the source ledger and evidence table, mark the citation check not_observed, and hand back the draft with the missing [n] source IDs for correction.
+ 54 - If an evidence row's quote cannot be attached from the page text, retain the retrieved source and other supported rows, mark that claim unresolved, and hand back the unmatched wording and source for correction.
+ 55 - If a pricing comparison mixes periods, currencies, or denominators, retain its dated source rows, mark the comparison tentative, and hand back the missing common basis before drawing a decision implication.
- 58 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
- 82 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`), and carry two more fields on every evidence row: the ledger id written as `[n]` - a bare number in a cell is not a citation to `verify`, so that row would go unchecked - and the verbatim quote attached with `sources.py quote <id> --text <quote> --from <page text file>`, which rejects wording that file does not contain. Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. A row whose quote could not be attached says so, and a claim that rests on model knowledge is marked `[unverified]` and listed as unresolved, never entered as evidence. Run `sources.py verify <draft> --evidence`, since every evidence row is meant to carry its quote, and report the citation check from that run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`; it is a citation check, not fact verification. Without the skill, keep the source and its quoted wording in the row and report the citation check as `not_observed`.
+ 83 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`), and carry two more fields on every evidence row: the ledger id written as `[n]` - a bare number in a cell is not a citation to `verify`, so that row would go unchecked - and the verbatim quote attached with `sources.py quote <id> --text <quote> --from <page text file>`, which rejects wording that file does not contain. Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. A row whose quote could not be attached says so, and a claim that rests on model knowledge is marked `[unverified]` and listed as unresolved, never entered as evidence. Run `sources.py verify <draft> --evidence`, since every evidence row is meant to carry its quote, and report the citation check from that run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`; it is a citation check, not fact verification. After that verify, run `omh research receipts verify --citations <ledger> --draft <draft>` and report its fetched coverage from the run, or as `not_observed`; a receipt proves only that the page was opened in this session tree, never that it supports the claim. Without the skill, keep the source and its quoted wording in the row and report the citation check as `not_observed`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-research-department/SKILL.md
Week of Nov 2, 2026 · +4 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 55 - If sources cannot be accessed, state the retrieval gap and use only observed local context.
- 56 - If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary.
+ 55 - If one watch source cannot be read, retain covered sources' findings and the failed source's previous cutoff, mark its coverage unresolved, and hand back that source and uncovered window rather than reporting a quiet period.
+ 56 - If the synthesis tool cannot process collected findings, retain raw findings in source_inbox/v1, mark synthesis not_observed, and hand back research_department_plan/v1 with the synthesis-tool readiness gap.
+ 57 - If schedule creation has no cronjob_manage result or cron listing, retain the cadence and Scout, Analyst, and Briefer plan, mark job creation not_observed, and hand back the prepared job description for separately approved scheduling.
- 60 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 61 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-routing/SKILL.md
Week of Nov 2, 2026 · +4 / −4 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 59 - If routing signals conflict, show the compact picker or ask one clarifying question.
- 60 - If wrapper metadata is unavailable, keep the recommendation advisory and avoid runtime claims.
+ 59 - If a skill is not installed, keep the intent; hand back the install gap as unresolved.
+ 60 - If executor readiness is unknown, keep routing; hand back the check as not_observed.
- 68 - Intent -> plan: `deep-interview`, `ralplan`, `plan`, `loop`.
+ 68 - Intent -> plan: `deep-interview`, `ralplan`, `plan`, `dag-ulw`, `loop`.
- 81 - Never let that autonomy bypass existing confirmation gates for destructive changes, credentials, external writes, deployment, executor dispatch, or starting a follow-on workflow engine (`ultrawork` — including its coordinated-scope, single-owner-persistence, delivery-boundary, and durable-checkpoint capabilities — `loop`, `ultraqa`) from another skill's output: an accepted plan or clarified brief is planning evidence, not permission — recommend the engine that fits the work's shape and wait for the user's explicit go-ahead. Do not claim that a native skill, subagent, review, CI, or merge ran unless matching observation exists.
+ 81 - Never let that autonomy bypass existing confirmation gates for destructive changes, credentials, external writes, deployment, executor dispatch, or starting a follow-on workflow engine (`dag-ulw`, `ultrawork` — including its coordinated-scope, single-owner-persistence, delivery-boundary, and durable-checkpoint capabilities — `loop`, `ultraqa`) from another skill's output: an accepted plan or clarified brief is planning evidence, not permission — recommend the engine that fits the work's shape and wait for the user's explicit go-ahead. Do not claim that a native skill, subagent, review, CI, or merge ran unless matching observation exists.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-rules-distill/SKILL.md
Week of Nov 2, 2026 · +9 / −7 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 47 - The durable fact, source evidence, retrieval hint, and staleness risk are recorded.
- 48 - Uncertain or conflicting knowledge is marked as review-needed rather than permanent truth.
- 49 - Separate coding or docs tasks are extracted instead of buried in notes.
+ 47 - Every candidate in principle_candidate_set/v1 cites the repeated observations it rests on; a candidate resting on one observation stays needs-evidence in review_queue/v1.
+ 48 - Every candidate is classed mechanical or judgement before it is worded. A mechanical candidate is a miss a machine can find from the text alone (a forbidden call, a disallowed import, a file in the wrong place), and its destination is a check (a linter rule, test, hook, or CI step); when the repository already has a check for it that never runs or no longer fails, the candidate is repairing that check, not adding another. Its approved_patch_handoff/v1 names the check and where it is wired, and sets as an acceptance criterion the run the implementer must observe: the check fails with the violation injected and passes once it is reverted. A mechanical candidate outside the chosen destination boundary is reported as a check proposal outside the boundary, never reworded as prose. Only judgement candidates, which need a reader (consistency across files, fit with the code around them), are worded as prose.
+ 49 - duplication_conflict_report/v1 names the existing rule or check each candidate repeats or contradicts, or says none was found and where it looked.
+ 50 - Nothing reached a destination without an approval recorded in review_queue/v1.
- 53 - If source evidence conflicts, route to memory or knowledge review before writing durable guidance.
- 54 - If the fact may be stale, record the staleness warning and next refresh action.
+ 54 - If a principle rests on one observation, retain its source reference in principle_candidate_set/v1, mark the rule tentative and needs-evidence in review_queue/v1, and hand back the candidate for repeated observations.
+ 55 - If approval is missing, retain principle_candidate_set/v1 and duplication_conflict_report/v1, mark implementation not_observed, and hand back review_queue/v1 without producing approved_patch_handoff/v1.
+ 56 - If skill_manage stages an approved change, retain the approved candidate and staged result, mark the skill update not_observed, and hand back the pending ID for the person's `/skills approve <id>`.
- 91 - destination boundary: AGENTS, skill catalog, prompt, docs, memory, or no-write review
+ 93 - destination boundary: AGENTS, skills, prompt, docs, memory, check, or no-write review
- 106 - principle_candidate_set/v1 with source references, repeated pattern, candidate wording, scope, non-goals, and risk
+ 108 - principle_candidate_set/v1 with source references, repeated pattern, mechanical or judgement class, candidate wording or check, scope, non-goals, and risk
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-run-efficiency/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If provider metrics are unavailable, report only local metadata and mark provider truth not_observed.
- 53 - If cost or latency looks risky, surface a warning plus the next measurement rather than a completion claim.
+ 52 - If the named Hermes session has no row or recorded tokens, retain supplied timings and context data in run_efficiency_report/v1, mark host_usage not_observed, and hand back the session ID for a recorded-usage check.
+ 53 - If session_activity_receipt/v1 omits tool durations or context-budget metrics, retain its available observations, mark the missing metrics not_observed rather than zero, and hand back the exact missing measurements.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-running-work-board/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-rust/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 50 - The gate list names the exact commands the executor must run and pass.
+ 50 - The gate list names the exact commands the executor must run and pass, covering every target, the feature extremes, doc tests, and the declared MSRV.
- 82 - Load `references/rust-discipline.md` for the ownership, error, and API rules, and name the gate commands from it rather than assuming `cargo build` is the whole bar.
+ 82 - Load `references/rust-discipline.md` for the ownership, error, API, binary-interface, and dependency rules, and name the gate commands from it rather than assuming `cargo build` is the whole bar.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-sales-development/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If evidence is mostly assumption, label it and recommend a research or feedback-triage pass.
- 55 - If the decision owner is missing, keep the output as options rather than accepted strategy.
+ 54 - If consent or suppression status is unknown, retain sales_opportunity_evidence_record/v1 and sales_qualification_state/v1, mark sequence eligibility unresolved with HOLD, and hand back the missing eligibility questions without drafting outreach.
+ 55 - If no observed buyer response supports a commitment, retain the eligible sales_draft_sequence/v1, mark confirmation not_observed, and hand back sales_handoff_disposition/v1 with proposed actions, owners, timing, and exit criteria.
- 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-sales-pipeline-review/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-security-event-response/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Instructions only
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-security-safety-review/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If the reviewed target is missing, inspect the requested artifact or ask one target question.
- 55 - If independent verification is unavailable, report the gap and avoid an approval-style claim.
+ 54 - If verify-new lacks an observed credential check, retain the redacted risk matrix and credential_rotation_sequence/v1, mark replacement unresolved, and hand back the verify-new evidence requirement before the operator revokes the old credential.
+ 55 - If no single local plugin directory is explicitly named, no plugin audit finding stands; mark plugin_risk_audit/v1 not_observed and hand back the directory question without importing, registering, or activating any plugin.
+ 56 - If a proposed deny glob also blocks commands the workflow needs, retain safe_action_policy/v1, mark proposed_approval_deny_list/v1 unresolved, and hand back the conflicting globs and needed commands for user revision without changing config.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-show-reel/SKILL.md
Week of Nov 2, 2026 · +2 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 30 - If the selected concept is a 60-120 s launch film of a product the team can run and capture, read `references/launch-film.md` before the act sheet and scene authoring; a promo of 15 s or less keeps the one-scene rule.
+ 41 - A promo or social clip of 15 s or less holds one hero scene with no meta text, one number smaller than the logo, and the official logo unboxed at 25% or more of the frame height; check a still sheet against `references/craft-design.md` (Short promo clips) before rendering.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-skill/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-skill-health/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-skill-scout/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-source-finder/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 62 - If the user asks for facts or citations, route to `research`.
+ 62 - If the user asks for facts or citations, route to `ulw-research`.
- 68 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 68 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-spend-gate/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-sprite-forge/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Local scripts → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Local scripts
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-support-operations/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 54 - If feedback lacks source or severity, ask for the missing signal before coding handoff.
- 55 - If the item is actually a plan or research request, route to that workflow instead of triage.
+ 54 - If customer impact or reproduction evidence is missing, retain the stated case facts, mark severity tentative, and hand back the reply draft and missing repro, account, or entitlement evidence list.
+ 55 - If no escalation owner or path is available, retain the issue/severity/impact/escalation matrix, mark ownership unresolved, and hand back the internal next-step and owner handoff brief with the owner question.
- 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 59 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-systematic-review/SKILL.md
Week of Nov 2, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 98284f305f6a
No earlier version was observed for comparison.
skills/omh-tech-debt-audit/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 3 description: "[omh] Accumulated tech debt to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED against the previous ledger on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt."
+ 3 description: "[omh] Accumulated tech debt or architecture deepening to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt."
- 68 Strong routing signals: `tech-debt-audit`, `tech debt`, `tech debt audit`, `technical debt`, `technical debt audit`, `tech debt ledger`, `debt ledger`, `audit our tech debt`, `tech debt report`, `code debt audit`, `where is our tech debt`, `기술부채`, `기술 부채`, `기술부채 감사`, `기술부채 감사해줘`, `기술부채 점검`, `기술부채 장부`, `부채 원장`, `техдолг`, `технический долг`, `аудит техдолга`, `аудит технического долга`
+ 68 Strong routing signals: `tech-debt-audit`, `tech debt`, `tech debt audit`, `technical debt`, `technical debt audit`, `tech debt ledger`, `debt ledger`, `audit our tech debt`, `tech debt report`, `code debt audit`, `where is our tech debt`, `improve the codebase architecture`, `improve the architecture of this repo`, `deepening opportunities in this codebase`, `shallow modules in this codebase`, `기술부채`, `기술 부채`, `기술부채 감사`, `기술부채 감사해줘`, `기술부채 점검`, `기술부채 장부`, `부채 원장`, `코드베이스 아키텍처 개선해줘`, `코드 아키텍처 개선해줘`, `техдолг`, `технический долг`, `аудит техдолга`, `аудит технического долга`
+ 84 - For an architecture-improvement or deepening request, load `omh-tech-debt-audit/references/architecture-deepening.md`: candidates are architectural-decay ledger rows proven shallow by the deletion test, never by size, and the audit stops at ranked candidates with one named top pick - it proposes no interface.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-terminal/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Network or broad shell → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Network or broad shell
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-todo-checklist/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-toolbelt-readiness/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 53 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 52 - If tool_search finds a deferred native tool but access is untested, retain its present classification, mark API access not_observed, and hand back the tool_call step for a user-approved check instead of listing the tool as missing.
+ 53 - If a required MCP server or CLI is absent, retain the present, optional, and unsafe inventory entries, mark workflow readiness unresolved, and hand back the missing dependency and installation owner without installing it.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-verification-gate/SKILL.md
Week of Nov 2, 2026 · +5 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If the expected behavior is unclear, route back to plan before running adversarial checks.
- 53 - If verification fails, return to fix or research with the failed signal instead of advancing.
+ 52 - If a required check fails with an unknown origin, keep the other fresh results, mark the claim unresolved on HOLD, and hand back the same check rerun at the merge base as the missing evidence.
+ 53 - If a fix test has only a fresh green result, retain that result within its scope, mark the claim unresolved on HOLD with regression_witness_missing, and hand back the required pre-fix red witness and its source.
+ 54 - If a declared generated path has no known regeneration command, retain verification_matrix/v1, mark generated-output verification unresolved, and hand back generated_artifact_provenance/v1 with the command gap.
+ 85 - A fix claim whose evidence is a new or changed test needs a regression witness: an observed red of that test, for the bug's reason, on the pre-fix tree (the fix commit's parent, or the merge-base when the fix is the whole change), recorded with its source -- a run in a clean detached worktree at that tree, a CI job on a commit that adds only the test, or the debugging session's run before the fix. A collection or import error there is not a witness. For an intermittent fault the witness is the failure rate over N runs before beside 0/N at the same N after. When the test calls a seam the fix added, force the red by reverting only the behavioural lines, keep the seam, and show that diff. When the fix changes only test code, the witness is the old test's measured failure rate on the pre-fix tree beside the new test's 0/N at the same N. A fix test only ever observed green is HOLD with `regression_witness_missing`. A fix recorded with `regression_seam: none_correct` and its reason has no fix test; its evidence is the reproduction loop observed red before and green after (for an intermittent fault, its rate over N runs before beside 0/N after), and the test witness rule does not apply.
- 112 - claim_verdict/v1 with PASS, HOLD, or BLOCK and exact missing or failed checks, each failed one with its origin
+ 114 - claim_verdict/v1 with PASS, HOLD, or BLOCK, a HOLD reason of `regression_witness_missing` when a fix test has no observed pre-fix red, and exact missing or failed checks, each failed one with its origin
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-visual-qa/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-voice-input/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 51 - If transcript confidence or intent is weak, ask one short clarification before action.
- 52 - If platform delivery is unavailable, keep the response in chat and mark delivery not_observed.
+ 51 - If a dictated request names no target context, nothing is actionable yet; mark the next action unresolved and hand back one target question before preparing voice-operator/v1.
+ 52 - If a clarified voice request still lacks confirmation for a risky action, retain the voice-operator/v1 guidance, mark execution not_observed, and hand back the proposed next action for explicit approval.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-web-research/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 66 - If leads keep expanding past one round, hand the question to `research` with the sources already gathered.
+ 66 - If leads keep expanding past one round, hand the question to `ulw-research` with the sources already gathered.
- 70 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 70 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
- 95 - When that ledger is in use, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`, and so is an answer given only in chat: `verify` reads a draft file and exits `2` without one, so write the answer to a file first when the check matters. The run compares cited ids and the Sources block with the ledger; it does not test whether a claim is true, so a passing citation check is never reported as fact verification. Without the ledger the citation check is `not_observed`.
+ 95 - When that ledger is in use, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`, and so is an answer given only in chat: `verify` reads a draft file and exits `2` without one, so write the answer to a file first when the check matters. The run compares cited ids and the Sources block with the ledger; it does not test whether a claim is true, so a passing citation check is never reported as fact verification. After that verify, run `omh research receipts verify --citations <ledger> --draft <draft>` and report its fetched coverage from the run, or as `not_observed`; a receipt proves only that the page was opened in this session tree, never that it supports the claim. Without the ledger the citation check is `not_observed`.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-websearch-setup/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-wiki/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-workflow-learning/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/omh-workspace-audit/SKILL.md
Week of Nov 2, 2026 · +2 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If required context is missing, ask one blocking question or route back to the narrower workflow.
- 53 - If runtime or wrapper evidence is unavailable, keep the status as not_observed and expose the next observable action.
+ 52 - If an in-scope plugin, MCP, or runtime surface cannot be inspected, retain the observed surface_inventory/v1 entries, mark that surface not_observed, and hand back the evidence gap rather than call it a missing capability.
+ 53 - If config risks cannot be checked without exposing secret values, retain redacted key names and paths, mark those checks unresolved, and hand back config_security_findings/v1 with risk categories for later remediation.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-context/SKILL.md
Week of Nov 2, 2026 · +1 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 61 - If the user moves from terminology to implementation, summarize confirmed understanding and hand off to `ralplan`, `ulw-plan`, or the selected coding owner only after a separate go-ahead.
+ 61 - If the user moves from terminology to implementation, summarize confirmed understanding and hand off to `ulw-plan` or the selected coding owner only after a separate go-ahead.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-interview/SKILL.md
Week of Nov 2, 2026 · +2 / −1 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 105 number (a reply by number would collide with it, in the list below and in a messaging picker).
+ 105 number (a reply by number would collide with it). If memory suggests candidates, draw one
+ 106 from the request or repository, so memory never fills every slot.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-loop/SKILL.md
Week of Nov 2, 2026 · +1 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
+ 112 - When the stop ladder names `replan_stuck_loop_once`, re-plan once from the goal ledger and recorded failures alone, not the transcript or recalled memory; record the new approach and continue; a second stop names the blocker step.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-maestro/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 58 - If the selected executor is unavailable, ask for Codex, Claude Code, Hermes, or another runtime before retrying.
- 59 - If dispatch or result evidence is missing, keep the handoff prepared_not_observed and expose the next observable action.
+ 58 - If this run lacks an explicit coding-owner choice, no handoff stands yet; mark prompt composition unresolved and hand back the choose_executor question without selecting a CLI.
+ 59 - If the scratch-edit permission probe fails, retain the composed prompt and discovered skill names, mark execution not_observed, and hand back the denied permission and required grant change before retrying.
+ 60 - If dispatch returns no session or thread id, retain the dispatch receipt, mark steering unresolved, and hand back the explicit unsteerable note and any observed unit result without claiming a resumable session.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-perf/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-plan/SKILL.md
Week of Nov 2, 2026 · +4 / −4 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 67 - If current-source evidence is missing, route a `research` step before accepting the plan.
- 68 - If the user asks for implementation after acceptance, recommend the follow-on path that fits the work's shape (`ultrawork` with the matching capability — durable checkpoint, coordinated lanes, single-owner persistence, or one delivery cycle — or a direct selected executor handoff) with a one-line fit reason, and start it only on the user's explicit go-ahead — never auto-start an engine from acceptance alone.
+ 67 - If current-source evidence is missing, route a `ulw-research` step before accepting the plan.
+ 68 - If the user asks for implementation after acceptance, recommend the follow-on path that fits the work's shape (`dag-ulw` when the accepted lanes form a graph with a verification lane, `ulw-work` with the matching capability — durable checkpoint, coordinated lanes, single-owner persistence, or one delivery cycle — or a direct selected executor handoff) with a one-line fit reason, and start it only on the user's explicit go-ahead — never auto-start an engine from acceptance alone.
- 95 - List every lane of the accepted plan in node-prompt shape - `TASK`, `DELIVERABLE`, `SCOPE`, `VERIFY`, `STOP WHEN` - with `depends_on` per lane, so `ultrawork` can prepare board rows from the plan without re-planning; planning itself stays a bounded in-session lane.
+ 95 - List every lane of the accepted plan in node-prompt shape - `TASK`, `DELIVERABLE`, `SCOPE`, `VERIFY`, `STOP WHEN` - with `depends_on` per lane, so `dag-ulw` nodes or `ultrawork` board rows come from the plan without re-planning; planning itself stays a bounded in-session lane.
- 110 - Plan acceptance approves the plan content, not execution: after acceptance, recommend the follow-on path that fits the work's shape — `ultrawork` durable checkpoints for progress that must survive sessions as a checkpointed ledger, `ultrawork` coordinated lanes for an accepted plan split into disjoint parallel lanes, `ultrawork` single-owner persistence for one already-scoped task with a single owner, `ultrawork` for one bounded delivery cycle, or a direct selected executor/runtime handoff for a single prepared coding change — state the fit reason in one line, and start it only after the user's explicit go-ahead.
+ 110 - Plan acceptance approves the plan content, not execution: after acceptance, recommend the follow-on path that fits the work's shape — `dag-ulw` for an accepted plan whose tasks form a graph (several tasks with disjoint write scopes or an order between them, handing work on through files, plus a separate verification task), `ultrawork` durable checkpoints for progress that must survive sessions as a checkpointed ledger, `ultrawork` coordinated lanes for an accepted plan split into disjoint parallel lanes, `ultrawork` single-owner persistence for one already-scoped task with a single owner, `ultrawork` for one bounded delivery cycle, or a direct selected executor/runtime handoff for a single prepared coding change — state the fit reason in one line, and start it only after the user's explicit go-ahead.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-qa/SKILL.md
Week of Nov 2, 2026 · +3 / −2 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 52 - If the expected behavior is unclear, route back to plan before running adversarial checks.
- 53 - If verification fails, return to fix or research with the failed signal instead of advancing.
+ 52 - If a scenario needs a real install or external service the harness cannot reach, retain other observed pass/fail evidence, mark that scenario not_observed, and hand back its manual test guide with setup, do, expect, and broken signals.
+ 53 - If a hostile browser scenario would submit, buy, send, or delete on a live target without approval, retain read-only scenario results, mark that action not_observed, and hand back the target and exact action for user approval.
+ 54 - If a failing browser scenario has no screenshot or console readback, keep its observed failure, mark diagnosis tentative, and hand back the scenario, target, and missing capture for a bounded rerun.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-research/SKILL.md
Week of Nov 2, 2026 · +3 / −3 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
- 72 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+27 more`) - research, signals, ops, and briefings.
+ 72 - Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `model-optimization`, `inference-serving`, `model-finetuning`, `research-brief`, `+28 more`) - research, signals, ops, and briefings.
- 100 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`). Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. Use parent-only serialized writes: lanes return observed source entries and quote refs; the parent registers URLs, attaches quotes, and remaps lane ids before drafting. Lanes never write the shared ledger. When a human briefing is written, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`. It is a citation check, not fact verification, and it never stands in for the contested-claim gate. Without the skill, keep each source's URL and retrieval date in the research notes and report the citation check as `not_observed`.
+ 100 - When Hermes' bundled `grounded-citations` skill is available, load it and register each source in its ledger when it is retrieved (`scripts/sources.py add`). Keep the run's ledger in a file of its own, passed as `--ledger <path>` before the subcommand on every call: the default ledger is shared by the whole profile, and another run's reset rebinds its ids. Use parent-only serialized writes: lanes return observed source entries and quote refs; the parent registers URLs, attaches quotes, and remaps lane ids before drafting. Lanes never write the shared ledger. When a human briefing is written, report the citation check from a run, or as `not_observed`: the exit status of `sources.py verify <draft>` is the observed check - `0` is a pass and any other status is not - and `verify --evidence` also fails a draft whose cited source carries no verbatim quote. An exit `0` whose `info: stats:` line reads `0 distinct source(s) cited` checked nothing and is reported as `not_observed`. It is a citation check, not fact verification, and it never stands in for the contested-claim gate. After that verify, run `omh research receipts verify --citations <ledger> --draft <draft>` and report its fetched coverage from the run, or as `not_observed`; a receipt proves only that the page was opened in this session tree, never that it supports the claim. Without the skill, keep each source's URL and retrieval date in the research notes and report the citation check as `not_observed`.
- 103 - Decompose the question into orthogonal research axes and disambiguate named entities before any deep reading.
+ 103 - Decompose the question into orthogonal research axes and disambiguate named entities before any deep reading. Before answering from a source, confirm it studies the exact entity the question names; a different name is a different entity unless a source says they are the same, so a source on a related one is a lead, not an answer.
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
skills/ulw-work/SKILL.md
Week of Nov 2, 2026 · +0 / −0 lines
Before Instructions only → After Network or broad shell
d8697e46651e → 98284f305f6a
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → d8697e46651e
No earlier version was observed for comparison.
Verified commit 98284f305f6a9dce6e36a1580c9f333105f1a950
git clone --filter=blob:none --no-checkout https://github.com/rlaope/oh-my-hermes.git .hotskills/rlaope-oh-my-hermes && git -C .hotskills/rlaope-oh-my-hermes checkout --detach 98284f305f6a9dce6e36a1580c9f333105f1a950
# Copy each selected skill directory from .hotskills/rlaope-oh-my-hermes into .claude/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/rlaope/oh-my-hermes.git .hotskills/rlaope-oh-my-hermes && git -C .hotskills/rlaope-oh-my-hermes checkout --detach 98284f305f6a9dce6e36a1580c9f333105f1a950
# Copy each selected skill directory from .hotskills/rlaope-oh-my-hermes into .agents/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/rlaope/oh-my-hermes.git .hotskills/rlaope-oh-my-hermes && git -C .hotskills/rlaope-oh-my-hermes checkout --detach 98284f305f6a9dce6e36a1580c9f333105f1a950
# Copy each selected skill directory from .hotskills/rlaope-oh-my-hermes into .cursor/skills/<skill-name>/git clone --filter=blob:none --no-checkout https://github.com/rlaope/oh-my-hermes.git .hotskills/rlaope-oh-my-hermes && git -C .hotskills/rlaope-oh-my-hermes checkout --detach 98284f305f6a9dce6e36a1580c9f333105f1a950
# Copy each selected skill directory from .hotskills/rlaope-oh-my-hermes into .opencode/skills/<skill-name>/Heat
7.8- Star growth, last 7 daysAhead of 96% of tracked repositories
- Star growth, last 24 hoursAhead of 96% of tracked repositories
- Rank movement, last 7 daysAhead of 62% of tracked repositories
- Commits, last 30 daysAhead of 100% of tracked repositories
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekAhead of 0% of tracked repositories
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
Individual skills in this repository
- omh-accessibility-audit
agent-skills/omh-accessibility-audit - omh-adversarial-consensus
agent-skills/omh-adversarial-consensus - omh-agent-debug
agent-skills/omh-agent-debug - omh-agent-instructions
agent-skills/omh-agent-instructions - omh-agent-ops-review
agent-skills/omh-agent-ops-review - omh-ai-job-search
agent-skills/omh-ai-job-search - omh-ai-slop-cleaner
agent-skills/omh-ai-slop-cleaner - omh-app-debugging
agent-skills/omh-app-debugging - omh-apple-design
agent-skills/omh-apple-design - omh-application-threat-model
agent-skills/omh-application-threat-model - omh-apps
agent-skills/omh-apps - omh-ask
agent-skills/omh-ask - omh-award-bar-score
agent-skills/omh-award-bar-score - omh-backend
agent-skills/omh-backend - omh-biomedical-evidence
agent-skills/omh-biomedical-evidence - omh-build-failure-triage
agent-skills/omh-build-failure-triage - omh-cancel
agent-skills/omh-cancel - omh-code-review
agent-skills/omh-code-review - omh-codebase-onboarding
agent-skills/omh-codebase-onboarding - omh-codebase-uml
agent-skills/omh-codebase-uml - omh-codegraph-refresh
agent-skills/omh-codegraph-refresh - omh-commit-pr-authoring
agent-skills/omh-commit-pr-authoring - omh-content-operator
agent-skills/omh-content-operator - omh-context-budget-review
agent-skills/omh-context-budget-review - omh-cto-loop
agent-skills/omh-cto-loop - omh-curriculum-design
agent-skills/omh-curriculum-design - omh-data-analysis
agent-skills/omh-data-analysis - omh-data-pipelines
agent-skills/omh-data-pipelines - omh-data-share-review
agent-skills/omh-data-share-review - omh-decide
agent-skills/omh-decide - omh-decision-prototype
agent-skills/omh-decision-prototype - omh-decision-recall
agent-skills/omh-decision-recall - omh-deliverable-package
agent-skills/omh-deliverable-package - omh-deploy-and-monitor
agent-skills/omh-deploy-and-monitor - omh-design-orchestration
agent-skills/omh-design-orchestration - omh-design-quality-gate
agent-skills/omh-design-quality-gate - omh-docs
agent-skills/omh-docs - omh-external-connector-readiness
agent-skills/omh-external-connector-readiness - omh-failure-signal-audit
agent-skills/omh-failure-signal-audit - omh-feedback-triage
agent-skills/omh-feedback-triage - omh-files
agent-skills/omh-files - omh-finance-analysis
agent-skills/omh-finance-analysis - omh-frontend
agent-skills/omh-frontend - omh-frontend-refactor
agent-skills/omh-frontend-refactor - omh-geospatial-analysis
agent-skills/omh-geospatial-analysis - omh-git-workflow
agent-skills/omh-git-workflow - omh-github-event-ops
agent-skills/omh-github-event-ops - omh-github-issue-intake
agent-skills/omh-github-issue-intake - omh-harness-session-inventory
agent-skills/omh-harness-session-inventory - omh-iac-change
agent-skills/omh-iac-change - omh-idea-to-deploy
agent-skills/omh-idea-to-deploy - omh-image-cards
agent-skills/omh-image-cards - omh-inference-serving
agent-skills/omh-inference-serving - omh-instinct-ledger
agent-skills/omh-instinct-ledger - omh-internal-audit
agent-skills/omh-internal-audit - omh-jit-learn
agent-skills/omh-jit-learn - omh-legal-compliance-review
agent-skills/omh-legal-compliance-review - omh-lifecycle-growth
agent-skills/omh-lifecycle-growth - omh-live-incident-response
agent-skills/omh-live-incident-response - omh-live-info
agent-skills/omh-live-info - omh-llm-app-dev
agent-skills/omh-llm-app-dev - omh-localization-review
agent-skills/omh-localization-review - omh-market-research
agent-skills/omh-market-research - omh-materials-package
agent-skills/omh-materials-package - omh-media-input
agent-skills/omh-media-input - omh-meeting-brief
agent-skills/omh-meeting-brief - omh-memory-new
agent-skills/omh-memory-new - omh-mobile-release
agent-skills/omh-mobile-release - omh-model-finetuning
agent-skills/omh-model-finetuning - omh-molecular-docking
agent-skills/omh-molecular-docking - omh-native-debugging
agent-skills/omh-native-debugging - omh-operating-rhythm
agent-skills/omh-operating-rhythm - omh-ops-observability-card
agent-skills/omh-ops-observability-card - omh-ops-review
agent-skills/omh-ops-review - omh-paper-learning
agent-skills/omh-paper-learning - omh-people-ops
agent-skills/omh-people-ops - omh-physical-device-readiness
agent-skills/omh-physical-device-readiness - omh-plan
agent-skills/omh-plan - omh-product-brief
agent-skills/omh-product-brief - omh-product-discovery-validation
agent-skills/omh-product-discovery-validation - omh-production-audit
agent-skills/omh-production-audit - omh-provider-profile-posture
agent-skills/omh-provider-profile-posture - omh-refactor-plan
agent-skills/omh-refactor-plan - omh-relational-db
agent-skills/omh-relational-db - omh-release-cut
agent-skills/omh-release-cut - omh-reliability-review
agent-skills/omh-reliability-review - omh-report-package
agent-skills/omh-report-package - omh-repro-audit
agent-skills/omh-repro-audit - omh-research-brief
agent-skills/omh-research-brief - omh-rules-distill
agent-skills/omh-rules-distill - omh-run-efficiency
agent-skills/omh-run-efficiency - omh-running-work-board
agent-skills/omh-running-work-board - omh-rust
agent-skills/omh-rust - omh-sales-development
agent-skills/omh-sales-development - omh-sales-pipeline-review
agent-skills/omh-sales-pipeline-review - omh-security-event-response
agent-skills/omh-security-event-response - omh-security-safety-review
agent-skills/omh-security-safety-review - omh-show-reel
agent-skills/omh-show-reel - omh-skill-health
agent-skills/omh-skill-health - omh-skill-scout
agent-skills/omh-skill-scout - omh-source-finder
agent-skills/omh-source-finder - omh-spend-gate
agent-skills/omh-spend-gate - omh-sprite-forge
agent-skills/omh-sprite-forge - omh-support-operations
agent-skills/omh-support-operations - omh-systematic-review
agent-skills/omh-systematic-review - omh-tech-debt-audit
agent-skills/omh-tech-debt-audit - omh-terminal
agent-skills/omh-terminal - omh-toolbelt-readiness
agent-skills/omh-toolbelt-readiness - omh-verification-gate
agent-skills/omh-verification-gate - omh-visual-qa
agent-skills/omh-visual-qa - omh-voice-input
agent-skills/omh-voice-input - omh-web-research
agent-skills/omh-web-research - omh-wiki
agent-skills/omh-wiki - omh-workspace-audit
agent-skills/omh-workspace-audit - ulw-context
agent-skills/ulw-context - ulw-interview
agent-skills/ulw-interview - ulw-loop
agent-skills/ulw-loop - ulw-perf
agent-skills/ulw-perf - ulw-plan
agent-skills/ulw-plan - ulw-qa
agent-skills/ulw-qa - ulw-research
agent-skills/ulw-research - ulw-work
agent-skills/ulw-work - dag-ulw
skills/dag-ulw - omh-accessibility-audit
skills/omh-accessibility-audit - omh-achievements
skills/omh-achievements - omh-adversarial-consensus
skills/omh-adversarial-consensus - omh-agent-board
skills/omh-agent-board - omh-agent-debug
skills/omh-agent-debug - omh-agent-evaluation
skills/omh-agent-evaluation - omh-agent-instructions
skills/omh-agent-instructions - omh-agent-ops-review
skills/omh-agent-ops-review - omh-ai-job-search
skills/omh-ai-job-search - omh-ai-slop-cleaner
skills/omh-ai-slop-cleaner - omh-app-debugging
skills/omh-app-debugging - omh-apple-design
skills/omh-apple-design - omh-application-threat-model
skills/omh-application-threat-model - omh-apps
skills/omh-apps - omh-ask
skills/omh-ask - omh-automation-blueprint
skills/omh-automation-blueprint - omh-award-bar-score
skills/omh-award-bar-score - omh-backend
skills/omh-backend - omh-biomedical-evidence
skills/omh-biomedical-evidence - omh-browser
skills/omh-browser - omh-build-failure-triage
skills/omh-build-failure-triage - omh-buzz
skills/omh-buzz - omh-cancel
skills/omh-cancel - omh-capability-toggle
skills/omh-capability-toggle - omh-code-review
skills/omh-code-review - omh-codebase-onboarding
skills/omh-codebase-onboarding - omh-codebase-uml
skills/omh-codebase-uml - omh-codegraph-refresh
skills/omh-codegraph-refresh - omh-commit-pr-authoring
skills/omh-commit-pr-authoring - omh-content-operator
skills/omh-content-operator - omh-context-budget-review
skills/omh-context-budget-review - omh-cto-loop
skills/omh-cto-loop - omh-curriculum-design
skills/omh-curriculum-design - omh-data-analysis
skills/omh-data-analysis - omh-data-pipelines
skills/omh-data-pipelines - omh-data-share-review
skills/omh-data-share-review - omh-decide
skills/omh-decide - omh-decision-prototype
skills/omh-decision-prototype - omh-decision-recall
skills/omh-decision-recall - omh-deliverable-package
skills/omh-deliverable-package - omh-deploy-and-monitor
skills/omh-deploy-and-monitor - omh-design-orchestration
skills/omh-design-orchestration - omh-design-quality-gate
skills/omh-design-quality-gate - omh-docs
skills/omh-docs - omh-doctor
skills/omh-doctor - omh-executor-runtime-readiness
skills/omh-executor-runtime-readiness - omh-external-connector-readiness
skills/omh-external-connector-readiness - omh-failure-signal-audit
skills/omh-failure-signal-audit - omh-feedback-triage
skills/omh-feedback-triage - omh-files
skills/omh-files - omh-finance-analysis
skills/omh-finance-analysis - omh-frontend
skills/omh-frontend - omh-frontend-refactor
skills/omh-frontend-refactor - omh-gateway-intent-card
skills/omh-gateway-intent-card - omh-geospatial-analysis
skills/omh-geospatial-analysis - omh-git-workflow
skills/omh-git-workflow - omh-github-event-ops
skills/omh-github-event-ops - omh-github-issue-intake
skills/omh-github-issue-intake - omh-harness-session-inventory
skills/omh-harness-session-inventory - omh-iac-change
skills/omh-iac-change - omh-idea-to-deploy
skills/omh-idea-to-deploy - omh-image-cards
skills/omh-image-cards - omh-inference-serving
skills/omh-inference-serving - omh-instinct-ledger
skills/omh-instinct-ledger - omh-internal-audit
skills/omh-internal-audit - omh-jev-action-check
skills/omh-jev-action-check - omh-jev-ask
skills/omh-jev-ask - omh-jev-done-check
skills/omh-jev-done-check - omh-jev-failure-triage
skills/omh-jev-failure-triage - omh-jev-review-gate
skills/omh-jev-review-gate - omh-jev-route
skills/omh-jev-route - omh-jit-learn
skills/omh-jit-learn - omh-legal-compliance-review
skills/omh-legal-compliance-review - omh-lifecycle-growth
skills/omh-lifecycle-growth - omh-live-incident-response
skills/omh-live-incident-response - omh-live-info
skills/omh-live-info - omh-llm-app-dev
skills/omh-llm-app-dev - omh-localization-review
skills/omh-localization-review - omh-long-document-reading
skills/omh-long-document-reading - omh-market-research
skills/omh-market-research - omh-materials-package
skills/omh-materials-package - omh-media-input
skills/omh-media-input - omh-meeting-brief
skills/omh-meeting-brief - omh-memory-new
skills/omh-memory-new - omh-memory-sync
skills/omh-memory-sync - omh-meta-router
skills/omh-meta-router - omh-mobile-release
skills/omh-mobile-release - omh-model-finetuning
skills/omh-model-finetuning - omh-model-optimization
skills/omh-model-optimization - omh-model-setup
skills/omh-model-setup - omh-molecular-docking
skills/omh-molecular-docking - omh-morning-brief
skills/omh-morning-brief - omh-native-debugging
skills/omh-native-debugging - omh-operating-rhythm
skills/omh-operating-rhythm - omh-ops-observability-card
skills/omh-ops-observability-card - omh-ops-review
skills/omh-ops-review - omh-paper-learning
skills/omh-paper-learning - omh-parallel-tools
skills/omh-parallel-tools - omh-people-ops
skills/omh-people-ops - omh-physical-device-readiness
skills/omh-physical-device-readiness - omh-plan
skills/omh-plan - omh-product-brief
skills/omh-product-brief - omh-product-discovery-validation
skills/omh-product-discovery-validation - omh-production-audit
skills/omh-production-audit - omh-prompt-import-readiness
skills/omh-prompt-import-readiness - omh-provider-profile-posture
skills/omh-provider-profile-posture - omh-refactor-plan
skills/omh-refactor-plan - omh-relational-db
skills/omh-relational-db - omh-release-cut
skills/omh-release-cut - omh-reliability-review
skills/omh-reliability-review - omh-report-package
skills/omh-report-package - omh-repro-audit
skills/omh-repro-audit - omh-research-brief
skills/omh-research-brief - omh-research-department
skills/omh-research-department - omh-routing
skills/omh-routing - omh-rules-distill
skills/omh-rules-distill - omh-run-efficiency
skills/omh-run-efficiency - omh-running-work-board
skills/omh-running-work-board - omh-rust
skills/omh-rust - omh-sales-development
skills/omh-sales-development - omh-sales-pipeline-review
skills/omh-sales-pipeline-review - omh-security-event-response
skills/omh-security-event-response - omh-security-safety-review
skills/omh-security-safety-review - omh-show-reel
skills/omh-show-reel - omh-skill
skills/omh-skill - omh-skill-health
skills/omh-skill-health - omh-skill-scout
skills/omh-skill-scout - omh-source-finder
skills/omh-source-finder - omh-spend-gate
skills/omh-spend-gate - omh-sprite-forge
skills/omh-sprite-forge - omh-support-operations
skills/omh-support-operations - omh-systematic-review
skills/omh-systematic-review - omh-tech-debt-audit
skills/omh-tech-debt-audit - omh-terminal
skills/omh-terminal - omh-todo-checklist
skills/omh-todo-checklist - omh-toolbelt-readiness
skills/omh-toolbelt-readiness - omh-verification-gate
skills/omh-verification-gate - omh-visual-qa
skills/omh-visual-qa - omh-voice-input
skills/omh-voice-input - omh-web-research
skills/omh-web-research - omh-websearch-setup
skills/omh-websearch-setup - omh-wiki
skills/omh-wiki - omh-workflow-learning
skills/omh-workflow-learning - omh-workspace-audit
skills/omh-workspace-audit - ulw-context
skills/ulw-context - ulw-interview
skills/ulw-interview - ulw-loop
skills/ulw-loop - ulw-maestro
skills/ulw-maestro - ulw-perf
skills/ulw-perf - ulw-plan
skills/ulw-plan - ulw-qa
skills/ulw-qa - ulw-research
skills/ulw-research - ulw-work
skills/ulw-work
How it works
omh-accessibility-audit
When your agent uses it
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces. Use when the user says: accessibility-audit, accessibility audit, a11y audit, a11y architect, wcag audit, wcag 2.2, wcag 2.2 aa, accessibility pass.
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
2,503 tokensWhen the skill is activated
Reference documents
1,476 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,426 bytesSKILL.mdcore11,426 bytesreferences/a11y-rules.mddoc5,453 bytes
Read SKILL.md
# Accessibility Audit
This is an OMH `accessibility-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`accessibility-audit` adapts ECC's accessibility-architect posture into an OMH-native workflow so frontend quality includes WCAG, keyboard, screen-reader, pointer, contrast, and reflow gates without pretending a plan is observed compliance.
## Do Not Use When
- The user needs initial frontend design or redesign planning before accessibility-specific review; use `omh-frontend` first.
- The user needs rendered layout, screenshot, CJK, or pixel-diff QA rather than accessibility semantics; use `omh-visual-qa`.
- The user needs a broad premium-quality gate across web, deck, PDF, or posters; use `omh-design-quality-gate`.
- The user asks to implement accessibility fixes directly; prepare a selected executor/runtime handoff after the audit or use the coding workflow.View the complete source on GitHubomh-adversarial-consensus
When your agent uses it
[omh] Technical proposal facing adversarial scrutiny: independent perspectives attack a proposal, then distill into a bundle a separate planner consumes. Use when the user says: adversarial-consensus, adversarial planning, adversarial plan review, red team this plan, red-team this plan, red team the proposal, multi-perspective review, multiple perspectives.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
2,410 tokensWhen the skill is activated
Reference documents
1,478 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,509 bytesreferences/consensus-protocol.mddoc6,894 bytes
Read SKILL.md
# Adversarial Consensus
This is an OMH `adversarial-consensus` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`adversarial-consensus` exists because agreement reached by perspectives that read each other is not review — it is convergence. Independent findings, an attack round nobody is allowed to defend against, and a distillation that may only subtract produce objections a single planning pass never surfaces, and the mandatory handoff keeps that bundle from being mistaken for the plan.
## Do Not Use When
- The user wants the plan itself, with options, acceptance criteria, and verification commands; use `ulw-plan`, which this workflow feeds.
- The request is still too ambiguous to state the proposal being attacked; use `ulw-interview` first.
- The user wants completed code reviewed for defects rather than a proposal attacked before it is built; use `omh-code-review`.
- The user wants hostile runtime scenarios against a built change; use `ulw-qa`.View the complete source on GitHubomh-agent-debug
When your agent uses it
[omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action. Use when the user says: agent-debug, agent debug, agent debugging, agent introspection, agent self-debug, self-debug, self debugging, looping agent.
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,667 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,937 bytes
Read SKILL.md
# Agent Debug
This is an OMH `agent-debug` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`agent-debug` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-agent-instructions
When your agent uses it
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
1,753 tokensWhen the skill is activated
Reference documents
1,036 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,090 bytesreferences/instruction-file-method.mddoc4,250 bytes
Read SKILL.md
# Agent Instructions
This is an OMH `agent-instructions` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`agent-instructions` exists because the file every handoff target reads first had no owner: `rules-distill` extracts rule candidates, `codebase-onboarding` builds a human reading path, and `context` aligns terminology, and each reads that file without writing it.
## First Steps
- List every instruction file and which agent reads it before proposing a section.
- Run or ask for the observed run of each command before marking it verified.
## Do Not Use WhenView the complete source on GitHubomh-agent-ops-review
When your agent uses it
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers. Use when the user says: agent-ops-review, agent ops review, agent productivity, operator productivity, manager view, quality dashboard, throughput review, agent work quality.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,612 tokensWhen the skill is activated
Reference documents
801 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,391 bytesSKILL.mdcore7,391 bytesreferences/instrumentation-ladder.mddoc3,615 bytes
Read SKILL.md
# Agent Ops Review
This is an OMH `agent-ops-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`agent-ops-review` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-ai-job-search
When your agent uses it
[omh] Career search to interview: find verified opportunities, tailor evidence-grounded applications and track confirmed outcomes. Use when the user says: ai-job-search, job search, evaluate this job posting, tailor my resume, tailor my cv, prepare for my job interview, track my job applications, draft my cover letter.
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
1,380 tokensWhen the skill is activated
Reference documents
6,875 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/scripts/job_state.py
Files
SKILL.mdcore7,000 bytesSKILL.mdcore7,000 bytesSKILL.mdcore7,000 bytesSKILL.mdcore7,000 bytesreferences/execution-and-qa.mddoc4,032 bytesreferences/fit-and-drafting.mddoc2,507 bytesreferences/interview-and-outcomes.mddoc2,063 bytesreferences/procedure.mddoc4,038 bytesreferences/profile-and-discovery.mddoc3,511 bytestoolkit/LICENSE.upstreamasset1,071 bytestoolkit/README.mddoc17,066 bytestoolkit/examples/synthetic-captures.jsonasset1,341 bytestoolkit/scripts/job_state.pyruns34,247 bytestoolkit/upstream-manifest.jsonasset2,447 bytes
Read SKILL.md
# Ai Job Search
This is an OMH `ai-job-search` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Cross-session career work needs stable posting identity, candidate-evidence links and a strict boundary between prepared applications and confirmed events.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md`; load only the relevant profile/discovery, fit/drafting or interview/outcomes reference for the current action.
- Confirm an approved private workspace outside the product checkout through the active profile; ask only action-specific questions and keep group replies public-safe.
- Actually invoke `toolkit/scripts/job_state.py` through the host terminal: validate captures, merge approved local tracking input, then summary and read-back; produce requested documents rather than stopping at a prepared card.
View the complete source on GitHubomh-ai-slop-cleaner
When your agent uses it
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
2,108 tokensWhen the skill is activated
Reference documents
2,924 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,686 bytesreferences/cleanup-passes.mddoc5,850 bytesreferences/prose-lexicon.mddoc4,452 bytesreferences/ui-review-checklist.mddoc2,521 bytes
Read SKILL.md
# Ai Slop Cleaner
This is an OMH `ai-slop-cleaner` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ai-slop-cleaner` exists to keep `maintenance` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The goal is new or changed behavior rather than removing existing code; a plain refactor, feature, or fix request belongs to `ulw-work`.
- The cleanup would change architecture or module boundaries and needs its execution shaped into phases first; use `omh-refactor-plan`, or `ulw-plan` when the direction itself is still contested.
- The user wants code judged for bugs or merge readiness with no drafted slop removal to inspect; use `omh-code-review` for a bug-first review and `omh-failure-signal-audit` for swallowed failures.
View the complete source on GitHubomh-app-debugging
When your agent uses it
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the demonstrated root cause. Use when the user says: app-debugging, app debugging, application debugging, root cause, root-cause, find the root cause, root cause analysis, flaky test.
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
2,602 tokensWhen the skill is activated
Reference documents
4,727 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,144 bytesreferences/hypothesis-and-race-method.mddoc13,912 bytes../omh-verification-gate/references/test-authoring.mddoc7,914 bytes
Read SKILL.md
# App Debugging
This is an OMH `app-debugging` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`app-debugging` exists because a wrong result in application code had no owner: `native-debugging` covers native binaries, `build-failure-triage` covers red builds, and `agent-debug` covers agent misbehaviour, so the most common debugging request dispatched straight to an execution lane that skipped the diagnosis.
## First Steps
- Ask for, or plan, the one command that shows the wrong behaviour, and record its observed output before naming a cause.
- Refuse to prepare a fix while the reproduction reads not_observed; plan the observation that would establish it instead.
## Do Not Use WhenView the complete source on GitHubomh-apple-design
When your agent uses it
[omh] Designing or reviewing an iOS, macOS, or Apple-style UI: prepare native Apple UI or Apple marketing product-visual direction, review, and improvement briefs with evidence-backed remediation handoffs. Use when the user says: apple-design, apple design, apple ui design, apple hig, human interface guidelines, ios design guidelines, macos app design, apple-inspired web.
What it loads into context
Frontmatter
136 tokensAlways available to the agent
SKILL.md
1,760 tokensWhen the skill is activated
Reference documents
3,781 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,740 bytesSKILL.mdcore8,740 bytesSKILL.mdcore8,740 bytesreferences/materials-and-accessibility.mddoc2,411 bytesreferences/platform-foundations.mddoc2,902 bytesreferences/product-visual-production.mddoc5,101 bytesreferences/review-playbook.mddoc2,405 bytesreferences/web-production-libraries.mddoc4,531 bytes
Read SKILL.md
# Apple Design
This is an OMH `apple-design` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`apple-design` turns Apple UI design, review, and improvement requests into a platform-aware brief that respects native and web differences while preserving OMH's existing implementation and evidence owners.
## Do Not Use When
- The request is generic frontend design, accessibility, screenshot QA, image-card work, or material guidance without an Apple-specific phrase or explicit `omh-apple-design` invocation; use the existing specialist lane.
- The message concerns Apple fruit, stock, support, a glass database, material science, or unrelated Swift/macOS discussion.
- The user needs a conformance, accessibility PASS, or visual PASS claim without supplied and observed evidence.
View the complete source on GitHubomh-application-threat-model
When your agent uses it
[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the security test that proves each control holds. Use when the user says: application-threat-model, application threat model, threat model, threat modeling, threat modelling, threat modeling session, threat modeling workshop, security threat model.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
2,088 tokensWhen the skill is activated
Reference documents
1,147 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,062 bytesreferences/threat-model-method.mddoc5,328 bytes
Read SKILL.md
# Application Threat Model
This is an OMH `application-threat-model` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`application-threat-model` exists because the nearest neighbour does not merely miss this request. `security-safety-review` maps the agent's own prompt, tool, credential, and dependency surface, so an application threat-model request came back as an agent tool inventory under a near-identical name — a confident wrong artifact rather than a miss, in the one domain where that costs most.
## Do Not Use When
- The subject is the agent's own prompts, tools, files, credentials, dependencies, or destructive actions; use `omh-security-safety-review`, which maps that runtime surface.
- The user wants defects found in a diff or a file; use `omh-code-review`.
- The user asks whether a release is ready across rollout, rollback, and observability; use `omh-production-audit`.
- The user asks which commands prove a merge is safe; use `omh-verification-gate`.View the complete source on GitHubomh-apps
When your agent uses it
[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack, Discord, Notion, Linear, Jira, CRM, and similar providers, scoped with auth, payload, confirmation, and result-evidence gates. Use when the user says: connector-operator, connector operator, external app action, external connector action, saas action, api action, send email, email customer.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,807 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,542 bytes
Read SKILL.md
# Connector Operator
This is an OMH `connector-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`connector-operator` exists because an email sent, a ticket written, or an invite delivered cannot be taken back: it scopes the provider, target, and payload, takes a missing connection to the host's own connection setup and respects a skip, and reports delivery only from a provider receipt.
## Do Not Use When
- Only the reply or thread policy of a Discord, Slack, or Telegram conversation is in question.
- The user is choosing or adopting a new provider, MCP server, or integration rather than acting through one; use `omh-external-connector-readiness`.
## ExamplesView the complete source on GitHubomh-ask
When your agent uses it
[omh] Outside AI critique wanted: consulting an external advisor when configured. Use when the user says: ask, external advisor, ask claude, ask gemini, consult claude, consult gemini, opinion from claude, opinion from gemini.
What it loads into context
Frontmatter
109 tokensAlways available to the agent
SKILL.md
1,188 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,647 bytesSKILL.mdcore5,647 bytesSKILL.mdcore5,647 bytes
Read SKILL.md
# Ask
This is an OMH `ask` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ask` exists to put one outside model's critique beside the agent's own answer when the user wants it, as advice the agent weighs in the open rather than a verdict it adopts, from the advisor the user named or configured and never from a default one.
## 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.
- The user wants typed yes/no, pick-one, or scored probabilities from Jev over supplied text.
View the complete source on GitHubomh-award-bar-score
When your agent uses it
[omh] Aiming for design-award quality: score a web surface against published design-award judging axes and name the binding constraint. Use when the user says: award-bar-score, award bar score, award winning, award-winning, award winning website, award-winning website, award winning design, award ready.
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
1,725 tokensWhen the skill is activated
Reference documents
1,703 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,008 bytesreferences/award-judging-model.mddoc6,169 bytes
Read SKILL.md
# Award Bar Score
This is an OMH `award-bar-score` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`award-bar-score` gives "make it award-winning" a measurable meaning: published axes, published weights, a published threshold, and the one axis holding the surface below it — instead of a taste argument nobody can settle.
## Do Not Use When
- The request is broad premium quality across decks, PDFs, or posters; use `omh-design-quality-gate`.
- The request is frontend implementation, layout, or design-system work; use `omh-frontend`.
- The request is WCAG, keyboard, or screen-reader conformance; use `omh-accessibility-audit`.
- The request is a rendered capture or a pixel verdict; use `omh-visual-qa`.View the complete source on GitHubomh-backend
When your agent uses it
[omh] Designing an API, server, or data-layer change: prepare server, API, and data-layer contracts — auth boundary, error paths, response shape, and schema/migration discipline — before implementation. Use when the user says: backend, back-end, back end, backend skill, server side, server-side, api design, api contract.
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
2,597 tokensWhen the skill is activated
Reference documents
6,856 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,058 bytesreferences/consumer-impact.mddoc3,879 bytesreferences/contract-tests.mddoc4,527 bytesreferences/inbound-and-async.mddoc5,790 bytesreferences/schema-migration.mddoc3,299 bytesreferences/service-contract.mddoc14,537 bytes
Read SKILL.md
# Backend
This is an OMH `backend` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`backend` gives OMH a first-class server-side workflow so Hermes can prepare auth boundaries, error paths, response shapes, and migration order without becoming the hidden runtime that executes them.
## Do Not Use When
- The work is the database itself -- a slow query and the index that fixes it, DDL that locks a live table, N+1 queries, or when to partition or shard; use `omh-relational-db`, which owns the lock behaviour and rollback of each statement.
- The request is about web UI, layout, or a design system; use `omh-frontend`.
- The request is a security posture or threat review rather than a service design; use `omh-security-safety-review`.
- The request is to run or judge the verification of an already-built service; use `omh-verification-gate`.View the complete source on GitHubomh-biomedical-evidence
When your agent uses it
[omh] Public variant claims to cross-check: retrieve and reconcile source-labelled biomedical evidence with identity, conflict and freshness checks. Use when the user says: biomedical-evidence, biomedical evidence reconciliation, ClinVar cross-check, variant evidence matrix, BioMCP capture reconciliation.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,489 tokensWhen the skill is activated
Reference documents
3,920 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/scripts/reconcile.py
Files
SKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesSKILL.mdcore7,660 bytesreferences/execution-and-qa.mddoc3,131 bytesreferences/full-contract.mddoc3,242 bytesreferences/procedure.mddoc4,140 bytestoolkit/README.mddoc7,790 bytestoolkit/scripts/reconcile.pyruns19,519 bytestoolkit/upstream-manifest.jsonasset3,060 bytes
Read SKILL.md
# Biomedical Evidence
This is an OMH `biomedical-evidence` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Public sources can disagree about a variant while describing different alleles, diseases or assertion domains. Preserve those differences and their provenance before any synthesis; a fetched record is not a clinical recommendation.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md`; inspect the installed BioMCP version and help before any public retrieval.
- Require public entities only; name exact identifiers, source terms, isolated workspace and a 40-second per-retrieval host timeout before capturing unmodified stdout/stderr.
- Run `toolkit/scripts/reconcile.py` only against a hash-checked local capture envelope; never execute provider text or install an upstream skill pack.
View the complete source on GitHubomh-build-failure-triage
When your agent uses it
[omh] Build or CI failure to triage: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error.
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
2,493 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,005 bytesSKILL.mdcore11,005 bytes
Read SKILL.md
# Build Failure Triage
This is an OMH `build-failure-triage` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`build-failure-triage` adapts ECC's build-fix and PR-test-analysis posture into an OMH-native workflow so failed checks become evidence-backed minimal handoffs instead of ad hoc debugging or false-green verification claims.
## Do Not Use When
- The user needs a pre-merge evidence matrix for passing or missing checks; use `omh-verification-gate`.
- The user needs a code review of changed behavior rather than failing command triage; use `omh-code-review`.
- The user needs broad production readiness; use `omh-production-audit`.
- The user asks for incident or SLO review after deployment; use `omh-reliability-review`.View the complete source on GitHubomh-cancel
When your agent uses it
[omh] Aborting an active workflow: ending active workflow state cleanly. Use when the user says: cancel, stop the workflow, abort the run, cancel the loop.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,335 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,994 bytes
Read SKILL.md
# Cancel
This is an OMH `cancel` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`cancel` exists so a request to stop ends the right thing: OMH clears the state this session owns, and work the host owns stops through the person's own host command, so nothing reads as stopped before a record or the host's own reply says it is.
## Do Not Use When
- The workflow finished and its outcome should be kept; record it with omh state finish instead of clearing it.
- The user wants to see what is still running rather than stop it; use `omh-running-work-board`.
- The user means cancelling something in their own product or accounts, such as an order, a subscription, or a meeting, rather than OMH or host work.
View the complete source on GitHubomh-code-review
When your agent uses it
[omh] Pull request or changes to vet: bug-first review with evidence. Use when the user says: code-review, review, audit, find bugs, release gate, claim audit, evidence audit, README claim.
What it loads into context
Frontmatter
101 tokensAlways available to the agent
SKILL.md
2,300 tokensWhen the skill is activated
Reference documents
7,984 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,633 bytesSKILL.mdcore10,633 bytesreferences/architecture-delta.mddoc5,026 bytesreferences/finding-validation.mddoc3,893 bytesreferences/review-dispatch.mddoc11,603 bytesreferences/review-lenses.mddoc5,315 bytesreferences/review-response.mddoc2,425 bytesreferences/risk-selection.mddoc4,239 bytesreferences/smell-baseline.mddoc4,508 bytes
Read SKILL.md
# Code Review
This is an OMH `code-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`code-review` exists to make review bug-first and evidence-grounded: findings must cite concrete files, diffs, commands, or artifacts before any summary or fix proposal.
## Do Not Use When
- The user asks to implement the fix rather than review existing code or claims.
- There is no diff, file set, claim, artifact, or expected behavior to review.
- The request is broad product critique, strategy, or planning rather than code or evidence review.
View the complete source on GitHubomh-codebase-onboarding
When your agent uses it
[omh] Unfamiliar repository needing a guided tour: create a repo map, reading path, glossary, risk map, and first-task runway for unfamiliar codebases. Use when the user says: codebase-onboarding, codebase onboarding, repo onboarding, repository onboarding, codebase tour, code tour, new repo orientation, understand this repo.
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,725 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,839 bytesSKILL.mdcore7,839 bytesSKILL.mdcore7,839 bytesSKILL.mdcore7,839 bytes
Read SKILL.md
# Codebase Onboarding
This is an OMH `codebase-onboarding` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`codebase-onboarding` adapts ECC's code-tour and onboarding surfaces into an OMH-native first-read workflow so unfamiliar repos become navigable before implementation pressure starts.
## Do Not Use When
- The user already named a concrete implementation task and acceptance criteria; use `ulw-work` or `omh-idea-to-deploy`.
- The user needs a whole-workspace capability inventory; use `omh-workspace-audit`.
- The user wants a code diff review; use `omh-code-review`.
View the complete source on GitHubomh-codebase-uml
When your agent uses it
[omh] Architecture picture of a codebase: turn a repository into one readable, interface-level PlantUML architecture picture - packages or modules, the public symbols other units actually import, bounded import edges - and get it rendered to a single PNG a chat surface can show. Use when the user says: codebase-uml, codebase uml, uml, plantuml, uml diagram, class diagram, package diagram, module diagram.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
2,138 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,250 bytesSKILL.mdcore9,250 bytesSKILL.mdcore9,250 bytes
Read SKILL.md
# Codebase Uml
This is an OMH `codebase-uml` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`codebase-uml` exists so 'visualize our codebase' produces one deterministic, readable picture instead of a hand-drawn guess: the interface each unit exposes is ranked by who imports it, the layout is bounded before PlantUML sees it, and every omission the bounding made is printed on the image.
## Do Not Use When
- The user wants the local code index refreshed or a task-scoped handoff pack, not a picture; use `omh-codegraph-refresh`.
- The user wants a narrative first-read tour, reading path, or glossary; use `omh-codebase-onboarding`.
- The user wants a summary card, thumbnail, or explainer image of a PR, meeting, or release rather than a structural diagram; use `omh-image-cards`.
View the complete source on GitHubomh-codegraph-refresh
When your agent uses it
[omh] Outdated code index or codemap: refresh local code intelligence, summarize repo structure, and prepare task-scoped codegraph handoff context without overclaiming execution. Use when the user says: codegraph-refresh, codegraph refresh, refresh codegraph, update codegraph, codegraph stale, stale codegraph, codegraph handoff, codegraph summary.
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
1,634 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,474 bytes
Read SKILL.md
# Codegraph Refresh
This is an OMH `codegraph-refresh` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`codegraph-refresh` adapts ECC-style codemap freshness into OMH's local codegraph commands so operators can refresh navigation context before handoff without pretending code intelligence is execution evidence.
## Do Not Use When
- The user needs a narrative first-read tour of an unfamiliar repo; use `omh-codebase-onboarding`.
- The user already has accepted implementation criteria and wants code changes; use `ulw-work` or a coding handoff.
- The user asks for visual, frontend, or rendered UI QA; use `omh-frontend`, `omh-design-quality-gate`, or `omh-visual-qa`.
View the complete source on GitHubomh-commit-pr-authoring
When your agent uses it
[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with `Tested:` listing only commands observed to run and everything prepared but not run under `Not-tested:`. Use when the user says: commit-pr-authoring, commit message, commit messages, write the commit message, draft the commit message, commit body, squash message, pr body.
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,939 tokensWhen the skill is activated
Reference documents
1,274 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,671 bytesreferences/commit-and-pr-conventions.mddoc5,419 bytes
Read SKILL.md
# Commit Pr Authoring
This is an OMH `commit-pr-authoring` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`commit-pr-authoring` exists because nothing in the catalog authored the commit or the PR body. `code-review` reads a commit message as a thing to review and `github-event-ops` routes PR events, so the text an engineer writes several times a day had no owner, and nothing applied the observed-versus-prepared split to it.
## First Steps
- Read the PR template and the recent log, and record the convention before drafting.
- Build the evidence ledger: each command, observed with its exit status or not_observed.
## Do Not Use WhenView the complete source on GitHubomh-content-operator
When your agent uses it
[omh] Product or company copy to publish or rewrite: scope publish-ready writing, rewriting, summarization, translation, release-note, newsletter, customer-copy, social-copy, README-copy, and email-draft work with audience, tone, style, source, review, and hallucination gates. Use when the user says: content-operator, content operator, content workflow, writing workflow, publish-ready writing, publish ready writing, release notes, release note draft.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,679 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,897 bytesSKILL.mdcore7,897 bytesSKILL.mdcore7,897 bytesSKILL.mdcore7,897 bytesSKILL.mdcore7,897 bytesSKILL.mdcore7,897 bytes
Read SKILL.md
# Content Operator
This is an OMH `content-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`content-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-context-budget-review
When your agent uses it
[omh] Context window or token budget at risk: plan compact context, token/cost budgets, summarization checkpoints, and overflow recovery before long agent work. Use when the user says: context-budget-review, context budget review, context budget, token budget review, token budget, prompt budget, prompt caching, prompt cache.
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,870 tokensWhen the skill is activated
Reference documents
378 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,912 bytesSKILL.mdcore8,912 bytesreferences/cache-placement.mddoc1,855 bytes
Read SKILL.md
# Context Budget Review
This is an OMH `context-budget-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`context-budget-review` ports ECC's context-budget and token-budget instincts into OMH as a compactness gate that protects long-running work without redefining success around a smaller task.
## Do Not Use When
- The user asks only what this Hermes session has used or cost so far; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user asks to continue a loopable goal; use `ulw-loop` unless budget planning is the explicit blocker.
- The task is a short one-step answer with no meaningful context risk.
View the complete source on GitHubomh-cto-loop
When your agent uses it
[omh] Engineering leadership over roadmap and risk: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence. Use when the user says: cto-loop, cto loop, cto, cto pm, pm dev qa security ops, roadmap technical tradeoffs, technical tradeoff, delivery risk.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,216 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,786 bytes
Read SKILL.md
# Cto Loop
This is an OMH `cto-loop` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`cto-loop` exists to keep `leadership` 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 a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly or use `omh-decide` for a decision brief instead of starting a leadership operating loop.
## Examples
View the complete source on GitHubomh-curriculum-design
When your agent uses it
[omh] Team training or course that needs a syllabus: turn a learning goal into a teachable curriculum, assessment plan, and learner-ready sequence. Use when the user says: curriculum design, learning objectives, assessment plan, 커리큘럼 설계, 학습 목표, 평가 계획.
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
1,277 tokensWhen the skill is activated
Reference documents
1,493 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,262 bytesreferences/procedure.mddoc7,012 bytes
Read SKILL.md
# Curriculum Design
This is an OMH `curriculum-design` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`curriculum-design` makes outcomes, sequence, assessment, and constraints reviewable before materials or LMS work.
## Do Not Use When
- The user wants an explanation of a supplied academic paper rather than a teachable sequence; use `omh-paper-learning`.
- The user needs a deck, workbook, PDF, or other exported learning artifact; route packaging to `omh-materials-package` after the curriculum is accepted.
- The user asks to create or publish an LMS course, enroll students, grade work, or change course settings; use `omh-apps` with explicit authorization and observed evidence.
- The user needs only a short rewrite or one isolated worksheet prompt, not curriculum structure; use `omh-content-operator`.View the complete source on GitHubomh-data-analysis
When your agent uses it
[omh] Dataset or table to analyze: scope supplied data with provenance, causal-claim, and hallucination guards. Use when the user says: data-analysis, data analysis, dataset analysis, csv analysis, json analysis, log analysis, table analysis, analyze csv.
What it loads into context
Frontmatter
112 tokensAlways available to the agent
SKILL.md
1,497 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,063 bytes
Read SKILL.md
# Data Analysis
This is an OMH `data-analysis` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`data-analysis` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-data-pipelines
When your agent uses it
[omh] Data pipeline work -- an ETL or streaming job, a backfill or replay, duplicate events, a schema change downstream, a lineage question, a data-quality regression: make every rerun idempotent, bound every replay, and gate each load on observed checks. Use when the user says: data-pipelines, data pipeline, data pipelines, etl, elt, etl pipeline, etl job, etl backfill.
What it loads into context
Frontmatter
153 tokensAlways available to the agent
SKILL.md
1,959 tokensWhen the skill is activated
Reference documents
589 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,689 bytesSKILL.mdcore8,689 bytesreferences/pipeline-method.mddoc2,587 bytes
Read SKILL.md
# Data Pipelines
This is an OMH `data-pipelines` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`data-pipelines` exists because pipeline work had no owner: `backend` owns a service's schema migration, `data-analysis` analyzes data it is handed, and `relational-db` owns a database's locks and indexes, while a backfill that duplicated events or a schema change with unknown readers reached memory and event lanes with no idempotency contract or replay bound at all.
## First Steps
- Ask what makes a row unique at the sink before planning any rerun.
- Bound the window and the targets before ordering any replay or backfill step.
## Do Not Use WhenView the complete source on GitHubomh-data-share-review
When your agent uses it
[omh] Before data leaves the team -- a dataset, log, ticket export or transcript excerpt bound for a vendor, a public issue, a model provider or a training corpus: classify every field, minimize first, pseudonymize with the mapping kept local, and call it redacted only after an observed residual scan. Use when the user says: data-share-review, data share review, pii redaction, redact pii, pseudonymize, de-identify, anonymize the dataset, residual pii.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
2,453 tokensWhen the skill is activated
Reference documents
969 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,788 bytesreferences/data-share-method.mddoc4,235 bytes
Read SKILL.md
# Data Share Review
This is an OMH `data-share-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`data-share-review` exists because data leaving the team had no owner: Hermes redacts identifiers in gateway chat and secrets in tool output, `omh-security-safety-review` reviews an agent's own exposure, and `omh-legal-compliance-review` reads the obligations, while nothing minimized a file's fields, kept its pseudonym mapping local, and refused to call it redacted before a scan of what actually leaves.
## First Steps
- Ask where the file goes and what the destination needs it for before touching a field.
- Inventory the fields from the header and the schema before planning any masking.
## Do Not Use WhenView the complete source on GitHubomh-decide
When your agent uses it
[omh] Team or business decision between options: tradeoffs, a recommendation, and a decision note you can act on. Use when the user says: strategy-brief, strategy brief, strategy memo, product strategy, strategic options, decision note, leadership strategy, next strategy.
What it loads into context
Frontmatter
111 tokensAlways available to the agent
SKILL.md
1,447 tokensWhen the skill is activated
Reference documents
1,557 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,886 bytesreferences/capacity-planning.mddoc3,369 bytesreferences/decision-records.mddoc3,505 bytes
Read SKILL.md
# Strategy Brief
This is an OMH `strategy-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`strategy-brief` exists to keep `strategy` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The strategic question is whether an early idea's customer problem and segment are real, and no validated discovery receipt exists yet; use `omh-product-discovery-validation`.
- The question is how to run a hiring process — scorecards, interview loops, candidate comparison — rather than whether to hire at all; use `omh-people-ops`.
- The user wants Jev's typed probabilities for a yes/no, pick-one, or scored question over supplied text rather than tradeoffs and a recommendation.
View the complete source on GitHubomh-decision-prototype
When your agent uses it
[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
2,317 tokensWhen the skill is activated
Reference documents
2,548 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,007 bytesreferences/artifact-shapes.mddoc4,675 bytesreferences/procedure.mddoc7,772 bytes
Read SKILL.md
# Decision Prototype
This is an OMH `decision-prototype` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`decision-prototype` exists so one empirical uncertainty can be settled by a bounded, disposable experiment instead of endless interviewing or an experiment hidden inside production work; it records observed results apart from interpretation and feeds planning a receipt without claiming the prototype is implementation-ready.
## Do Not Use When
- $context is the explicit-only route for a repository terminology or product decision frontier (`ulw-context`); preference or policy decisions that behavior cannot test stay with `ulw-interview`.
- $context is the explicit-only route for unresolved repository terminology or project language (`ulw-context`); hand only an empirical decision here.
- The decision is already made and the request is an implementation plan with acceptance criteria; use `ulw-plan` and consume the decision receipt there.
- The user wants the feature built, reviewed, or shipped rather than one question answered; use `ulw-work` after an accepted plan.View the complete source on GitHubomh-decision-recall
When your agent uses it
[omh] Previously rejected options to revisit: recall scoped reviewed rejected decisions without elevating them to approved memory. Use when the user says: decision-recall, rejected decision recall, rejected decisions, why was this rejected, previously rejected alternative, 거절된 결정, 기각된 대안.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,171 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,633 bytesSKILL.mdcore5,633 bytes
Read SKILL.md
# Decision Recall
This is an OMH `decision-recall` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`decision-recall` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-deliverable-package
When your agent uses it
[omh] Attachment and deliverable status tracking: track PPT, PDF, XLSX, DOCX, HWP, Markdown, and attachments through prepared, generated, QA, approved, attached, archived, and published states. Use when the user says: deliverable-package, deliverable mode, file attachment, attach file, attachment status, file delivery, file deliverable status, generated file.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,761 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,241 bytesSKILL.mdcore8,241 bytesSKILL.mdcore8,241 bytes
Read SKILL.md
# Deliverable Package
This is an OMH `deliverable-package` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`deliverable-package` exists because a requested file moves through prepared, generated, QA-checked, approved, and attached states that no single tool reports together: it tracks each file through them and reports a state only from that state's own evidence, never from an earlier one's.
## Do Not Use When
- Planning a deck, PDF, workbook, or document from source inputs before any file exists (its outline, target formats, and QA ladder); use `omh-materials-package`.
- A text-only report, executive brief, or slide outline with no file to produce; use `omh-report-package`.
## ExamplesView the complete source on GitHubomh-deploy-and-monitor
When your agent uses it
[omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status. Use when the user says: deploy-and-monitor, deploy and monitor, deploy monitor, deployment monitoring, release monitor, post deploy, post-deploy, rollback.
What it loads into context
Frontmatter
118 tokensAlways available to the agent
SKILL.md
1,660 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,903 bytesSKILL.mdcore7,903 bytes
Read SKILL.md
# Deploy And Monitor
This is an OMH `deploy-and-monitor` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`deploy-and-monitor` exists to keep `monitoring` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- An incident has already been declared and the work is commanding it -- severity, commander, running timeline, recovery verification -- rather than watching a release; use `omh-live-incident-response`.
- The ask is deciding a release before it ships -- what goes in, its version and tag, the canary stages, or which command rolls it back; use `omh-release-cut`, which writes the rollback trigger down before it is needed.
- The change is to declared infrastructure itself -- a Terraform plan, a Kubernetes manifest, a Helm chart -- and needs its drift, blast radius, and cost delta read before it is applied; use `omh-iac-change`.
View the complete source on GitHubomh-design-orchestration
When your agent uses it
[omh] Entire product design problem to delegate: prepare a bounded design direction, existing-lane composition, and executor-neutral handoff. Use when the user says: design-orchestration, design orchestration, design ownership, handle this product design, take on the design, デザインを任せる, デザイン全体を任せ, プロダクトデザインを任せ.
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
1,691 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,205 bytes
Read SKILL.md
# Design Orchestration
This is an OMH `design-orchestration` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`design-orchestration` lets Hermes users say that they want design handled without making them manually compose four specialist lanes or confusing preparation with completed visual work.
## Do Not Use When
- The request is directly about premium multi-format quality or publishing; use `omh-design-quality-gate`.
- The request is directly about frontend implementation, layout, responsive behavior, or a design system; use `omh-frontend`.
- The request is directly about WCAG, keyboard, screen-reader, or semantic accessibility; use `omh-accessibility-audit`.
- The request is directly about screenshots, visual regression, pixel diff, rendered layout, or a verdict; use `omh-visual-qa`.View the complete source on GitHubomh-design-quality-gate
When your agent uses it
[omh] Deliverable demands premium polish: enforce superior content, design, layout, publishing, and visual QA gates. Use when the user says: design-quality-gate, design quality gate, ui ux pro max, design pro max, frontend pro max, visual qa pro, premium design, high quality design.
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,967 tokensWhen the skill is activated
Reference documents
1,459 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,156 bytesSKILL.mdcore9,156 bytesSKILL.mdcore9,156 bytesreferences/design-critique-rubric.mddoc6,276 bytes
Read SKILL.md
# Design Quality Gate
This is an OMH `design-quality-gate` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`design-quality-gate` makes high-stakes visual deliverables premium and trustworthy by treating taste, content, layout, accessibility, and render QA as first-class evidence.
## Do Not Use When
- Basic image prompt card only; use `omh-image-cards`.
- The artifact is a throwaway probe whose quality is irrelevant to the decision it answers; use `omh-decision-prototype`.
- Ordinary file packaging/export plan only; use `omh-materials-package` or `omh-deliverable-package`.
- Pure backend, CLI, data, or text-only research with no visual surface.View the complete source on GitHubomh-docs
When your agent uses it
[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory. Use when the user says: product-docs, OMH documentation, oh-my-hermes documentation, what is OMH, what is oh-my-hermes, how does OMH work, OMH capability catalog, OMH skill catalog.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,439 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,974 bytesSKILL.mdcore6,974 bytesSKILL.mdcore6,974 bytesSKILL.mdcore6,974 bytesSKILL.mdcore6,974 bytesSKILL.mdcore6,974 bytes
Read SKILL.md
# Product Docs
This is an OMH `product-docs` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`omh-docs` gives Hermes one bounded, source-first way to explain OMH itself without turning product questions into generic workflow routing or silently changing the user's installation.
## Do Not Use When
- The user wants generic documentation writing, editing, or summarization unrelated to OMH.
- The question is about OpenAI or Hermes Agent rather than OMH; use that product's official documentation skill.
- The user wants setup or repair.
- The user wants to install, update, remove, or edit catalog skills.View the complete source on GitHubomh-external-connector-readiness
When your agent uses it
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
3,454 tokensWhen the skill is activated
Reference documents
720 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore16,529 bytesreferences/memory-provider-trial.mddoc3,408 bytes
Read SKILL.md
# External Connector Readiness
This is an OMH `external-connector-readiness` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`external-connector-readiness` exists because adopting a plugin, connector, API, or memory provider changes what the agent can reach, spend, and remember, and a host's install-time scan or a vendor's docs answer only part of that: it scores capability, auth, cost, freshness, safety, and fallback for each candidate, and reports a trial only from what was observed.
## Do Not Use When
- Choosing which coding owner runs a task.
- Finding which tool, credential, or install is missing for work already chosen; use `omh-toolbelt-readiness`.
- A read-only live lookup or an external write through a connector already adopted; use `omh-live-info` or `omh-apps`.
View the complete source on GitHubomh-failure-signal-audit
When your agent uses it
[omh] Hidden or swallowed errors suspected: find swallowed errors, unsafe fallbacks, hidden UI/runtime failures, and missing propagation before they become false green status. Use when the user says: failure-signal-audit, failure signal audit, silent failure, silent failures, silent failure hunter, swallowed error, swallowed errors, empty catch.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,707 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,144 bytesSKILL.mdcore8,144 bytesSKILL.mdcore8,144 bytesSKILL.mdcore8,144 bytes
Read SKILL.md
# Failure Signal Audit
This is an OMH `failure-signal-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`failure-signal-audit` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-feedback-triage
When your agent uses it
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow. Use when the user says: feedback-triage, customer-feedback-triage, feedback triage, customer feedback, feedback cluster, bug or feature, feature request triage, payment failure feedback.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,319 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,307 bytesSKILL.mdcore6,307 bytesSKILL.mdcore6,307 bytesSKILL.mdcore6,307 bytesSKILL.mdcore6,307 bytesSKILL.mdcore6,307 bytes
Read SKILL.md
# Feedback Triage
This is an OMH `feedback-triage` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`feedback-triage` exists to keep customer and community signals from jumping straight into roadmap or coding; it clusters evidence, ranks signals, and chooses the next workflow.
## Do Not Use When
- The request already contains an accepted product decision and asks for implementation.
- There are no feedback items, source boundary, or product area to classify.
- The user wants current market research rather than triage of supplied signals.
- The triage result asks for a retention or activation intervention rather than another cluster; use `omh-lifecycle-growth`.View the complete source on GitHubomh-files
When your agent uses it
[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,911 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,105 bytes
Read SKILL.md
# Workspace File Operator
This is an OMH `workspace-file-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`workspace-file-operator` exists because a delete, overwrite, or bulk move often has no undo point: it scopes the path, confirms each destructive step, records beforehand whether a checkpoint covers the target (Hermes takes none unless checkpoints are on), and reports only what file evidence shows.
## Do Not Use When
- An ordinary list, search, read, or one-file edit inside a known folder; use the native file tools directly.
- The request converts files or produces a deck, PDF, or attachment; use `omh-materials-package` or `omh-deliverable-package`.
## ExamplesView the complete source on GitHubomh-finance-analysis
When your agent uses it
[omh] Company budget overrun, cash risk, or close issue: turn finance and accounting inputs into a decision-ready variance, cash, and close-risk brief. Use when the user says: finance analysis, budget variance, budget vs actual, month-end close, 재무 분석, 예산 대비 실적, 월마감.
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,335 tokensWhen the skill is activated
Reference documents
1,267 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,405 bytesSKILL.mdcore6,405 bytesSKILL.mdcore6,405 bytesSKILL.mdcore6,405 bytesreferences/procedure.mddoc5,962 bytes
Read SKILL.md
# Finance Analysis
This is an OMH `finance-analysis` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`finance-analysis` prepares a source-bounded decision brief without claiming an authoritative financial action.
## Do Not Use When
- The request is for a current quote, exchange rate, crypto price, or other live market lookup; use `omh-live-info`.
- The user wants generic exploration of a supplied CSV or table without accounting periods, controls, or finance decision framing; use `omh-data-analysis`.
- The user asks to post journal entries, reconcile accounts, approve payments, submit tax filings, or configure an accounting system; use `omh-apps` for an explicit observed action path.
- The user wants pipeline coverage, deal health, or a seller forecast scenario rather than authoritative revenue or close reporting; use `omh-sales-pipeline-review`.View the complete source on GitHubomh-frontend
When your agent uses it
[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
4,456 tokensWhen the skill is activated
Reference documents
19,522 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore20,306 bytesSKILL.mdcore20,306 bytesSKILL.mdcore20,306 bytesSKILL.mdcore20,306 bytesSKILL.mdcore20,306 bytesreferences/chart-styling.mddoc5,026 bytesreferences/component-registry-adoption.mddoc8,923 bytesreferences/design-system-contract.mddoc12,739 bytesreferences/forms-and-input.mddoc8,728 bytesreferences/reference-token-extraction.mddoc2,835 bytesreferences/rendered-scene-craft.mddoc3,980 bytesreferences/screenshot-loop.mddoc5,533 bytesreferences/scroll-motion-libraries.mddoc7,119 bytesreferences/taste-foundations.mddoc11,519 bytesreferences/tui-craft.mddoc6,678 bytesreferences/web-vitals-budgets.mddoc3,688 bytes../omh-verification-gate/references/test-authoring.mddoc7,914 bytes
Read SKILL.md
# Frontend
This is an OMH `frontend` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`frontend` gives OMH a first-class web UI creation and polishing workflow so Hermes can prepare high-quality layout, design-system, accessibility, performance, and visual-QA handoffs without becoming the hidden coding or browser runtime.
## Do Not Use When
- The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `omh-design-quality-gate`.
- The user wants a disposable wireframe or mocked interaction to settle one interaction question before planning; use `omh-decision-prototype`.
- The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `omh-materials-package` or `omh-deliverable-package`.
- The user only needs an image card or infographic prompt; use `omh-image-cards`.View the complete source on GitHubomh-frontend-refactor
When your agent uses it
[omh] Oversized or tangled UI component: behavior-preserving refactor of UI code - preview the full change plan first, apply as a second explicit step, and work impact-ordered from state architecture down to naming polish. Use when the user says: frontend-refactor, front-refactor, frontend refactor, refactor this component, refactor the component, refactor my component, component refactor, react refactor.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,897 tokensWhen the skill is activated
Reference documents
1,875 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,982 bytesreferences/refactor-passes.mddoc4,636 bytesreferences/state-discipline.mddoc3,746 bytes
Read SKILL.md
# Frontend Refactor
This is an OMH `frontend-refactor` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`frontend-refactor` exists so UI restructuring runs as a previewed, behavior-locked, impact-ordered process instead of ad-hoc rewrites: the plan comes before any edit, state fixes come before polish, and every change carries its safety reason.
## Do Not Use When
- The target is not UI code, or the smell is generic slop, duplication, or dead code outside a component tree; use `omh-ai-slop-cleaner`.
- The user wants new UI built or redesigned rather than restructured; use `omh-frontend`.
- The user wants findings and a verdict without changing the code; use `omh-code-review`.
- The restructuring crosses module boundaries or changes architecture beyond the component tree; use `omh-refactor-plan` for the phased execution shape, or `ulw-plan` first when the direction itself is still contested.View the complete source on GitHubomh-geospatial-analysis
When your agent uses it
[omh] Spatial layers to intersect: execute CRS-safe polygon overlay with measured areas, validated geometry and reproducible GeoJSON outputs. Use when the user says: geospatial-analysis, geospatial overlay, spatial intersection, intersect geojson layers, compute overlap area.
What it loads into context
Frontmatter
112 tokensAlways available to the agent
SKILL.md
1,523 tokensWhen the skill is activated
Reference documents
3,778 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/scripts/analyze.py
Files
SKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesSKILL.mdcore7,631 bytesreferences/execution-and-qa.mddoc4,427 bytesreferences/full-contract.mddoc3,113 bytesreferences/procedure.mddoc3,655 bytestoolkit/LICENSE.upstreamasset1,305 bytestoolkit/README.mddoc6,412 bytestoolkit/examples/input.jsonasset501 bytestoolkit/examples/overlay.jsonasset351 bytestoolkit/scripts/analyze.pyruns17,267 bytestoolkit/upstream-manifest.jsonasset3,163 bytes
Read SKILL.md
# Geospatial Analysis
This is an OMH `geospatial-analysis` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Polygon computations can return plausible but wrong numbers when CRS, coordinate units or geometry are invalid. This skill couples fail-closed checks to a runnable optional overlay producer and inspectable replay artifacts.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md` before executing `toolkit/scripts/analyze.py`; installation and skill discovery never run it.
- Confirm the two layers, explicit EPSG declarations, study extent, projected metre CRS, output directory and finite host timeout; never guess a missing CRS.
- Use the original synthetic rectangle fixture only for backend QA; do not describe it as a public flood, facility or site-suitability finding.
View the complete source on GitHubomh-git-workflow
When your agent uses it
[omh] Git branch in trouble -- a merge conflict, a commit that broke something, history to repair: plan the resolution, the bisect, or the rewrite, name what is already pushed first, and force-push only with `--force-with-lease`. Use when the user says: git-workflow, git workflow, merge conflict, merge conflicts, rebase conflict, resolve the conflict, resolve this conflict, conflict markers.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,906 tokensWhen the skill is activated
Reference documents
1,074 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,451 bytesreferences/git-repair-method.mddoc4,304 bytes
Read SKILL.md
# Git Workflow
This is an OMH `git-workflow` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`git-workflow` exists because conflict resolution, bisect, and history repair had no owner: "resolve this merge conflict" reached a file operator and "clean up this branch's history" a live-information lane, while this repository's own incidents -- a stack that replayed its base commits, a commit landing on another session's branch -- each had a known correct procedure.
## First Steps
- Name what is already pushed: each branch involved with its local head, its remote head, and whether others may have fetched it.
- Before any step that rewrites history, name its recovery point.
## Do Not Use WhenView the complete source on GitHubomh-github-event-ops
When your agent uses it
[omh] Incoming GitHub PR, issue, or CI event: GitHub event operations: route PR, issue, CI, and review webhook events into triage, review, or fix handoff cards. Use when the user says: github-event-ops, github event ops, github ops, github triage, github pr, github review, github action, github actions.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,700 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,569 bytes
Read SKILL.md
# Github Event Ops
This is an OMH `github-event-ops` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`github-event-ops` exists because a GitHub event arrives as a payload, not a decision: it sorts the event into review, triage, or a fix hand-off, re-reads remote state rather than trusting the payload, and never reports a label, rerun, or review the run did not observe.
## Do Not Use When
- One issue to file from a bug report or an idea, with no incoming event to route; use `omh-github-issue-intake`.
- A failing build log to diagnose, with no event routing left to decide; use `omh-build-failure-triage`.
- The event is a security advisory, a CVE in a dependency, or a leaked credential; use `omh-security-event-response`, which orders containment and closes only on an observed rotation or fix.
- The PR is a dependabot or renovate version bump with no advisory; use `omh-refactor-plan`, which decides whether it is safe to merge from the breaking changes against this repository's call sites.View the complete source on GitHubomh-github-issue-intake
When your agent uses it
[omh] Chat report that should become a GitHub issue: turn a public chat report into a confirmed, verified issue package. Use when the user says: github-issue-intake, github issue intake, issue intake, file this as an issue, file a github issue, open a github issue, create a github issue, submit a github issue.
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
1,944 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,307 bytesSKILL.mdcore9,307 bytesSKILL.mdcore9,307 bytes
Read SKILL.md
# Github Issue Intake
This is an OMH `github-issue-intake` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`github-issue-intake` exists so a public support-chat report can become a verified GitHub issue through one bounded, confirmation-gated lane instead of ad hoc chat narration or an unscoped bot write.
## Do Not Use When
- The report only wants classification or signal clustering; use feedback-triage instead.
- The event concerns an already-existing issue, PR, review, or CI run; use github-event-ops instead.
- The user wants implementation; coding stays a separate follow-up lane with its own maintainer authority.
- The report describes a security vulnerability; redirect to the private SECURITY.md path.View the complete source on GitHubomh-harness-session-inventory
When your agent uses it
[omh] Lost track of agent sessions and worktrees: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory.
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
1,584 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,431 bytesSKILL.mdcore7,431 bytesSKILL.mdcore7,431 bytes
Read SKILL.md
# Harness Session Inventory
This is an OMH `harness-session-inventory` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`harness-session-inventory` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-iac-change
When your agent uses it
[omh] Infrastructure-as-code change -- Terraform, OpenTofu, Pulumi, a Kubernetes manifest, a Helm chart: read the drift, the blast radius and the cost delta from the saved plan, then stage the apply behind a health gate with a rollback per stage. Use when the user says: iac-change, iac change, infrastructure as code, infrastructure-as-code, terraform plan, terraform apply, terraform state, terraform drift.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,974 tokensWhen the skill is activated
Reference documents
694 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,970 bytesreferences/iac-change-method.mddoc2,991 bytes
Read SKILL.md
# Iac Change
This is an OMH `iac-change` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`iac-change` exists because infrastructure changes had no owner: `deploy-and-monitor` watches an application release, `release-cut` decides one, and `inference-serving` deploys a model server, while a Terraform plan with drift, a Helm chart change, or a manifest edit reached a generic planner with no blast radius, cost delta, or staged apply at all.
## First Steps
- Ask for the saved plan or the diff output before assessing anything.
- Separate existing drift from the proposed change before ordering stages.
## Do Not Use WhenView the complete source on GitHubomh-idea-to-deploy
When your agent uses it
[omh] App idea headed for launch: shape an app idea into decisions, delivery handoff, verification, release, and monitoring status. Use when the user says: idea-to-deploy, idea to deploy, from idea to deploy, plan to deploy, idea to launch, ship this idea, ship this feature, launch this feature.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,512 tokensWhen the skill is activated
Reference documents
1,771 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,161 bytesreferences/project-bootstrap.mddoc8,329 bytes
Read SKILL.md
# Idea To Deploy
This is an OMH `idea-to-deploy` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`idea-to-deploy` exists to keep `delivery` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The task is already a concrete repo change whose stopping point is one PR-ready cycle, not product or release operations; use `ulw-work`.
- The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly instead of opening a product delivery loop.
## ExamplesView the complete source on GitHubomh-image-cards
When your agent uses it
[omh] Infographic card for meeting notes, a report, or PR: image prompt cards - turn meetings, reports, PRs, issues, research, and releases into domain-aware image prompt cards. Use when the user says: img-summary, img summary, visual prompt card, image card, image generation, image edit, edit this image, remove the background.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
2,881 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytesSKILL.mdcore13,473 bytes
Read SKILL.md
# Img Summary
This is an OMH `img-summary` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`img-summary` exists so Hermes can turn common communication work into provider-neutral image-card prompts while adapting format, domain mood, background, texture, lighting, camera, and poster grammar, and keeping generation, QA, and delivery as observed-only evidence.
## Do Not Use When
- The user needs a deck, PDF, spreadsheet, HWP, Markdown package, or binary file export plan; use `omh-materials-package`.
- The user wants a text-only report, leadership brief, or PPT-ready outline; use `omh-report-package`.
- The user asks OMH to directly generate, inspect, upload, or post an image without a wrapper-supplied observed evidence path.
View the complete source on GitHubomh-inference-serving
When your agent uses it
[omh] Self-hosted LLM serving on GPUs: choose the serving engine and quantization from decision tables, prepare deployment as an idempotent runbook with observed-only verification, and measure the endpoint with the standard TTFT/TPOT/goodput protocol. Use when the user says: inference-serving, inference serving, serve this model, serve the model, model serving, serving endpoint, vllm, llama.cpp.
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
1,846 tokensWhen the skill is activated
Reference documents
1,424 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,248 bytesreferences/serving-bench.mddoc2,279 bytesreferences/serving-runbooks.mddoc3,547 bytes
Read SKILL.md
# Inference Serving
This is an OMH `inference-serving` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`inference-serving` exists so serving an LLM runs as one decided, gated, measured process instead of scattered flag folklore: the engine choice is a table, the deployment is an idempotent runbook whose only completion evidence is the observed verification, and the benchmark speaks the standard metric vocabulary.
## Do Not Use When
- A new model generation needs recognition, calibration, routing, and pricing onboarding.
- The user wants their own machine's model routing or providers configured.
- The question is whether a coding runtime/executor can run at all.
- The goal is application or system performance rather than the serving endpoint itself; use `ulw-perf`.View the complete source on GitHubomh-instinct-ledger
When your agent uses it
[omh] Recurring lessons worth promoting: turn repeated project or cross-project lessons into atomic, confidence-scored instinct candidates with scoped promotion and export boundaries. Use when the user says: instinct-ledger, instinct ledger, project instincts, project-scoped instincts, project scoped instincts, global instincts, instinct review, instinct candidate.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,584 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,605 bytesSKILL.mdcore7,605 bytes
Read SKILL.md
# Instinct Ledger
This is an OMH `instinct-ledger` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`instinct-ledger` exists because a lesson seen once is an anecdote and one seen across runs or projects is a candidate rule: it records each as one atomic instinct with its trigger, action, scope, confidence, and evidence, and promotes one only through a reviewed store route, never by writing a host's memory or skills on its own.
## Do Not Use When
- A single missed route or one run's trace.
- Writing reviewed lessons into AGENTS guidance, prompts, or skills; use `omh-rules-distill`.
- A run that is stuck right now; use `omh-agent-debug` before drawing a lesson from it.
View the complete source on GitHubomh-internal-audit
When your agent uses it
[omh] Testing an internal control -- SOX, ICFR or ITGC: define the population and the sample, name the evidence that proves each item, re-perform the control, and grade any deficiency from stated likelihood, magnitude and compensating-control criteria, never by assertion. Use when the user says: internal-audit, internal audit, internal control, internal controls, internal control audit, control testing, test of controls, tests of controls.
What it loads into context
Frontmatter
151 tokensAlways available to the agent
SKILL.md
1,892 tokensWhen the skill is activated
Reference documents
549 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,114 bytesSKILL.mdcore9,114 bytesreferences/control-audit-method.mddoc2,540 bytes
Read SKILL.md
# Internal Audit
This is an OMH `internal-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`internal-audit` exists because control-testing methodology had no owner: `finance-analysis` reports figures and names control exceptions, `tech-debt-audit` audits code, and `production-audit` audits a release, while population, sampling, re-performance, and deficiency severity had nothing that derived a grade from criteria.
## First Steps
- Ask what the control is meant to prevent or detect, and over which population and period it operates.
- Ask for the sampling guidance and the materiality threshold before sizing any sample or grading anything.
## Do Not Use WhenView the complete source on GitHubomh-jit-learn
When your agent uses it
[omh] Blocked on a project by a knowledge gap: just-in-time learning workflow: select and confirm an immediate learning target, research credible sources, and prepare an application-first brief without popularity ranking. Use when the user says: jit-learn, learn next, learn now, blocker-specific learning target, highest-leverage learning target, immediate learning payoff, immediately applicable learning brief, source-backed learning brief.
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,872 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytesSKILL.mdcore9,333 bytes
Read SKILL.md
# Jit Learn
This is an OMH `jit-learn` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`jit-learn` exists to choose what is worth learning for the user's present problem and convert credible sources into an immediate application path, instead of returning a generic self-help shelf or a popularity list.
## Do Not Use When
- The user asks OMH to learn from workflow outcomes, missed routes, or evaluation traces.
- The learning goal is already chosen and the user wants a multi-week syllabus, instructional sequence, or assessment plan; use `omh-curriculum-design`.
- The user supplied a paper, PDF, arXiv entry, or excerpt and wants it explained; use `omh-paper-learning`.
- The requested output is a typed source candidate inventory or acquisition status rather than a fitted learning brief; use `omh-source-finder`.View the complete source on GitHubomh-legal-compliance-review
When your agent uses it
[omh] Business contract, NDA, or policy with legal risk: surface contract and compliance risks, questions, and escalation points before a legal decision or action. Use when the user says: contract review, contract liability clause, regulatory analysis, compliance review, contract redline, redline the contract, negotiation preparation, negotiation strategy.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,536 tokensWhen the skill is activated
Reference documents
2,537 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,435 bytesSKILL.mdcore7,435 bytesreferences/negotiation-preparation.mddoc3,454 bytesreferences/procedure.mddoc8,258 bytes
Read SKILL.md
# Legal Compliance Review
This is an OMH `legal-compliance-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`legal-compliance-review` prepares scoped issues for human legal review without claiming counsel or filing authority.
## Do Not Use When
- The user needs a final jurisdiction-specific legal opinion, legal representation, or authoritative filing decision; prepare the issue and counsel brief instead.
- The review is about code, secrets, permissions, prompt injection, dependencies, or unsafe tool behavior; use `omh-security-safety-review`.
- The request is a plain-language rewrite without a legal-risk review objective; use `omh-content-operator`.
- The user asks to sign, accept, submit, file, publish, or change a policy or contract in an external system; use `omh-apps` only after explicit authority.View the complete source on GitHubomh-lifecycle-growth
When your agent uses it
[omh] Churn or weak activation among users: turn an observed onboarding, activation, retention, re-engagement, referral, or monetization problem into one consent-safe in-app journey or growth experiment plan with a bounded readout and an explicit decision. Use when the user says: lifecycle-growth, lifecycle growth, lifecycle marketing, lifecycle messaging, in-app journey, in-app message campaign, onboarding journey, onboarding nudge.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
2,195 tokensWhen the skill is activated
Reference documents
2,932 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,785 bytesreferences/procedure.mddoc13,741 bytes
Read SKILL.md
# Lifecycle Growth
This is an OMH `lifecycle-growth` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`lifecycle-growth` exists so audience eligibility, consent and frequency safety, sticky exposure, causal measurement, and the stop decision travel together in one plan instead of being assembled ad hoc from analysis, copy, scheduling, and connector work.
## Do Not Use When
- The user only wants a one-off message, email, banner, or push copy rewrite with no audience, experiment, or decision; use `omh-content-operator`.
- The user wants generic exploration or calculation over a supplied cohort, retention, conversion, or segment table with no journey or experiment to design; use `omh-data-analysis`.
- The user wants a recurring schedule, cron, or digest cadence for an already-decided operation rather than a lifecycle intervention.
- The user asks to send a message, change a feature flag, create a segment, or start an experiment in a provider now; use `omh-apps` with explicit authorization and observed results.View the complete source on GitHubomh-live-incident-response
When your agent uses it
[omh] Production is down or an incident is open: command an incident that is still open -- severity as declared live state, commander and roles, an append-only timeline, a recorded temporary mitigation, verified recovery, and the customer notice. Use when the user says: live-incident-response, live incident response, incident response, active incident, ongoing incident, open incident, incident open, incident commander.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
2,205 tokensWhen the skill is activated
Reference documents
1,329 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,552 bytesreferences/incident-command-method.mddoc6,192 bytes
Read SKILL.md
# Live Incident Response
This is an OMH `live-incident-response` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`live-incident-response` exists because an incident that is still open had no owner. `support-operations` sent an active incident to `reliability-review`, and `reliability-review` reviews incident notes after the fact, so the one skill that saw the request handed it to a postmortem while the outage was still running.
## Do Not Use When
- The incident is over and the request is the postmortem, the SLO or error-budget consequence, or remediation follow-up; use `omh-reliability-review`.
- The request is one customer's support case needing a reply, a severity opinion, and an escalation path, with no incident declared; use `omh-support-operations`.
- The request is a release being rolled out and watched -- deploy checklist, health signals, rollback criteria -- and nothing has been declared broken; use `omh-deploy-and-monitor`.
- The request is to send the page, publish the status-page update, or deliver the customer notice; use `omh-apps`, which records a send as observed only on a returned result.View the complete source on GitHubomh-live-info
When your agent uses it
[omh] Live rate, score, or local time a work task needs: policy overlay for live lookups - add provider, freshness, units, and source-quality gates after preferring native live-data tools for ordinary weather, finance, sports, maps, and time-zone requests. Use when the user says: live-info-operator, live info operator, live information, real time information, real-time information, weather today, current weather, weather forecast.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,451 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,821 bytesSKILL.mdcore6,821 bytesSKILL.mdcore6,821 bytesSKILL.mdcore6,821 bytesSKILL.mdcore6,821 bytes
Read SKILL.md
# Live Info Operator
This is an OMH `live-info-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`live-info-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-llm-app-dev
When your agent uses it
[omh] LLM-powered feature to build: LLM app development: prepare a build handoff for an LLM-powered feature with a pinned provider boundary, schema-first outputs, versioned prompt files, grounded retrieval, and an eval suite as a shipped deliverable. Use when the user says: llm-app-dev, llm app development, llm application development, build an llm app, build an llm feature, llm feature development, build a rag pipeline, rag pipeline.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
3,348 tokensWhen the skill is activated
Reference documents
9,993 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore15,864 bytesSKILL.mdcore15,864 bytesreferences/build-rails.mddoc11,778 bytesreferences/eval-harness.mddoc13,052 bytesreferences/public-board.mddoc7,899 bytesreferences/stateful-contracts.mddoc16,259 bytes
Read SKILL.md
# Llm App Dev
This is an OMH `llm-app-dev` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`llm-app-dev` exists because the failure modes of an LLM feature are not the failure modes of the code around it. A floating model alias, a prompt buried in a string literal, an output scraped out of prose with a regex, and a retrieval layer nobody measured all pass code review and all fail in production, and without a golden set nobody can tell whether the next prompt edit helped or hurt.
## Do Not Use When
- The subject is comparing executors or agent harnesses - Codex against Claude Code against Hermes coding - rather than evaluating the product's own model calls.
- An agent run is already stuck, looping, or drifting and needs diagnosis; use `omh-agent-debug`.
- The subject is the harness's own context window, prompt caching, or token budget rather than the application being built; use `omh-context-budget-review`.
- The request is a prompt-injection, secret-handling, or dependency risk gate on work that already exists; use `omh-security-safety-review`.View the complete source on GitHubomh-localization-review
When your agent uses it
[omh] Translated product or content release: make a product or content release locale-ready with terminology, cultural-fit, and quality-review guidance. Use when the user says: localization review, translation QA, locale glossary, 현지화 검토, 번역 QA, 용어집.
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,236 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,989 bytesSKILL.mdcore5,989 bytesSKILL.mdcore5,989 bytesSKILL.mdcore5,989 bytesSKILL.mdcore5,989 bytes
Read SKILL.md
# Localization Review
This is an OMH `localization-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`localization-review` makes terminology, context, cultural fit, and locale QA reviewable without treating a drafted translation as a published or visually validated release.
## Do Not Use When
- The request is a short sentence or word translation or rewrite with no product or locale QA context; answer directly or use `omh-content-operator`.
- The user needs fresh rendered UI evidence, clipping checks, or a visual PASS/REVISE/BLOCK verdict; use `omh-visual-qa`.
- The user asks to edit locale files, push a translation-management-system job, publish strings, or configure localization settings; use `omh-files` or `omh-apps` with explicit target and authority.
- The request asks for a regulatory or contractual conclusion about translated legal text; use `omh-legal-compliance-review`.View the complete source on GitHubomh-market-research
When your agent uses it
[omh] Market sizing or customer/competitive analysis: investigate a scoped market with TAM/SAM/SOM sensitivity, attributed customer evidence, and comparable competitor/pricing profiles before a decision brief. Use when the user says: market-research, market sizing, tam sam som, bottom up market sizing, market size sensitivity, customer evidence analysis, jtbd evidence matrix, competitor pricing profiles.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,618 tokensWhen the skill is activated
Reference documents
3,870 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesSKILL.mdcore8,255 bytesreferences/competitive-pricing.mddoc2,540 bytesreferences/customer-evidence.mddoc2,423 bytesreferences/findings-template.mddoc2,855 bytesreferences/market-sizing.mddoc3,345 bytesreferences/procedure.mddoc7,150 bytes
Read SKILL.md
# Market Research
This is an OMH `market-research` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`market-research` turns a broad market question into bounded sizing, customer evidence, and comparable competitive analysis that a decision owner can inspect without mistaking secondary research for validation.
## First Steps
- Confirm the decision, buyer/segment, geography, period, currency/base year, units/denominator, source cutoff, budget, and stop condition before retrieval. Mark missing inputs unknown; ask the one that changes the analysis first.
- Read `references/findings-template.md` to open the ledger, then load only the needed methods: `references/market-sizing.md`, `references/customer-evidence.md`, or `references/competitive-pricing.md`. Do not manufacture empty analysis lanes for an out-of-scope question.
## Do Not Use WhenView the complete source on GitHubomh-materials-package
When your agent uses it
[omh] PPT, PDF, Excel, or HWP output to produce: decks, PDFs, spreadsheets, documents, HWP, Markdown, and binary export handoffs. Use when the user says: materials-package, material package, materials package, document package, deck file, binary export, file export, render qa.
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
1,924 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytesSKILL.mdcore8,519 bytes
Read SKILL.md
# Materials Package
This is an OMH `materials-package` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`materials-package` exists so Hermes can handle document, deck, spreadsheet, PDF, Word, Keynote, HWP, and Markdown work as a first-class material-processing workflow without becoming a hidden file generator.
## Do Not Use When
- The user only needs a weekly/monthly report outline; use `omh-report-package`.
- The user asks for recurring meeting minutes or scrum history; use `omh-operating-rhythm`.
- The request is code documentation, README, or project wiki maintenance; use the docs/wiki workflow.
View the complete source on GitHubomh-media-input
When your agent uses it
[omh] Audio, video, or screenshot to process: user-sent media - audio, video, YouTube links, screenshots, receipts, OCR, meeting recordings, transcripts, timestamps, and clip summaries, gated for source, permission, and hallucination risk. Use when the user says: media-input-operator, media input operator, media input, audio transcription, audio transcript, transcribe audio, transcribe this audio, meeting recording.
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
1,898 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,926 bytesSKILL.mdcore8,926 bytesSKILL.mdcore8,926 bytesSKILL.mdcore8,926 bytesSKILL.mdcore8,926 bytes
Read SKILL.md
# Media Input Operator
This is an OMH `media-input-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`media-input-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-meeting-brief
When your agent uses it
[omh] Upcoming work meeting that lacks an agenda: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.
What it loads into context
Frontmatter
109 tokensAlways available to the agent
SKILL.md
1,186 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,794 bytesSKILL.mdcore5,794 bytes
Read SKILL.md
# Meeting Brief
This is an OMH `meeting-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`meeting-brief` exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.
## Do Not Use When
- The user needs observed meeting minutes, decisions, or action items but has not provided notes.
- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
View the complete source on GitHubomh-memory-new
When your agent uses it
[omh] Project fact to remember across future sessions: capture one bounded durable project or product memory candidate through explicit remember, refuse, or defer review; for a past decision use decision-recall. Use when the user says: memory-new, new memory, project memory, product memory, remember this project, remember this product, do not save, do not save this token.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
1,459 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,985 bytes
Read SKILL.md
# Memory New
This is an OMH `memory-new` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`memory-new` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-mobile-release
When your agent uses it
[omh] Releasing an iOS or Android app through the stores -- signing, the privacy manifest, a TestFlight or Play beta, a staged rollout, a hotfix: prepare each gate the store enforces, and plan the halt and the next build before the rollout starts, because a store release cannot be rolled back. Use when the user says: mobile-release, mobile release, mobile app release, ios release, android release, app store release, app store submission, submit to the app store.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
1,954 tokensWhen the skill is activated
Reference documents
637 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,916 bytesreferences/mobile-release-method.mddoc2,906 bytes
Read SKILL.md
# Mobile Release
This is an OMH `mobile-release` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`mobile-release` exists because store releases had no owner: `release-cut` decides a service release that can roll back, `deploy-and-monitor` watches a deploy, and `production-audit` audits readiness platform-neutrally, while signing, a privacy manifest, a TestFlight beta or a Play staged rollout had nothing that knew the store's gates.
## First Steps
- Ask which platforms, which version and build number, and how signing is held today.
- Ask what halts the rollout, before planning any rollout step.
## Do Not Use WhenView the complete source on GitHubomh-model-finetuning
When your agent uses it
[omh] Fine-tuning a model on your own data -- SFT, DPO, RLVR or a LoRA adapter: decide first whether prompting or retrieval already closes the gap, choose the method from the data you have, and promote a checkpoint only when it beats the untuned baseline on a held-out eval. Use when the user says: model-finetuning, model finetuning, model fine-tuning, fine-tune a model, fine-tune the model, fine tune a model, fine tune the model, fine-tune.
What it loads into context
Frontmatter
174 tokensAlways available to the agent
SKILL.md
1,981 tokensWhen the skill is activated
Reference documents
634 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,901 bytesSKILL.mdcore8,901 bytesreferences/finetuning-method.mddoc2,830 bytes
Read SKILL.md
# Model Finetuning
This is an OMH `model-finetuning` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`model-finetuning` exists because producing a model had no owner: `inference-serving` serves one that exists and `llm-app-dev` builds on top of one, while an SFT or DPO question had no baseline comparison and no way to answer that training is not needed.
## First Steps
- Ask what the untuned model and the best prompt score on the held-out examples before discussing any method.
- Ask what shape the data has -- demonstrations, preference pairs, or answers a program can check.
## Do Not Use WhenView the complete source on GitHubomh-molecular-docking
When your agent uses it
[omh] Prepared PDBQT inputs: run bounded standalone Vina docking with real poses, scores and replay provenance; never infer efficacy or safety. Use when the user says: molecular-docking, rigid-receptor docking, PDBQT docking, ligand docking poses, AutoDock Vina.
What it loads into context
Frontmatter
117 tokensAlways available to the agent
SKILL.md
1,445 tokensWhen the skill is activated
Reference documents
4,704 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/scripts/dock.py
Files
SKILL.mdcore7,043 bytesSKILL.mdcore7,043 bytesSKILL.mdcore7,043 bytesreferences/execution-and-qa.mddoc5,357 bytesreferences/full-contract.mddoc2,848 bytesreferences/procedure.mddoc4,037 bytestoolkit/NOTICE.mddoc1,647 bytestoolkit/README.mddoc7,069 bytestoolkit/examples/settings.jsonasset581 bytestoolkit/scripts/dock.pyruns17,670 bytestoolkit/upstream-manifest.jsonasset6,050 bytes
Read SKILL.md
# Molecular Docking
This is an OMH `molecular-docking` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Input validation and tutorial numbers are not measured docking. Require a real engine search and digest-bound poses, finite energies and replay settings.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md`. Use the explicitly invoked standalone Vina Python helper, not an invented ToolUniverse tool or hidden core execution service.
- Recover prepared file paths, source/license and preparation receipts, angstrom binding box, seed, CPU, new output directory and host deadline. Never guess a site, silently prepare a molecule or install dependencies on skill load.
- Use `--validate-only` for dependency-free prerequisites, or explicitly invoke actual docking in an approved environment with a host-enforced timeout and stdout/stderr capture. Missing dependencies must refuse, not produce guessed findings.
View the complete source on GitHubomh-native-debugging
When your agent uses it
[omh] Native program crashes or corrupts memory: prepare hypothesis-driven debugging of native binaries and instruct the executor to drive a DAP debugger instead of printf. Use when the user says: native-debugging, native debugging, native binary, segfault, segmentation fault, core dump, stack corruption, memory corruption.
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
2,036 tokensWhen the skill is activated
Reference documents
1,308 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,285 bytesSKILL.mdcore9,285 bytesSKILL.mdcore9,285 bytesreferences/native-debug-loop.mddoc5,941 bytes
Read SKILL.md
# Native Debugging
This is an OMH `native-debugging` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`native-debugging` closes OMH's zero-coverage low-level domain by preparing a hypothesis-driven, DAP-first debugging plan for native binaries, while OMH itself continues to execute nothing.
## Do Not Use When
- The failure is a build or CI failure rather than a runtime fault in a binary; use `omh-build-failure-triage`.
- The subject is an agent or workflow misbehaving rather than a native binary; use `omh-agent-debug`.
- The wrong result, flaky test, or lost update is in application code such as a Python or TypeScript service and needs its root cause reproduced; use `omh-app-debugging`.
- The change is Rust source work whose risk is `unsafe` or UB discipline; use `omh-rust`.View the complete source on GitHubomh-operating-rhythm
When your agent uses it
[omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,387 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,665 bytesSKILL.mdcore6,665 bytesSKILL.mdcore6,665 bytesSKILL.mdcore6,665 bytesSKILL.mdcore6,665 bytesSKILL.mdcore6,665 bytes
Read SKILL.md
# Operating Rhythm
This is an OMH `operating-rhythm` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`operating-rhythm` exists so recurring operating work has durable minutes, decisions, and follow-up history without pretending a meeting outcome was observed.
## Do Not Use When
- The user only needs a one-off meeting agenda before the meeting; use `omh-meeting-brief`.
- The request is a weekly status/risk summary rather than cadence history; use `omh-ops-review`.
- The user asks for report packaging, PPT outline, or reliability evidence review.
View the complete source on GitHubomh-ops-observability-card
When your agent uses it
[omh] Tracking cost, tokens, latency, or service health: prepare an operations command-board for wrapper-safe token, cost, latency, run history, queue, failure-mode, external metric-provider, and service-quality evidence boundaries. Use when the user says: ops-observability-card, observability card, operations command board, ops command board, service quality board, service quality, external metric provider, metric provider.
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
1,727 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,281 bytes
Read SKILL.md
# Ops Observability Card
This is an OMH `ops-observability-card` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ops-observability-card` exists so service, loop, and automation operations get one board where each cost, latency, token, failure-mode, and metric-provider figure is marked observed or prepared, instead of an improvised dashboard.
## Do Not Use When
- The user asks what their own Hermes conversation has used or cost; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user wants one run's timing and context-budget report; use `omh-run-efficiency`.
- The user asks OMH to sign in to a metric provider, billing console, or dashboard and pull live figures; the card reads only supplied payloads and Hermes' own records.
View the complete source on GitHubomh-ops-review
When your agent uses it
[omh] Recurring operating status and blockers: status, risks, blockers, priorities, and follow-ups. Use when the user says: ops-review, ops review, weekly ops review, status review, operating review, release risks, risks and blockers, priorities.
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,195 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,635 bytes
Read SKILL.md
# Ops Review
This is an OMH `ops-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ops-review` exists to keep `operations` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The review is over sales stages, forecast categories, deal aging, or seller forecast rather than generic operating status; use `omh-sales-pipeline-review`.
- The primary output is durable cadence history, minutes, a decision log, or action history; use `omh-operating-rhythm`.
## ExamplesView the complete source on GitHubomh-paper-learning
When your agent uses it
[omh] Paper or paper PDF to understand: explain a supplied paper or paper/PDF at a selected level while preserving full section coverage and source evidence boundaries. Use when the user says: paper-learning, paper learning, paper-explainer, paper explainer, paper explanation, explain this paper, explain this arxiv paper, paper walkthrough.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,930 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,094 bytesSKILL.mdcore9,094 bytesSKILL.mdcore9,094 bytesSKILL.mdcore9,094 bytesSKILL.mdcore9,094 bytesSKILL.mdcore9,094 bytes
Read SKILL.md
# Paper Learning
This is an OMH `paper-learning` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`paper-learning` exists so Hermes can act like a strong human tutor for papers: choose the right explanation level, walk through the full paper section by section, and keep PDF extraction and validation evidence honest.
## Do Not Use When
- The request asks to export, convert, render, or package a file; use `omh-materials-package`.
- The request asks for daily/weekly paper monitoring, digest, source inbox, or Scout/Analyst/Briefer operations.
- The request asks to find current papers or sources when no supplied paper exists; use `ulw-research`.
- The request asks for a visual/image card; use `omh-image-cards`.View the complete source on GitHubomh-people-ops
When your agent uses it
[omh] Company hiring or HR process to structure: turn hiring and people context into a fair, structured recruiting or people-operations brief. Use when the user says: recruiting plan, hiring scorecard, interview scorecard, candidate debrief, 채용 계획, 면접 평가표, 후보자 비교.
What it loads into context
Frontmatter
121 tokensAlways available to the agent
SKILL.md
1,237 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,010 bytes
Read SKILL.md
# People Ops
This is an OMH `people-ops` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`people-ops` keeps recruiting and people-process guidance fair, structured, and evidence bounded before any human decision or external HR action.
## Do Not Use When
- The request asks for a jurisdiction-specific employment-law conclusion, policy compliance ruling, or contract interpretation; use `omh-legal-compliance-review`.
- The user only needs a one-off job-ad, rejection, or interview-email rewrite; use `omh-content-operator`.
- The user asks to create ATS records, send invitations, book interviews, change employment status, or modify HRIS settings; use `omh-apps` with explicit authorization and observed results.
- The prompt asks the workflow to make an unsupported candidate decision from protected characteristics or missing interview evidence; retain the process and evidence gap instead.View the complete source on GitHubomh-physical-device-readiness
When your agent uses it
[omh] Agent control of a robot, 3D printer, or IoT relay: gate robots, 3D printers, IoT relays, sensors, and lab hardware before trials; use external-connector-readiness for provider or connector adoption and toolbelt-readiness for missing control tools. Use when the user says: physical-device-readiness, physical device readiness, device safety readiness, physical device safety, hardware safety gate, 3d printer readiness, 3D printer safety, snapmaker printer safety.
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
1,943 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,194 bytes
Read SKILL.md
# Physical Device Readiness
This is an OMH `physical-device-readiness` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`physical-device-readiness` exists because a robot, heater, or relay acts on the physical world, where a wrong command can hurt someone or damage property: it fixes the safety envelope, sensor and camera gates, dry runs, operator approval, and emergency stop before any trial, and turns the commands the agent must never run into a proposed deny list the user applies.
## Do Not Use When
- The device is reached through a provider or connector the user has not adopted yet; use `omh-external-connector-readiness`.
- The tool that would control the device is missing; use `omh-toolbelt-readiness`.
- The user asks to run the command, move the hardware, or start the print now; use `omh-terminal` or `omh-apps`, which need observed operator approval before any execution claim.
View the complete source on GitHubomh-plan
When your agent uses it
[omh] Software feature or bugfix not yet planned: structured planning before execution. Use when the user says: plan, implementation plan, make a plan, write a plan, write the plan, task breakdown, safe feature, safely add a feature.
What it loads into context
Frontmatter
105 tokensAlways available to the agent
SKILL.md
2,737 tokensWhen the skill is activated
Reference documents
758 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,809 bytesreferences/project-constitution.mddoc3,427 bytes
Read SKILL.md
# Plan
This is an OMH `plan` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`plan` exists so a feature or a fix gets its goals, non-goals, risks, acceptance criteria, and verification shape written down and accepted by the user before any code moves, with every step small enough to check and no implementation hidden inside the plan text.
## 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.
## ExamplesView the complete source on GitHubomh-product-brief
When your agent uses it
[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.
What it loads into context
Frontmatter
124 tokensAlways available to the agent
SKILL.md
1,399 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,617 bytes
Read SKILL.md
# Product Brief
This is an OMH `product-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`product-brief` turns product evidence into a reviewable PRD and prioritization frame before delivery planning without treating a draft as an accepted roadmap commitment.
## Do Not Use When
- The input is unprocessed feedback, bug reports, or feature asks that first need clustering and evidence boundaries; use `omh-feedback-triage`.
- The product evidence is unvalidated, synthetic, or a founder belief and the problem gate has not returned validated; use `omh-product-discovery-validation` before a PRD.
- The input is a growth hypothesis that still needs an experiment and readout before it becomes a product requirement; use `omh-lifecycle-growth`.
- The user needs a company or product strategy decision across high-level options rather than a requirements or roadmap artifact; use `omh-decide`.View the complete source on GitHubomh-product-discovery-validation
When your agent uses it
[omh] Unvalidated early product idea: test whether a customer problem, segment, and business hypothesis deserve product investment, ending in kill, pivot, persevere, or inconclusive before any PRD. Use when the user says: product-discovery-validation, product discovery validation, product discovery, customer discovery, customer discovery plan, zero to one validation, validate the problem before building, problem solution interview.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
1,912 tokensWhen the skill is activated
Reference documents
2,650 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,327 bytesreferences/procedure.mddoc12,148 bytes
Read SKILL.md
# Product Discovery Validation
This is an OMH `product-discovery-validation` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`product-discovery-validation` gives an early idea a bounded, evidence-typed path to a kill, pivot, persevere, or inconclusive decision so `product-brief` consumes validated inputs instead of judging raw discovery itself.
## Do Not Use When
- The user needs market, competitor, pricing, or customer research on named sources without a discovery decision to make; use `omh-research-brief`.
- The user is clarifying their own request, requirements, or preferences rather than testing a customer problem with external people; use `ulw-interview`.
- The user needs a company or product strategy decision across existing options with evidence already in hand; use `omh-decide`.
- The problem, segment, and evidence are already validated and accepted and the user wants a PRD or prioritization; use `omh-product-brief`.View the complete source on GitHubomh-production-audit
When your agent uses it
[omh] Imminent production launch or release: evaluate release, deploy, security, observability, rollback, docs, and support readiness without claiming production access. Use when the user says: production-audit, production audit, production readiness, prod audit, prod readiness, ready for production, ready to ship, ship readiness.
What it loads into context
Frontmatter
126 tokensAlways available to the agent
SKILL.md
1,411 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,723 bytesSKILL.mdcore6,723 bytes
Read SKILL.md
# Production Audit
This is an OMH `production-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`production-audit` gives OMH a preflight release surface so operators can see production risks before launch while OMH stays out of deploy and infrastructure execution.
## Do Not Use When
- The user wants to implement a feature or fix; prepare a coding handoff first.
- The user wants incident/SLO analysis after production behavior; use `omh-reliability-review`.
- The user wants a narrow code diff review; use `omh-code-review`.
View the complete source on GitHubomh-provider-profile-posture
When your agent uses it
[omh] Provider credentials without exposure: prepare provider-profile metadata without reading secrets or calling providers. Use when the user says: provider-profile-posture, provider profile posture, provider profile readiness, secret presence confirmation, connector profile posture, 공급자 프로필 상태, 시크릿 존재 확인, 커넥터 준비 상태.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,218 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,101 bytes
Read SKILL.md
# Provider Profile Posture
This is an OMH `provider-profile-posture` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`provider-profile-posture` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-refactor-plan
When your agent uses it
[omh] Decided cross-module refactor to phase: refactor planning - turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.
What it loads into context
Frontmatter
153 tokensAlways available to the agent
SKILL.md
1,953 tokensWhen the skill is activated
Reference documents
2,608 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,170 bytesreferences/dependency-upgrade.mddoc5,274 bytesreferences/interface-shaping.mddoc3,095 bytesreferences/refactor-phases.mddoc3,415 bytes
Read SKILL.md
# Refactor Plan
This is an OMH `refactor-plan` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`refactor-plan` exists because boundary-changing refactors bounced between goal planning and behavior-preserving cleanup with neither owning the execution shape: the phase order, the per-phase rollback, and the files table that make a large refactor reviewable and abortable.
## Do Not Use When
- The refactor's direction is still contested or the goal itself needs consensus planning; use `ulw-plan`.
- The work is deletion-first cleanup with no boundary changes; use `omh-ai-slop-cleaner`.
- The plan is done and the claim is that work is complete; use `omh-verification-gate` for the evidence close.
- The version bump carries a security advisory, a CVE, or a leaked secret; use `omh-security-event-response`, which owns containment and closure.View the complete source on GitHubomh-relational-db
When your agent uses it
[omh] Database work on a relational store -- a slow query, an index to size, a migration on a big table, a lock taken during deploy, N+1 queries: plan it with the checks that prove it safe, and never call a migration ready without its lock behaviour and rollback. Use when the user says: relational-db, relational database, online migration, migration for a large table, lock-safe ddl, alter table, took a lock, table lock.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
2,035 tokensWhen the skill is activated
Reference documents
2,259 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,005 bytesSKILL.mdcore9,005 bytesreferences/engine-lock-tables.mddoc9,415 bytes
Read SKILL.md
# Relational Db
This is an OMH `relational-db` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`relational-db` exists because the database work itself had no owner: `backend` owns `schema_migration_plan/v1` for a service change, and an index question, a lock taken during deploy, or an N+1 finding was answered by a data, deploy, or interview lane with no lock model at all.
## First Steps
- Ask for the engine, the version, and the table sizes before proposing any statement.
- For a migration, give every step its lock behaviour and its rollback before calling the plan ready.
## Do Not Use WhenView the complete source on GitHubomh-release-cut
When your agent uses it
[omh] Shipping a versioned release -- tag it, stage it behind a canary, or roll back the last deploy: decide what goes in, the version, the rollout stages, and a rollback with its trigger and exact command before it is needed. Use when the user says: release-cut, release cut, cut a release, cut the release, cut a new release, tag a release, tag the release, release candidate.
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
1,877 tokensWhen the skill is activated
Reference documents
724 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,583 bytesreferences/release-and-rollback-method.mddoc3,137 bytes
Read SKILL.md
# Release Cut
This is an OMH `release-cut` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`release-cut` exists because nothing owned deciding a release: `deploy-and-monitor` watches a rollout that is already happening, and a cut, a canary, or a rollback decision reached an image card or a watch lane with no rollback trigger at all.
## First Steps
- State what goes in, what is held back, and the version before proposing the cut.
- Name the rollback trigger and its exact command before the first stage ships.
## Do Not Use WhenView the complete source on GitHubomh-reliability-review
When your agent uses it
[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,368 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,539 bytesSKILL.mdcore6,539 bytesSKILL.mdcore6,539 bytesSKILL.mdcore6,539 bytes
Read SKILL.md
# Reliability Review
This is an OMH `reliability-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`reliability-review` exists to make SRE-style review strict: service reliability claims must point to metrics or references, and remediation remains separate from the review narrative.
## Do Not Use When
- The user only needs a generic status report or leadership deck.
- No service, incident, SLO, metric, or reliability source boundary is available.
- The request is implementation of remediation rather than review of reliability evidence.
- The incident is still open and the user needs severity declared, a commander assigned, a running timeline, and recovery verified; use `omh-live-incident-response` and review it once it is closed.View the complete source on GitHubomh-report-package
When your agent uses it
[omh] Periodic report for executives: weekly/monthly reports, executive briefs, PPT-ready outlines, and upload packages. Use when the user says: report-package, report package, weekly report, monthly report, executive report, exec brief, leadership deck, status package.
What it loads into context
Frontmatter
111 tokensAlways available to the agent
SKILL.md
1,504 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,134 bytesSKILL.mdcore7,134 bytes
Read SKILL.md
# Report Package
This is an OMH `report-package` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`report-package` exists to make reporting a first-class operations surface: Hermes can produce clean report and slide outlines while keeping approvals, delivery, and binary deck export as separate evidence.
## Do Not Use When
- The user needs SLO, incident, or error-budget review; use `omh-reliability-review`.
- The user asks for a live `.pptx` deck file rather than a PPT-ready outline.
- The request is meeting minutes, scrum history, or action-item tracking.
View the complete source on GitHubomh-repro-audit
When your agent uses it
[omh] Evaluation logs versus reported paper conditions: audit supplied HellaSwag results with exact scores and review-gated evidence; never run a model. Use when the user says: repro-audit, hellaswag log, hellaswag results, hellaswag score.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
1,459 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytesSKILL.mdcore7,176 bytes
Read SKILL.md
# Repro Audit
This is an OMH `repro-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
A displayed score is not evidence that evaluation conditions match. This workflow compares retained source claims without executing an evaluator or inventing missing conditions.
## First Steps
- Ask which metric the person means if acc versus acc_norm is not explicit; never substitute one for the other.
- Use only supplied local files. If no evaluation record is available, ask for one; do not run or fetch a model.
- For agent infrastructure, call `omh paper import-harness --results FILE --metric acc_norm --out NEW_CASE` for native Harness JSON; `--metric acc` is a separate profile.
- When authoring a normalized case instead, call `omh paper audit-init --out NEW_CASE [--metric acc_norm]`; omitted metric preserves the acc default. All conditions start unknown.View the complete source on GitHubomh-research-brief
When your agent uses it
[omh] Business question on market, competitors, pricing: business research brief - turns a market, competitor, pricing, or customer question into a structured evidence-vs-inference brief; for raw link gathering use ulw-research. Use when the user says: research-brief, business-research, business research, research brief, decision brief, pricing decision brief, decision-ready brief, source-backed business research.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,971 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytesSKILL.mdcore9,532 bytes
Read SKILL.md
# Research Brief
This is an OMH `research-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`research-brief` exists to keep `research` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The user needs to decide whether a customer problem deserves product investment with evidence typing and customer re-entry; use `omh-product-discovery-validation`.
- The request is only fresh links, citations, or current facts without a business question or decision audience; use `ulw-research`.
- Sources have not yet been selected and the user wants source types, candidates, or acquisition state; use `omh-source-finder`.
View the complete source on GitHubomh-rules-distill
When your agent uses it
[omh] Turn repeated lessons into written rules: extract repeated principles from skills, prompts, traces, reviews, and failures into reviewed rule candidates without auto-mutating guidance. Use when the user says: rules-distill, rules distill, distill rules, rule distillation, principle distill, skill principles, extract agent rules, turn traces into rules.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
1,885 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,871 bytesSKILL.mdcore8,871 bytesSKILL.mdcore8,871 bytesSKILL.mdcore8,871 bytesSKILL.mdcore8,871 bytes
Read SKILL.md
# Rules Distill
This is an OMH `rules-distill` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`rules-distill` gives OMH a disciplined way to learn from large skill ecosystems like ECC without wholesale copying: extract principles, review them, then patch OMH only through explicit verified work.
## Do Not Use When
- The user wants a single workflow route regression.
- The user wants durable factual project memory; use `omh-wiki` or memory curation.
- The user already approved a concrete code/doc change; use the implementation workflow.
- The ask is writing or keeping current the file an agent reads at startup -- AGENTS.md, CLAUDE.md, a Cursor rule; use `omh-agent-instructions`, which updates only its marked region.View the complete source on GitHubomh-run-efficiency
When your agent uses it
[omh] Run efficiency and context usage report: report supplied local run efficiency while provider data stays unobserved. Use when the user says: run-efficiency, run efficiency report, local run efficiency, context utilization, tool duration report, 실행 효율 리포트, 컨텍스트 사용량, 도구 지연 시간.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,402 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,643 bytes
Read SKILL.md
# Run Efficiency
This is an OMH `run-efficiency` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`run-efficiency` exists so a question about how a run spent its time, tools, and context gets the supplied timings and context budget, plus what Hermes itself recorded for a named session's tokens and cost, instead of figures a model guesses.
## Do Not Use When
- The user asks only what this Hermes conversation has used or cost so far; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user wants service latency, uptime, error rates, or supplied metric-provider figures; use `omh-ops-observability-card`.
- The user wants a provider invoice or quota truth; no OMH report observes either, so name the provider's own console as the source.
View the complete source on GitHubomh-running-work-board
When your agent uses it
[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time. Use when the user says: running-work-board, running work board, which units are running, what models are running, 지금 뭐 돌고 있어, 뭐가 돌고 있어, 어떤 모델로 돌고 있어, 실행 중인 작업 보여줘.
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
1,360 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,322 bytes
Read SKILL.md
# Running Work Board
This is an OMH `running-work-board` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`running-work-board` exists because multi-session coding work was invisible: the runtime was tracked but the model was dropped, token counts had no write site at all, and a blocking dispatch could not report that it was still running. The board answers which model on which runtime, or says unknown.
## Do Not Use When
- The user wants to start, plan, or dispatch coding work rather than observe it.
- The user wants review, CI, or merge evidence, which a status board never provides.
- The user is asking about their own application's runtime status rather than OMH coding units.
View the complete source on GitHubomh-rust
When your agent uses it
[omh] Rust ownership, lifetime, or unsafe trouble: prepare Rust changes with ownership, error, and API discipline, and escalate any unsafe, FFI, or lock-free change to the UB checklist. Use when the user says: rust, rust code, rust skill, rustlang, borrow checker, lifetime error, ownership error, trait bound.
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
2,115 tokensWhen the skill is activated
Reference documents
3,622 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,283 bytesreferences/rust-discipline.mddoc10,231 bytesreferences/ub-escalation.mddoc5,364 bytes
Read SKILL.md
# Rust
This is an OMH `rust` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`rust` closes OMH's zero-coverage Rust domain and makes the escalation from ordinary Rust work to undefined-behavior discipline a deterministic routing rule rather than something a model is trusted to notice.
## Do Not Use When
- The request is a server, API, or schema design that happens to mention a Rust stack; use `omh-backend` for the contract and name Rust as the stack.
- The request is debugging a stripped or source-less native binary; use `omh-native-debugging`.
- The request is a general code review of finished Rust; use `omh-code-review`.
- The request is a Rust vocabulary or concept question with no change to prepare; answer it directly.View the complete source on GitHubomh-sales-development
When your agent uses it
[omh] Prospect or account worth pursuing: turn an account or market opportunity into a focused discovery, qualification, and next-step brief. Use when the user says: sales discovery, account plan, outbound messaging, 영업 발굴, 고객사 계획, 아웃바운드 메시지.
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,292 tokensWhen the skill is activated
Reference documents
1,501 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,292 bytesSKILL.mdcore6,292 bytesreferences/procedure.mddoc6,966 bytes
Read SKILL.md
# Sales Development
This is an OMH `sales-development` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`sales-development` prepares evidence-bounded discovery and qualification guidance without claiming sales execution.
## Do Not Use When
- The user needs a company-level positioning, market-entry, or strategic-options decision rather than account-level discovery; use `omh-decide`.
- The user supplies a CRM export or pipeline snapshot and needs portfolio health, aging, slipped deals, forecast calibration, or renewal-risk review; use `omh-sales-pipeline-review`.
- The user only wants a polished social post, newsletter, or one-off outbound-copy rewrite; use `omh-content-operator`.
- The user asks to send outreach, update Salesforce or HubSpot, create an opportunity, or book a meeting; use `omh-apps` with explicit recipient, object, and authority.View the complete source on GitHubomh-sales-pipeline-review
When your agent uses it
[omh] CRM pipeline or sales forecast to review: turn a supplied CRM export or pipeline snapshot into an evidence-bound pipeline health, forecast, and follow-up review. Aliases: pipeline-review, forecast-review, deal-review. Use when the user says: sales-pipeline-review, sales pipeline review, pipeline review, pipeline health, pipeline coverage, deal review, deal health, sales forecast review.
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
1,876 tokensWhen the skill is activated
Reference documents
2,129 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,106 bytesSKILL.mdcore9,106 bytesSKILL.mdcore9,106 bytesSKILL.mdcore9,106 bytesreferences/procedure.mddoc9,910 bytes
Read SKILL.md
# Sales Pipeline Review
This is an OMH `sales-pipeline-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`sales-pipeline-review` prepares evidence-bounded portfolio pipeline, forecast, and follow-up reviews from supplied CRM snapshots without replacing a CRM, mutating records, or claiming revenue.
## Do Not Use When
- The request is single-account discovery, qualification, buyer hypotheses, outreach drafting, or one opportunity's next step; use `omh-sales-development`.
- The user wants a weekly status, release-risk, or operating review with no sales stages, forecast categories, or deal records; use `omh-ops-review`.
- The user needs authoritative revenue, bookings, budget-variance, or close reporting rather than a pipeline scenario; use `omh-finance-analysis`.
- The user wants generic exploration or calculation on a supplied table with no stage, forecast, or deal-health semantics; use `omh-data-analysis`.View the complete source on GitHubomh-security-event-response
When your agent uses it
[omh] Security event on the code already shipped -- a CVE in a dependency, a secret committed to the repo, a license question, an advisory: triage reachability and severity, contain in order, and never close a leaked secret before its rotation is observed. Use when the user says: security-event-response, security event response, cve, triage this cve, cve in our dependency, cve in a dependency, security advisory, dependabot alert.
What it loads into context
Frontmatter
157 tokensAlways available to the agent
SKILL.md
1,988 tokensWhen the skill is activated
Reference documents
889 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,321 bytesreferences/event-containment-order.mddoc4,001 bytes
Read SKILL.md
# Security Event Response
This is an OMH `security-event-response` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`security-event-response` exists because an event had no owner: `security-safety-review` and `application-threat-model` review a design before it ships, and a CVE, a committed secret, or a license question was answered by onboarding, review, or an achievements lane with no containment order at all.
## First Steps
- Classify the event and state its exposure window before proposing any step.
- For a leaked secret, order the rotation and its observed rejection before any history rewrite.
## Do Not Use WhenView the complete source on GitHubomh-security-safety-review
When your agent uses it
[omh] Agent or automation safety risks: review prompt, tool, secret, dependency, destructive-action, and explicit local plugin risks before agent or code execution. Use when the user says: security-safety-review, security safety review, ai coding safety, agent safety review, prompt injection review, tool permission review, secret exposure review, destructive action review.
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
2,194 tokensWhen the skill is activated
Reference documents
959 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,456 bytesSKILL.mdcore10,456 bytesSKILL.mdcore10,456 bytesSKILL.mdcore10,456 bytesSKILL.mdcore10,456 bytesreferences/credential-rotation.mddoc4,478 bytes
Read SKILL.md
# Security Safety Review
This is an OMH `security-safety-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`security-safety-review` adapts ECC's AgentShield and safety-review posture into OMH as a review-first gate for agentic coding and operator workflows without adding hidden scanners or external dependencies.
## Do Not Use When
- The user asks for production readiness across release, rollback, and observability; use `omh-production-audit`.
- The user asks for merge verification commands; use `omh-verification-gate`.
- The user asks for a normal code review focused on bugs; use `omh-code-review`.
- The subject is an application or service rather than the agent's own runtime -- its assets, trust boundaries, attack scenarios, and the controls that defend them; use `omh-application-threat-model`.View the complete source on GitHubomh-show-reel
When your agent uses it
[omh] Video to make from an idea or a product: an explainer, motion graphics, kinetic type, a logo intro, a 3D scene, a data-viz animation, a music visual, a short or a source-grounded product film, authored and rendered to a measured MP4 with locale/export QA and source delivery. Use when the user says: show-reel, show reel, showreel, product showcase video, animated product film, motion showcase, animated portfolio, launch film.
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
2,538 tokensWhen the skill is activated
Reference documents
74,100 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/assets/engine/engine.jstoolkit/assets/engine/fx.jstoolkit/assets/engine/scenes.jstoolkit/scripts/codex_ref_image.shtoolkit/scripts/contact_sheet.pytoolkit/scripts/eleven.pytoolkit/scripts/finish.pytoolkit/scripts/font-coverage.mjstoolkit/scripts/mix.pytoolkit/scripts/motion_check.pytoolkit/scripts/music_tools.pytoolkit/scripts/narrate.pytoolkit/scripts/new_project.pytoolkit/scripts/preflight.pytoolkit/scripts/prep_images.pytoolkit/scripts/qa_check.pytoolkit/scripts/render.mjstoolkit/scripts/synth_music.pytoolkit/scripts/timeline.py
Files
SKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesSKILL.mdcore12,088 bytesreferences/art-direction.mddoc7,072 bytesreferences/assets-and-rights.mddoc1,951 bytesreferences/audio-production.mddoc4,148 bytesreferences/brief-and-locales.mddoc4,777 bytesreferences/craft-audio.mddoc19,081 bytesreferences/craft-brief.mddoc11,954 bytesreferences/craft-design.mddoc16,126 bytesreferences/craft-engine.mddoc26,944 bytesreferences/craft-images.mddoc8,927 bytesreferences/craft-qa.mddoc13,246 bytesreferences/craft-story.mddoc20,827 bytesreferences/craft-techniques-2.mddoc15,525 bytesreferences/craft-techniques.mddoc23,127 bytesreferences/craft-workflow.mddoc31,631 bytesreferences/game-capture.mddoc1,882 bytesreferences/genres.mddoc4,860 bytesreferences/kinetic-type.mddoc6,861 bytesreferences/launch-film.mddoc5,548 bytesreferences/motion-techniques.mddoc2,797 bytesreferences/procedure.mddoc17,387 bytesreferences/render-qa-delivery.mddoc8,525 bytesreferences/renderer-adapter.mddoc9,675 bytesreferences/source-package.mddoc1,469 bytesreferences/storyboard-and-evidence.mddoc5,451 bytestoolkit/LICENSE.upstreamasset1,081 bytestoolkit/README.mddoc18,809 bytestoolkit/assets/engine/engine.jsruns22,130 bytestoolkit/assets/engine/fx.jsruns21,400 bytestoolkit/assets/engine/index.htmlasset3,042 bytestoolkit/assets/engine/scenes.jsruns12,968 bytestoolkit/assets/sfx_presets.jsonasset3,425 bytestoolkit/examples/README.mddoc744 bytestoolkit/examples/music-spec.jsonasset372 bytestoolkit/examples/timing.jsonasset146 bytestoolkit/scripts/codex_ref_image.shruns2,625 bytestoolkit/scripts/contact_sheet.pyruns8,901 bytestoolkit/scripts/eleven.pyruns19,967 bytestoolkit/scripts/finish.pyruns8,152 bytestoolkit/scripts/font-coverage.mjsruns2,862 bytestoolkit/scripts/mix.pyruns9,761 bytestoolkit/scripts/motion_check.pyruns11,588 bytestoolkit/scripts/music_tools.pyruns30,110 bytestoolkit/scripts/narrate.pyruns12,785 bytestoolkit/scripts/new_project.pyruns10,728 bytestoolkit/scripts/preflight.pyruns5,777 bytestoolkit/scripts/prep_images.pyruns5,902 bytestoolkit/scripts/qa_check.pyruns7,307 bytestoolkit/scripts/render.mjsruns22,638 bytestoolkit/scripts/synth_music.pyruns6,597 bytestoolkit/scripts/timeline.pyruns16,476 bytestoolkit/scripts/tools/cutout.swiftasset1,801 bytestoolkit/upstream-manifest.jsonasset20,711 bytes
Read SKILL.md
# Show Reel
This is an OMH `show-reel` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`show-reel` owns the motion-production method for every authored video, from a 20-second idea explainer to a product film, so factual claims, visual decisions, locale timing, revision budget, measured exports, and delivery receipts cannot drift apart. It does not render inside OMH core.
## First Steps
- Pick the lane first. A video from an idea with no product claim, real UI or brand asset on screen takes the idea lane in `## Idea Videos` below; a product, launch, brand or work film, or any product fact on screen, takes the full method.
- Read `references/brief-and-locales.md` and `references/storyboard-and-evidence.md` before proposing visuals. Recover objective, audience, channel, duration, aspect ratio, fps, size cap, source/brand permissions, and tool availability from supplied context; honor explicit format and duration, ask only for irretrievable hard facts, and label reversible creative assumptions. A shot of a UI that exists is drawn from that product's own renderer output, never a look-alike, and every product fact on screen is copied from its canonical source and cited.
- Resolve content language from current explicit user/audience/channel instructions, then applicable stable preferences, then user language. Keep reply_language under host persona and separate content_locale, onscreen_text, subtitle_text, pronunciation_text, voice_policy, font_policy, and direction_policy; never replace literal IDs, commands, URLs, or trademarks.
- For a product, brand or work film, compare at least 3 genuinely distinct concept candidates before selection; record the rubric, winner, rejected alternatives, and per-segment art direction. Read `references/craft-workflow.md` (the full upstream production method), `toolkit/README.md` under the loaded skill directory with a file reader, then `references/renderer-adapter.md` before choosing tools; a missing renderer means HOLD on a requested video, not a completed delivery.View the complete source on GitHubomh-skill-health
When your agent uses it
[omh] OMH skill portfolio health overview: prepare a metadata-only OMH skill portfolio dashboard with stale surfaces, observed failure signals, pending amendments, and top actions. Use when the user says: skill-health, skill health, skill portfolio health, skill dashboard, skill health dashboard, skill failure pattern dashboard, skill failure patterns, pending skill amendments.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,631 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,689 bytesSKILL.mdcore7,689 bytes
Read SKILL.md
# Skill Health
This is an OMH `skill-health` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`skill-health` exists because a skill portfolio drifts in ways no single run shows -- a managed skill changed in place, an authoring finding nobody fixed, an update waiting on its hub -- and use counts measure none of that: it gathers the observed signals into one card with an owner lane and a safe next action for each, and changes nothing itself.
## Do Not Use When
- OMH setup, install, or a skill that does not load.
- One run that missed a route or went wrong.
- Finding a new skill to adopt; use `omh-skill-scout`.
View the complete source on GitHubomh-skill-scout
When your agent uses it
[omh] Existing skills to reuse before authoring: prepare a metadata-only search-before-creation report for local, marketplace, GitHub, and web skill candidates with risk review and adoption options. Use when the user says: skill-scout, skill scout, skill candidate, skill candidate search, skill discovery, find a skill, find skills, top skills.
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
1,676 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,700 bytesSKILL.mdcore7,700 bytesSKILL.mdcore7,700 bytesSKILL.mdcore7,700 bytes
Read SKILL.md
# Skill Scout
This is an OMH `skill-scout` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`skill-scout` exists because writing a skill that already exists, or adopting a public one on its popularity, both cost more than a search: it compares installed, bundled, and public candidates first, keeps each source's trust level and any scan verdict beside it, and recommends using, extending, or creating one without installing, copying, or trusting anything.
## Do Not Use When
- Repairing an OMH install or a skill that does not load.
- A health overview of the skills already installed; use `omh-skill-health`.
- Writing or changing a skill once the scout decision is made.
View the complete source on GitHubomh-source-finder
When your agent uses it
[omh] Gathering candidate papers, datasets, or repos: source candidate inventory - prepare typed source candidates and acquisition status before downstream work; use ulw-research to fetch and cite them, or research-brief to turn them into a decision-ready brief. Use when the user says: source-finder, source finder, source acquisition, source intake, find papers and datasets, find datasets and repos, find papers, find arxiv link.
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
1,790 tokensWhen the skill is activated
Reference documents
14,912 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesSKILL.mdcore8,600 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Source Finder
This is an OMH `source-finder` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`source-finder` exists so Hermes can turn vague source discovery requests into typed candidates, acquisition status, and downstream workflow choice without pretending OMH searched, downloaded, or verified the material.
## First Steps
- Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubomh-spend-gate
When your agent uses it
[omh] Spending money on the user's behalf -- a card checkout, an HTTP 402 or pay-per-request call, a wallet transfer, a booking, a paid data endpoint: show a pre-spend card (payee, total with fees, cap, refund terms, approver) first, and call it done only on an observed receipt. Use when the user says: spend-gate, spend gate, pre-spend, pre-spend card, spend cap, spending cap, spend limit, spending limit.
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
2,726 tokensWhen the skill is activated
Reference documents
1,142 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,651 bytesSKILL.mdcore11,651 bytesreferences/spend-rails.mddoc5,101 bytes
Read SKILL.md
# Spend Gate
This is an OMH `spend-gate` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`spend-gate` exists because money movement had at most one native guard, on one rail: where Hermes' saved-card fill is present it asks before filling a card and refuses when nobody can confirm, while an HTTP 402 call, a wallet transfer, a booking, or a paid data endpoint had no pre-spend check, no receipt rule, and no cap. `omh-provider-profile-posture` claims no payment at all.
## First Steps
- Check that a person can answer in this session; in a scheduled, webhook, API-server, single-query, background-worker, or subagent run, prepare the card and stop before any payment surface.
- Read the quote from its source and fill the pre-spend card from it, the cap included, before anything is submitted.
## Do Not Use WhenView the complete source on GitHubomh-sprite-forge
When your agent uses it
[omh] Character art to animate in a game: turn image-model sprite sheets into aligned, QC-gated frames with a fail-closed Pillow helper. Use when the user says: sprite-forge, sprite sheet, pixel sprite, pixel art character, game sprite frames, 2d sprite animation, 도트 캐릭터, 스프라이트 시트.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,700 tokensWhen the skill is activated
Reference documents
3,913 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Scripts executed separately
toolkit/scripts/forge.py
Files
SKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesSKILL.mdcore7,599 bytesreferences/character-art-direction.mddoc1,554 bytesreferences/execution-and-qa.mddoc2,293 bytesreferences/full-contract.mddoc3,123 bytesreferences/procedure.mddoc3,867 bytestoolkit/LICENSE.upstreamasset1,316 bytestoolkit/README.mddoc5,698 bytestoolkit/examples/layout.jsonasset357 bytestoolkit/scripts/forge.pyruns18,182 bytestoolkit/upstream-manifest.jsonasset2,559 bytes
Read SKILL.md
# Sprite Forge
This is an OMH `sprite-forge` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Image models return character poses at drifting scales and offsets, so frames cut by hand jitter in play. This skill couples a grid-sheet contract to a fail-closed processor whose numeric QC decides whether to regenerate the source.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md` before executing `toolkit/scripts/forge.py`; installation and skill discovery never run it.
- Obtain the raw sheet from the host's own image tool as a grid on flat #FF00FF; OMH generates no images, and a 1xN strip is regenerated as a grid, never processed.
- Record identity elements, rejected drafts, cell size and baseline in `references/character-art-direction.md` form before cutting frames.
View the complete source on GitHubomh-support-operations
When your agent uses it
[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
What it loads into context
Frontmatter
128 tokensAlways available to the agent
SKILL.md
1,325 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,323 bytesSKILL.mdcore6,323 bytes
Read SKILL.md
# Support Operations
This is an OMH `support-operations` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`support-operations` turns a bounded customer case into response and escalation guidance without treating drafts or recommendations as helpdesk actions.
## Do Not Use When
- The request clusters a backlog of customer signals to find product patterns or roadmap candidates; use `omh-feedback-triage`.
- The user only needs a generic, non-support marketing or email rewrite with no case, severity, or escalation context; use `omh-content-operator`.
- The request asks to send a reply, change ticket priority or status, issue a refund, modify an account, or update a helpdesk; use `omh-apps` with an explicit target and observed result.
- The request is an incident that is still open, needing severity declared, a commander assigned, and a running timeline rather than a support-case response; use `omh-live-incident-response`.View the complete source on GitHubomh-systematic-review
When your agent uses it
[omh] Literature screening against frozen criteria: two blind reviewers, a deterministic merge, open conflicts and agreement for systematic, scoping or rapid reviews. Use when the user says: systematic-review, systematic review, systematic literature review, scoping review, rapid review, prisma screening, title and abstract screening, inclusion and exclusion criteria screening.
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
1,645 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,767 bytes
Read SKILL.md
# Systematic Review
This is an OMH `systematic-review` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
Two reviewers screening the same records only count as dual review when neither sees the other's answers and the merge is mechanical. This workflow freezes the criteria first, keeps each reviewer blind, and never turns a missing answer into an exclusion.
## First Steps
- Agree the inclusion and exclusion criteria and the ordered exclusion codes with the person before any record is read; nothing is frozen until they say the criteria are final.
- Call `omh research screening freeze --criteria FILE --codes FILE --out DIR`. The protocol is write-once: a criteria change after freeze means a new DIR, never an edited protocol.json.
- Call `omh research screening prepare --dir DIR --records FILE --seed N`, then read DIR/manifest.json for the batch list.
- When `delegate_task` is in your tool list or tool_search finds it, dispatch two children, A and B: give each only its own `DIR/tasks/<A|B>/` files and tell it to write answer lines to `DIR/answers/<A|B>/`. Never pass one child the other's tasks, answers or name; without the tool, ask the person to run the two reviewers separately.View the complete source on GitHubomh-tech-debt-audit
When your agent uses it
[omh] Accumulated tech debt or architecture deepening to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
1,919 tokensWhen the skill is activated
Reference documents
2,244 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,634 bytesSKILL.mdcore8,634 bytesreferences/architecture-deepening.mddoc5,598 bytesreferences/debt-dimensions.mddoc4,180 bytes
Read SKILL.md
# Tech Debt Audit
This is an OMH `tech-debt-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`tech-debt-audit` exists so accumulated debt becomes a ranked, reconcilable ledger instead of a one-off complaint: findings cite file:line, severity and effort make the trade-off explicit, quick wins are separated from big fixes, and reruns mark what was resolved instead of rediscovering it.
## Do Not Use When
- The target is one diff, PR, or claim rather than the codebase's accumulated state; use `omh-code-review`.
- The user wants the debt removed now, behavior preserved; use `omh-ai-slop-cleaner` for deletion-first cleanup.
- A boundary-changing fix from the ledger needs its execution shaped into phases; use `omh-refactor-plan`.
- The question is release risk for a specific deploy rather than source quality; use `omh-production-audit`.View the complete source on GitHubomh-terminal
When your agent uses it
[omh] Shell command or test-suite execution: policy overlay for terminal commands - add cwd, environment, safety, and result-evidence gates after preferring native shell tools for ordinary CLI, package-manager, and test runs. Use when the user says: command-operator, command operator, terminal command, terminal task, shell command, shell task, cli command, command execution.
What it loads into context
Frontmatter
133 tokensAlways available to the agent
SKILL.md
2,138 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,199 bytes
Read SKILL.md
# Command Operator
This is an OMH `command-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`command-operator` exists because a host's own approval gate flags only some commands and can approve one with nobody asked: it fixes the working directory, environment, timeout, and stop condition, confirms every irreversible or externally visible command in chat whether or not the host flags it, records the host's own approval answer beside that confirmation, and reports results only from what the run returned.
## Do Not Use When
- An ordinary read-only or test command with a known working directory and nothing to gate; run it with the native terminal tool.
- The user pasted a failed command's output and asks for the cause; use `omh-build-failure-triage`, or `omh-agent-debug` when the agent itself is stuck.
- The user wants a command blocked for the agent from now on; use `omh-security-safety-review`, which prepares a proposed deny-glob list for the user to apply.
View the complete source on GitHubomh-toolbelt-readiness
When your agent uses it
[omh] Which tools and credentials a workflow needs: inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration. Use when the user says: toolbelt-readiness, mcp readiness, tool readiness, plugin readiness, connector readiness, needed mcp, api credential, missing cli.
What it loads into context
Frontmatter
135 tokensAlways available to the agent
SKILL.md
1,386 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,506 bytes
Read SKILL.md
# Toolbelt Readiness
This is an OMH `toolbelt-readiness` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`toolbelt-readiness` exists so the tools, CLIs, credentials, and connectors a workflow needs are listed as present, missing, optional, or unsafe before the work starts, instead of failing midway on a tool nobody checked.
## Do Not Use When
- One named integration needs assessing end to end before adoption; use `omh-external-connector-readiness`.
- The question is which coding owner should run the work.
- The user wants a tool installed, a credential validated, or a connector called now; the card names that step and who runs it, and performs none of them.
View the complete source on GitHubomh-verification-gate
When your agent uses it
[omh] Proof a change is done before merge: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge. Use when the user says: verification-gate, verification gate, quality gate, release gate, test gate, build lint test, lint typecheck tests, verify before merge.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
2,818 tokensWhen the skill is activated
Reference documents
4,979 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,992 bytesSKILL.mdcore12,992 bytesSKILL.mdcore12,992 bytesSKILL.mdcore12,992 bytesreferences/adaptation-quality.mddoc6,358 bytesreferences/generated-artifact-provenance.mddoc3,336 bytesreferences/requirement-coverage-map.mddoc5,761 bytesreferences/test-authoring.mddoc7,914 bytes
Read SKILL.md
# Verification Gate
This is an OMH `verification-gate` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`verification-gate` gives OMH a deterministic evidence surface before done/merge claims, inspired by ECC-style gates but rebuilt around OMH's prepared-versus-observed contract.
## Do Not Use When
- The user asks for visual render QA; use `omh-visual-qa`.
- The user asks for production release readiness beyond verification commands; use `omh-production-audit`.
- The user wants a bug-first code review of a diff; use `omh-code-review`.
View the complete source on GitHubomh-visual-qa
When your agent uses it
[omh] Rendered UI needing a visual verdict: prepare observed-only rendered QA gates for web, frontend, image, document, and TUI surfaces. Use when the user says: visual-qa, visual qa, visual QA, visual quality assurance, visual check, web qa, web visual qa, screenshot qa.
What it loads into context
Frontmatter
145 tokensAlways available to the agent
SKILL.md
3,628 tokensWhen the skill is activated
Reference documents
2,414 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore16,519 bytesSKILL.mdcore16,519 bytesSKILL.mdcore16,519 bytesSKILL.mdcore16,519 bytesreferences/motion-continuity.mddoc3,138 bytesreferences/playable-check.mddoc2,121 bytesreferences/visual-verdict-contract.mddoc4,898 bytes
Read SKILL.md
# Visual Qa
This is an OMH `visual-qa` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`visual-qa` gives OMH a completion gate for rendered surfaces so layout breaks, AI-looking polish gaps, CJK text problems, and mismatched-lineage screenshot claims cannot be mistaken for verified quality.
## Do Not Use When
- The user needs initial frontend design or redesign planning before implementation; use `omh-frontend`.
- The user needs a broad visual quality rubric before generation; use `omh-design-quality-gate`.
- The user needs image-card prompt creation; use `omh-image-cards`.
- The user wants non-visual code tests, CI, or PR review only; use the coding/review workflow.View the complete source on GitHubomh-voice-input
When your agent uses it
[omh] Dictated voice note about project work or status: terse voice and mobile-style requests - turn short spoken-style asks into clarify, plan, status, handoff, or confirmation actions. Use when the user says: voice-operator, voice operator, voice-first, voice command, mobile command, short command, dictated command, dictated request.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,302 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,160 bytes
Read SKILL.md
# Voice Operator
This is an OMH `voice-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`voice-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-web-research
When your agent uses it
[omh] Current technical or business fact to cite from web: web lookup lane - settle a current-facts question in one cited retrieval round with retrieval dates and source-quality notes; for pre-spec grounding across reference implementations use `research`. Use when the user says: web-research, web research, web search, search the web, internet search, look up, look up sources, latest sources.
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
2,383 tokensWhen the skill is activated
Reference documents
14,912 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesSKILL.mdcore11,124 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Web Research
This is an OMH `web-research` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`web-research` exists so a current-facts question returns a cited answer in one retrieval round, without the declared depth budget, reference-implementation study, and dossier that `research` requires.
## First Steps
- Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubomh-wiki
When your agent uses it
[omh] Scattered knowledge needing a wiki: wiki construction blueprints and retained knowledge capture with destination-aware external knowledge connection guidance. Use when the user says: wiki, project wiki, build a wiki, start a wiki, organize my notes, external knowledge store, knowledge base, Obsidian.
What it loads into context
Frontmatter
120 tokensAlways available to the agent
SKILL.md
1,451 tokensWhen the skill is activated
Reference documents
2,324 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,037 bytesSKILL.mdcore7,037 bytesSKILL.mdcore7,037 bytesreferences/wiki-blueprint.mddoc2,341 bytesreferences/wiki-operations.mddoc4,269 bytesreferences/wiki-patterns.mddoc4,056 bytes
Read SKILL.md
# Wiki
This is an OMH `wiki` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`wiki` exists to keep `knowledge` 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.
## ExamplesView the complete source on GitHubomh-workspace-audit
When your agent uses it
[omh] Workspace setup inventory and gaps: map repository, skill, prompt, plugin, MCP, hook, config, and runtime surfaces before strengthening or operating OMH. Use when the user says: workspace-audit, workspace audit, repo surface audit, repository surface audit, workspace surface audit, repo inventory, surface inventory, skill inventory.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,522 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,185 bytesSKILL.mdcore7,185 bytes
Read SKILL.md
# Workspace Audit
This is an OMH `workspace-audit` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`workspace-audit` gives OMH an ECC-inspired but OMH-native front door for understanding a large agent workspace before strengthening it, without turning inventory into hidden mutation or runtime proof.
## Do Not Use When
- The user already named a concrete implementation task with files and acceptance criteria; use the coding handoff or delivery workflow.
- The request is local OMH installation health only.
- The request is a source acquisition or current web lookup; use `omh-source-finder` or `ulw-research`.
View the complete source on GitHubulw-context
When your agent uses it
[omh] Repository vocabulary unclear or inconsistent: project terminology alignment workflow: look up, capture, correct, and align the words a repository uses before planning or handoff. Use when the user says: ulw-context, project terminology alignment, review project terms, align project terminology, terminology this project uses.
What it loads into context
Frontmatter
138 tokensAlways available to the agent
SKILL.md
2,096 tokensWhen the skill is activated
Reference documents
1,096 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesSKILL.mdcore11,018 bytesreferences/decision-frontier.mddoc3,503 bytesreferences/project-terms.mddoc1,925 bytes
Read SKILL.md
# Context
This is an OMH `context` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`context` exists to reduce repository terminology drift without creating a second machine store or a vocabulary router: the host can answer lookups, facilitate dependency-aware alignment, and project approved results into existing review and handoff boundaries.
## Do Not Use When
- A safe one-term definition or source lookup can be answered directly; use the read-only lookup mode and do not enter the full context interview.
- The request is broad ambiguity with no project-language conflict; use `ulw-interview`.
- The unresolved decision is empirical and a cheap isolated experiment can answer it; use `omh-decision-prototype` and keep the frontier for the rest.
- The terminology is already agreed and the request is to produce an implementation plan; use `ulw-plan`.View the complete source on GitHubulw-interview
When your agent uses it
[omh] Vague, underspecified request: one-question-at-a-time clarification. Use when the user says: deep-interview, interview me, clarify, feature shaping, ambiguous product request, one question, 要件を詰めて, 曖昧な要求.
What it loads into context
Frontmatter
113 tokensAlways available to the agent
SKILL.md
1,472 tokensWhen the skill is activated
Reference documents
1,013 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,052 bytesreferences/ambiguity-taxonomy.mddoc4,860 bytes
Read SKILL.md
# Deep Interview
This is an OMH `deep-interview` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`deep-interview` exists to stop the host from guessing through ambiguous product, workflow, or implementation intent; it converts uncertainty into a clarified brief before planning or handoff.
## Do Not Use When
- The request already has concrete scope, acceptance criteria, and verification commands.
- The missing information is discoverable from the repository or local artifacts without asking the user.
- The user asked for immediate read-only analysis and the ambiguity does not change the answer.
- The ambiguity is specifically repository terminology or project-language alignment; use `ulw-context` and its direct-lookup/frontier boundary.View the complete source on GitHubulw-loop
When your agent uses it
[omh] Ambitious project goal needing many build cycles: agentic interviewer -> planner -> researcher -> builder -> reviewer cycles until a real gate. Use when the user says: loop, goal loop, long horizon goal, never stop, research plan goal feedback, token exhaustion resume, permission profile, star 10k.
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
3,889 tokensWhen the skill is activated
Reference documents
5,597 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore18,999 bytesreferences/goal-constraint-discipline.mddoc5,024 bytesreferences/loop-design-review.mddoc15,428 bytesreferences/measured-loop-discipline.mddoc5,968 bytes
Read SKILL.md
# Loop
This is an OMH `loop` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`loop` exists for goals whose correct implementation cannot be known upfront but can be discovered through bounded cycles of definition, action, verification, and revision without confusing planned cycles with observed progress.
## Do Not Use When
- The user asks for one bounded delivery cycle; use `ulw-work`'s delivery-boundary capability instead.
- Scope and milestones are already known and only durable checkpoint/resume tracking is needed; use `ulw-work`'s durable-checkpoint capability.
- The user gives only a north-star outcome such as revenue, stars, or adoption and has not accepted a bounded first loop goal.
- The goal is too vague to name an observable problem, next artifact, verification signal, or stop condition.View the complete source on GitHubulw-perf
When your agent uses it
[omh] Software slowness, memory leaks, or cost spikes: find where a system is actually slow, leaking, or expensive across runtime, memory, token cost, storage, rendering, inference, CI, and query domains, then fix one measured hot path at a time behind a regression budget. Use when the user says: ultraperf, ulw-perf, performance audit, performance bottleneck, find the bottleneck, profile the hot path, memory leak investigation, token cost hotspot.
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,863 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,859 bytes
Read SKILL.md
# Ultraperf
This is an OMH `ultraperf` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ultraperf` exists because most performance work starts unlocalized: something is slow, leaking, or expensive and nobody knows where. It forces measurement before edits, one hypothesis at a time, executor-owned changes, and a regression budget, so an optimization loop cannot end in unverified claims.
## Do Not Use When
- The ask is to judge code quality, structure, or correctness rather than measured cost; use `omh-code-review`.
- The ask is to score model or agent output quality on a task suite.
- The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or one already-identified slow query or hotspot fix; handle it directly instead of opening a performance loop.
View the complete source on GitHubulw-plan
When your agent uses it
[omh] High-stakes technical proposal needing approval: consensus planning with review gates. Use when the user says: ralplan, consensus plan, reviewed plan, issue to PR, acceptance criteria, verification command, reviewable PR, risky planning.
What it loads into context
Frontmatter
106 tokensAlways available to the agent
SKILL.md
2,816 tokensWhen the skill is activated
Reference documents
1,189 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
../omh-verification-gate/references/adaptation-quality.mddoc6,358 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytesSKILL.mdcore13,604 bytes
Read SKILL.md
# Ralplan
This is an OMH `ralplan` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ralplan` exists to make planning reviewable before execution: the host should gather codebase/source facts, compare options, expose risks, define acceptance criteria, and prepare a handoff without pretending implementation already happened.
## First Steps
- Use the host task list or a durable checklist for repo facts, evidence gaps, options, risks, verification, and plan acceptance; keep one item active and insert research when evidence is missing. Checklist states are declarations, not execution evidence.
## Do Not Use When
View the complete source on GitHubulw-qa
When your agent uses it
[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.
What it loads into context
Frontmatter
108 tokensAlways available to the agent
SKILL.md
1,902 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,981 bytes
Read SKILL.md
# Ultraqa
This is an OMH `ultraqa` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ultraqa` exists because behavior that passes its own tests can still fail under inputs and conditions nobody wrote down: it turns the changed behavior and known risks into hostile scenarios, records each one's observed pass or fail apart from any proposed fix, and hands fixes to the selected coding executor.
## Do Not Use When
- Judging whether a rendered page, image, or terminal frame looks right across viewports and states; use `omh-visual-qa`.
- Confirming that a finished change meets its acceptance criteria with the smallest proving check, when no hostile scenarios are wanted; use `omh-verification-gate`.
## ExamplesView the complete source on GitHubulw-research
When your agent uses it
[omh] Deep dive before a decision: deep research engine - grounding for specs and decisions: study open-source reference implementations with pinned refs, gather live web evidence with citation discipline, verify contested claims, and distill a decision-grounding dossier that planning consumes; for a decision brief use research-brief, for upstream guidance use web-research. Use when the user says: research plan, literature review, research literature, review recent papers, deep research, deep-research, exhaustive research, saturation research.
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
4,092 tokensWhen the skill is activated
Reference documents
18,251 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesSKILL.mdcore19,972 bytesreferences/briefing-format.mddoc6,885 bytesreferences/evidence-records.mddoc8,668 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Research
This is an OMH `research` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`research` exists to make the host a careful research engine: it routes research demands to source-backed evidence gathering - from live web citations to studied reference implementations - verifies contested claims, and distills decision-grounding output so planning starts from evidence instead of guesses.
## First Steps
- When Hermes' bundled `grounded-citations` skill is available, set the citation ledger up before the first retrieval: choose one run-private file, have the parent reset it once (`sources.py --ledger <path> reset`), and declare parent-only writes in every lane brief. No lane resets it. Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubulw-work
When your agent uses it
[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.
What it loads into context
Frontmatter
155 tokensAlways available to the agent
SKILL.md
4,299 tokensWhen the skill is activated
Reference documents
2,066 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
../omh-verification-gate/references/adaptation-quality.mddoc6,358 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesSKILL.mdcore21,295 bytesreferences/dependency-topology.mddoc4,474 bytes
Read SKILL.md
# Ultrawork
This is an OMH `ultrawork` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
## Why This Exists
`ultrawork` exists to choose one-owner, ordered-dependency, or independent-frontier execution for an accepted implementation plan without letting concurrency blur ownership, verification, worker protocol, worktree isolation, or observed runtime evidence. It also carries four named internal capabilities absorbed from sibling engines: `coordinated_scope` (coordinated worker lanes), `delivery_boundary` (one bounded plan-to-PR cycle), `single_owner_persistence` (one owner finishes and verifies), and `durable_checkpoint` (durable goal ledger with checkpoints and a final gate).
## First Steps
- Initialize an English phase checklist through the host's task mechanism or a durable file: bootstrap, each implementation/verification lane, independent review, and evidence/cleanup close. Keep one outcome active and update declarations from observed results.
## Do Not Use When
View the complete source on GitHubdag-ulw
When your agent uses it
[omh] Large multi-part job to run on its own: plan it as a graph of small nodes, run the ready ones in parallel through Hermes' delegate_task, verify the goal with a separate node, and repair failed nodes before reporting. Use when the user says: dag-ulw, dag ulw, ulw dag, dag ultrawork, ultrawork dag, даг ультраворк, граф задач, задачи графом.
What it loads into context
Frontmatter
177 tokensAlways available to the agent
SKILL.md
3,064 tokensWhen the skill is activated
Reference documents
2,993 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesSKILL.mdcore13,786 bytesreferences/run-loop.mddoc12,217 bytes
Read SKILL.md
# Dag Ulw
This is a Hermes-native `dag-ulw` workflow skill.
## Why This Exists
`dag-ulw` exists so a big job runs end to end without the person driving it: the parent plans a graph OMH can validate and draw, runs the ready nodes in parallel on Hermes' own children, verifies the goal with a separate node, and repairs before it reports.
## First Steps
- Start at once; there is no plan approval. Write the goal criteria in one line.
- When the conversation holds a plan the user accepted (from `plan`, `ralplan` or `refactor-plan`), build the graph from it instead of re-planning: each task becomes a node with its id, depends_on and write scope, its done check goes into VERIFY and STOP WHEN, and its closing verification task becomes the `role: verify` node; plan only what it leaves open.
- Plan the graph and call `omh_dag action=define` with the complete run `goal` and each node's id, label, category, prompt, depends_on, write_scope and role (`build` by default; `baseline`, `verify`, `review`); fix every refusal and read the lint before going on. Never `delegate_task` before `define` returns its calls. The saved goal reaches every native task; local VERIFY does not replace goal acceptance.
- Keep the plan todo as the run's layers in ONE tool: `todo_list` when `todo_list` is in your tool list or tool_search finds it (OMH mirrors it), else `omh_todo`. One item per layer, named for what it delivers, never a list of its nodes (the panel draws those); advance it as each layer settles.View the complete source on GitHubomh-accessibility-audit
When your agent uses it
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces. Use when the user says: accessibility-audit, accessibility audit, a11y audit, a11y architect, wcag audit, wcag 2.2, wcag 2.2 aa, accessibility pass.
What it loads into context
Frontmatter
174 tokensAlways available to the agent
SKILL.md
2,682 tokensWhen the skill is activated
Reference documents
1,476 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,266 bytesSKILL.mdcore12,266 bytesSKILL.mdcore12,266 bytesreferences/a11y-rules.mddoc5,453 bytes
Read SKILL.md
# Accessibility Audit
This is a Hermes-native `accessibility-audit` workflow skill.
## Why This Exists
`accessibility-audit` adapts ECC's accessibility-architect posture into an OMH-native workflow so frontend quality includes WCAG, keyboard, screen-reader, pointer, contrast, and reflow gates without pretending a plan is observed compliance.
## Do Not Use When
- The user needs initial frontend design or redesign planning before accessibility-specific review; use `omh-frontend` first.
- The user needs rendered layout, screenshot, CJK, or pixel-diff QA rather than accessibility semantics; use `omh-visual-qa`.
- The user needs a broad premium-quality gate across web, deck, PDF, or posters; use `omh-design-quality-gate`.
- The user asks to implement accessibility fixes directly; prepare a selected executor/runtime handoff after the audit or use the coding workflow.View the complete source on GitHubomh-achievements
When your agent uses it
[omh] Hermes badges unlocked and achievement progress: achievements observation: summarize hermes-achievements badges, tiers, recent unlocks, and progress from local plugin artifacts. Use when the user says: achievements, achievement, badges, badge, my badges, show achievements, achievement summary, unlocked badges.
What it loads into context
Frontmatter
129 tokensAlways available to the agent
SKILL.md
1,467 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,964 bytes
Read SKILL.md
# Achievements
This is a Hermes-native `achievements` workflow skill.
## Why This Exists
`achievements` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-adversarial-consensus
When your agent uses it
[omh] Technical proposal facing adversarial scrutiny: independent perspectives attack a proposal, then distill into a bundle a separate planner consumes. Use when the user says: adversarial-consensus, adversarial planning, adversarial plan review, red team this plan, red-team this plan, red team the proposal, multi-perspective review, multiple perspectives.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
2,615 tokensWhen the skill is activated
Reference documents
1,478 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,356 bytesSKILL.mdcore12,356 bytesreferences/consensus-protocol.mddoc6,894 bytes
Read SKILL.md
# Adversarial Consensus
This is a Hermes-native `adversarial-consensus` workflow skill.
## Why This Exists
`adversarial-consensus` exists because agreement reached by perspectives that read each other is not review — it is convergence. Independent findings, an attack round nobody is allowed to defend against, and a distillation that may only subtract produce objections a single planning pass never surfaces, and the mandatory handoff keeps that bundle from being mistaken for the plan.
## Do Not Use When
- The user wants the plan itself, with options, acceptance criteria, and verification commands; use `ulw-plan`, which this workflow feeds.
- The request is still too ambiguous to state the proposal being attacked; use `ulw-interview` first.
- The user wants completed code reviewed for defects rather than a proposal attacked before it is built; use `omh-code-review`.
- The user wants hostile runtime scenarios against a built change; use `ulw-qa`.View the complete source on GitHubomh-agent-board
When your agent uses it
[omh] Coordinating several agents or profiles: coordinate multiple Hermes profiles or agents with task, handoff, heartbeat, blocker, and completion states. Use when the user says: agent-board, agent board, kanban, multi-agent, multi agent, multi agent board, multiple hermes agents, multiple hermes profiles.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,801 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,194 bytesSKILL.mdcore8,194 bytes
Read SKILL.md
# Agent Board
This is a Hermes-native `agent-board` workflow skill.
## Why This Exists
`agent-board` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
- A multi-lane implementation of an accepted plan is ultrawork, which prepares its durable lanes through this board.View the complete source on GitHubomh-agent-debug
When your agent uses it
[omh] Agent is stuck, looping, or drifting: capture a stuck, looping, drifting, or repeatedly failing agent run, diagnose the likely failure pattern, and prepare the smallest safe recovery action. Use when the user says: agent-debug, agent debug, agent debugging, agent introspection, agent self-debug, self-debug, self debugging, looping agent.
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,851 tokensWhen the skill is activated
Reference documents
1,421 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,835 bytesSKILL.mdcore8,835 bytesreferences/session-forensics.mddoc6,333 bytes
Read SKILL.md
# Agent Debug
This is a Hermes-native `agent-debug` workflow skill.
## Why This Exists
`agent-debug` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-agent-evaluation
When your agent uses it
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics. Use when the user says: agent-evaluation, agent evaluation, agent eval, agent benchmark, executor evaluation, executor benchmark, compare agents, compare codex claude.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,951 tokensWhen the skill is activated
Reference documents
1,426 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,515 bytesSKILL.mdcore9,515 bytesreferences/self-evaluation-loops.mddoc6,372 bytes
Read SKILL.md
# Agent Evaluation
This is a Hermes-native `agent-evaluation` workflow skill.
## Why This Exists
`agent-evaluation` gives OMH a way to improve executor choice empirically, not by vibes, while preserving executor-neutral product language across Codex, Claude Code, Hermes, and generic runtimes.
## Do Not Use When
- The user needs current runtime readiness only; use `omh-executor-runtime-readiness`.
- The user already selected an executor and wants implementation; use the coding handoff or delivery workflow.
- The user asks for workflow learning from a single failed route; use `omh-workflow-learning`.
- The ask is to find and fix runtime, memory, cost, or rendering hotspots rather than score executor or model output quality; use `ulw-perf`.View the complete source on GitHubomh-agent-instructions
When your agent uses it
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or marked unverified and no counts that drift. Use when the user says: agent-instructions, agents.md, claude.md, gemini.md, copilot-instructions.md, .cursorrules, cursor rules, cursor rule.
What it loads into context
Frontmatter
193 tokensAlways available to the agent
SKILL.md
1,939 tokensWhen the skill is activated
Reference documents
1,036 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,899 bytesSKILL.mdcore8,899 bytesreferences/instruction-file-method.mddoc4,250 bytes
Read SKILL.md
# Agent Instructions
This is a Hermes-native `agent-instructions` workflow skill.
## Why This Exists
`agent-instructions` exists because the file every handoff target reads first had no owner: `rules-distill` extracts rule candidates, `codebase-onboarding` builds a human reading path, and `context` aligns terminology, and each reads that file without writing it.
## First Steps
- List every instruction file and which agent reads it before proposing a section.
- Run or ask for the observed run of each command before marking it verified.
## Do Not Use WhenView the complete source on GitHubomh-agent-ops-review
When your agent uses it
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers. Use when the user says: agent-ops-review, agent ops review, agent productivity, operator productivity, manager view, quality dashboard, throughput review, agent work quality.
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,754 tokensWhen the skill is activated
Reference documents
801 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,053 bytesSKILL.mdcore8,053 bytesSKILL.mdcore8,053 bytesreferences/instrumentation-ladder.mddoc3,615 bytes
Read SKILL.md
# Agent Ops Review
This is a Hermes-native `agent-ops-review` workflow skill.
## Why This Exists
`agent-ops-review` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-ai-job-search
When your agent uses it
[omh] Career search to interview: find verified opportunities, tailor evidence-grounded applications and track confirmed outcomes. Use when the user says: ai-job-search, job search, evaluate this job posting, tailor my resume, tailor my cv, prepare for my job interview, track my job applications, draft my cover letter.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,159 tokensWhen the skill is activated
Reference documents
7,462 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/scripts/job_state.py
Files
SKILL.mdcore5,735 bytesSKILL.mdcore5,735 bytesSKILL.mdcore5,735 bytesreferences/execution-and-qa.mddoc4,032 bytesreferences/fit-and-drafting.mddoc2,507 bytesreferences/full-contract.mddoc3,000 bytesreferences/interview-and-outcomes.mddoc2,063 bytesreferences/procedure.mddoc4,038 bytesreferences/profile-and-discovery.mddoc3,511 bytestoolkit/LICENSE.upstreamasset1,071 bytestoolkit/README.mddoc17,066 bytestoolkit/examples/synthetic-captures.jsonasset1,341 bytestoolkit/scripts/job_state.pyruns34,247 bytestoolkit/upstream-manifest.jsonasset2,447 bytes
Read SKILL.md
# Ai Job Search
Required: requested career action, supported candidate facts and preferences, approved private workspace and source scope. Output: profile.md and preferences.md, jobs.json and shortlist.md, versioned application drafts and review.md, interview-prep.md and optional skill-gaps.md, evidence-bound tracker and next actions.
**Do Not Use When:** For citation attribution alone, use the bundled `grounded-citations` skill.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
Cross-session career work needs stable posting identity, candidate-evidence links and a strict boundary between prepared applications and confirmed events.
## First Steps
View the complete source on GitHubomh-ai-slop-cleaner
When your agent uses it
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical. Use when the user says: ai-slop-cleaner, cleanup, deslop, refactor, risky, behavior-preserving refactor, risk analysis, refactor workflow.
What it loads into context
Frontmatter
173 tokensAlways available to the agent
SKILL.md
3,023 tokensWhen the skill is activated
Reference documents
2,924 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore13,827 bytesSKILL.mdcore13,827 bytesreferences/cleanup-passes.mddoc5,850 bytesreferences/prose-lexicon.mddoc4,452 bytesreferences/ui-review-checklist.mddoc2,521 bytes
Read SKILL.md
# Ai Slop Cleaner
This is a Hermes-native `ai-slop-cleaner` workflow skill.
## Why This Exists
`ai-slop-cleaner` exists to keep `maintenance` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The goal is new or changed behavior rather than removing existing code; a plain refactor, feature, or fix request belongs to `ulw-work`.
- The cleanup would change architecture or module boundaries and needs its execution shaped into phases first; use `omh-refactor-plan`, or `ulw-plan` when the direction itself is still contested.
- The user wants code judged for bugs or merge readiness with no drafted slop removal to inspect; use `omh-code-review` for a bug-first review and `omh-failure-signal-audit` for swallowed failures.
- The user asks to simplify their own recent changes, a commit, or the staged diff with a reuse, quality, and efficiency pass rather than a behavior-locked removal of existing code; load Hermes' bundled `simplify-code` skill for that instead of this one.View the complete source on GitHubomh-app-debugging
When your agent uses it
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the demonstrated root cause. Use when the user says: app-debugging, app debugging, application debugging, root cause, root-cause, find the root cause, root cause analysis, flaky test.
What it loads into context
Frontmatter
190 tokensAlways available to the agent
SKILL.md
2,915 tokensWhen the skill is activated
Reference documents
3,501 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore13,552 bytesSKILL.mdcore13,552 bytesreferences/debugging-skill-composition.mddoc2,099 bytesreferences/hypothesis-and-race-method.mddoc13,912 bytes
Read SKILL.md
# App Debugging
This is a Hermes-native `app-debugging` workflow skill.
## Why This Exists
`app-debugging` exists because a wrong result in application code had no owner: `native-debugging` covers native binaries, `build-failure-triage` covers red builds, and `agent-debug` covers agent misbehaviour, so the most common debugging request dispatched straight to an execution lane that skipped the diagnosis.
## First Steps
- Ask for, or plan, the one command that shows the wrong behaviour, and record its observed output before naming a cause.
- Refuse to prepare a fix while the reproduction reads not_observed; plan the observation that would establish it instead.
## Do Not Use WhenView the complete source on GitHubomh-apple-design
When your agent uses it
[omh] Designing or reviewing an iOS, macOS, or Apple-style UI: prepare native Apple UI or Apple marketing product-visual direction, review, and improvement briefs with evidence-backed remediation handoffs. Use when the user says: apple-design, apple design, apple ui design, apple hig, human interface guidelines, ios design guidelines, macos app design, apple-inspired web.
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,873 tokensWhen the skill is activated
Reference documents
3,781 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,268 bytesSKILL.mdcore9,268 bytesSKILL.mdcore9,268 bytesSKILL.mdcore9,268 bytesreferences/materials-and-accessibility.mddoc2,411 bytesreferences/platform-foundations.mddoc2,902 bytesreferences/product-visual-production.mddoc5,101 bytesreferences/review-playbook.mddoc2,405 bytesreferences/web-production-libraries.mddoc4,531 bytes
Read SKILL.md
# Apple Design
This is a Hermes-native `apple-design` workflow skill.
## Why This Exists
`apple-design` turns Apple UI design, review, and improvement requests into a platform-aware brief that respects native and web differences while preserving OMH's existing implementation and evidence owners.
## Do Not Use When
- The request is generic frontend design, accessibility, screenshot QA, image-card work, or material guidance without an Apple-specific phrase or explicit `omh-apple-design` invocation; use the existing specialist lane.
- The message concerns Apple fruit, stock, support, a glass database, material science, or unrelated Swift/macOS discussion.
- The user needs a conformance, accessibility PASS, or visual PASS claim without supplied and observed evidence.
View the complete source on GitHubomh-application-threat-model
When your agent uses it
[omh] Attack paths into an operated system: turn a system's components and data flows into assets, trust boundaries, attack scenarios, controls, and the security test that proves each control holds. Use when the user says: application-threat-model, application threat model, threat model, threat modeling, threat modelling, threat modeling session, threat modeling workshop, security threat model.
What it loads into context
Frontmatter
184 tokensAlways available to the agent
SKILL.md
2,259 tokensWhen the skill is activated
Reference documents
1,147 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,830 bytesreferences/threat-model-method.mddoc5,328 bytes
Read SKILL.md
# Application Threat Model
This is a Hermes-native `application-threat-model` workflow skill.
## Why This Exists
`application-threat-model` exists because the nearest neighbour does not merely miss this request. `security-safety-review` maps the agent's own prompt, tool, credential, and dependency surface, so an application threat-model request came back as an agent tool inventory under a near-identical name — a confident wrong artifact rather than a miss, in the one domain where that costs most.
## Do Not Use When
- The subject is the agent's own prompts, tools, files, credentials, dependencies, or destructive actions; use `omh-security-safety-review`, which maps that runtime surface.
- The user wants defects found in a diff or a file; use `omh-code-review`.
- The user asks whether a release is ready across rollout, rollback, and observability; use `omh-production-audit`.
- The user asks which commands prove a merge is safe; use `omh-verification-gate`.View the complete source on GitHubomh-apps
When your agent uses it
[omh] Email, Slack, or Jira action to perform: external app actions - email, Slack, Discord, Notion, Linear, Jira, CRM, and similar providers, scoped with auth, payload, confirmation, and result-evidence gates. Use when the user says: connector-operator, connector operator, external app action, external connector action, saas action, api action, send email, email customer.
What it loads into context
Frontmatter
175 tokensAlways available to the agent
SKILL.md
1,979 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,331 bytesSKILL.mdcore9,331 bytes
Read SKILL.md
# Connector Operator
This is a Hermes-native `connector-operator` workflow skill.
## Why This Exists
`connector-operator` exists because an email sent, a ticket written, or an invite delivered cannot be taken back: it scopes the provider, target, and payload, takes a missing connection to the host's own connection setup and respects a skip, and reports delivery only from a provider receipt.
## Do Not Use When
- Only the reply or thread policy of a Discord, Slack, or Telegram conversation is in question; use `omh-gateway-intent-card`.
- The user is choosing or adopting a new provider, MCP server, or integration rather than acting through one; use `omh-external-connector-readiness`.
## ExamplesView the complete source on GitHubomh-ask
When your agent uses it
[omh] Outside AI critique wanted: consulting an external advisor when configured. Use when the user says: ask, external advisor, ask claude, ask gemini, consult claude, consult gemini, opinion from claude, opinion from gemini.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,437 tokensWhen the skill is activated
Reference documents
360 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,700 bytesSKILL.mdcore6,700 bytesSKILL.mdcore6,700 bytesSKILL.mdcore6,700 bytesreferences/cli-advisors.mddoc1,586 bytes
Read SKILL.md
# Ask
This is a Hermes-native `ask` workflow skill.
## Why This Exists
`ask` exists to put one outside model's critique beside the agent's own answer when the user wants it, as advice the agent weighs in the open rather than a verdict it adopts, from the advisor the user named or configured and never from a default one.
## 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.
- The user wants typed yes/no, pick-one, or scored probabilities from Jev over supplied text; use `omh-jev-ask`.
View the complete source on GitHubomh-automation-blueprint
When your agent uses it
[omh] Recurring Hermes job on a schedule (cron, digests): design recurring Hermes operations with schedule, delivery, silence policy, context chain, and prepared-vs-observed status. Use when the user says: automation-blueprint, scheduled ops, scheduled operation, scheduled operations, automation blueprint, cron blueprint, cron-ready, recurring ops.
What it loads into context
Frontmatter
180 tokensAlways available to the agent
SKILL.md
2,639 tokensWhen the skill is activated
Reference documents
2,328 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,124 bytesSKILL.mdcore12,124 bytesSKILL.mdcore12,124 bytesSKILL.mdcore12,124 bytesSKILL.mdcore12,124 bytesSKILL.mdcore12,124 bytesreferences/recurring-surface-choice.mddoc10,014 bytes
Read SKILL.md
# Automation Blueprint
This is a Hermes-native `automation-blueprint` workflow skill.
## Why This Exists
`automation-blueprint` exists so a recurring request reaches Hermes' own Automation Blueprints and cron with the decisions they leave open (overlap, missed run, retry, backfill, failure pause, silence) settled first, without OMH becoming a hidden cron runner, transport bot, source retriever, or executor.
## Do Not Use When
- An undecided lifecycle journey or growth experiment needs audience, consent, and measurement design before any schedule; use `omh-lifecycle-growth` first.
- The user needs a one-off report or deck; use `omh-report-package` or `omh-materials-package`.
- The user asks to review incident metrics once; use `omh-reliability-review`.
- The user needs actual code changes; prepare a selected executor/runtime handoff after the blueprint or plan is accepted.View the complete source on GitHubomh-award-bar-score
When your agent uses it
[omh] Aiming for design-award quality: score a web surface against published design-award judging axes and name the binding constraint. Use when the user says: award-bar-score, award bar score, award winning, award-winning, award winning website, award-winning website, award winning design, award ready.
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
1,884 tokensWhen the skill is activated
Reference documents
1,703 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,705 bytesreferences/award-judging-model.mddoc6,169 bytes
Read SKILL.md
# Award Bar Score
This is a Hermes-native `award-bar-score` workflow skill.
## Why This Exists
`award-bar-score` gives "make it award-winning" a measurable meaning: published axes, published weights, a published threshold, and the one axis holding the surface below it — instead of a taste argument nobody can settle.
## Do Not Use When
- The request is broad premium quality across decks, PDFs, or posters; use `omh-design-quality-gate`.
- The request is frontend implementation, layout, or design-system work; use `omh-frontend`.
- The request is WCAG, keyboard, or screen-reader conformance; use `omh-accessibility-audit`.
- The request is a rendered capture or a pixel verdict; use `omh-visual-qa`.View the complete source on GitHubomh-backend
When your agent uses it
[omh] Designing an API, server, or data-layer change: prepare server, API, and data-layer contracts — auth boundary, error paths, response shape, and schema/migration discipline — before implementation. Use when the user says: backend, back-end, back end, backend skill, server side, server-side, api design, api contract.
What it loads into context
Frontmatter
180 tokensAlways available to the agent
SKILL.md
2,787 tokensWhen the skill is activated
Reference documents
6,863 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,880 bytesSKILL.mdcore12,880 bytesreferences/consumer-impact.mddoc3,879 bytesreferences/contract-tests.mddoc4,553 bytesreferences/inbound-and-async.mddoc5,790 bytesreferences/schema-migration.mddoc3,299 bytesreferences/service-contract.mddoc14,537 bytes
Read SKILL.md
# Backend
This is a Hermes-native `backend` workflow skill.
## Why This Exists
`backend` gives OMH a first-class server-side workflow so Hermes can prepare auth boundaries, error paths, response shapes, and migration order without becoming the hidden runtime that executes them.
## Do Not Use When
- The work is the database itself -- a slow query and the index that fixes it, DDL that locks a live table, N+1 queries, or when to partition or shard; use `omh-relational-db`, which owns the lock behaviour and rollback of each statement.
- The request is about web UI, layout, or a design system; use `omh-frontend`.
- The request is a security posture or threat review rather than a service design; use `omh-security-safety-review`.
- The request is to run or judge the verification of an already-built service; use `omh-verification-gate`.View the complete source on GitHubomh-biomedical-evidence
When your agent uses it
[omh] Public variant claims to cross-check: retrieve and reconcile source-labelled biomedical evidence with identity, conflict and freshness checks. Use when the user says: biomedical-evidence, biomedical evidence reconciliation, ClinVar cross-check, variant evidence matrix, BioMCP capture reconciliation.
What it loads into context
Frontmatter
143 tokensAlways available to the agent
SKILL.md
1,205 tokensWhen the skill is activated
Reference documents
3,920 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/scripts/reconcile.py
Files
SKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesSKILL.mdcore6,060 bytesreferences/execution-and-qa.mddoc3,131 bytesreferences/full-contract.mddoc3,242 bytesreferences/procedure.mddoc4,140 bytestoolkit/README.mddoc7,790 bytestoolkit/scripts/reconcile.pyruns19,519 bytestoolkit/upstream-manifest.jsonasset3,060 bytes
Read SKILL.md
# Biomedical Evidence
Required: public gene/variant and disease query, bounded BioMCP capture workspace, intended entity identifiers and source scope. Output: biomedical_evidence_matrix/v1, biomedical_reconciliation_manifest/v1.
**Do Not Use When:** For citation verification and source attribution alone, load Hermes' bundled `grounded-citations` skill.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
Public sources can disagree about a variant while describing different alleles, diseases or assertion domains. Preserve those differences and their provenance before any synthesis; a fetched record is not a clinical recommendation.
## First Steps
View the complete source on GitHubomh-browser
When your agent uses it
[omh] Browser login, click, or form task: policy overlay for browser tasks - add auth, confirmation, and observed-trace gates after preferring the native browser for ordinary URL, click, login, and form actions. Use when the user says: browser-operator, browser operator, browser task, browser operation, browser automation, browser session, webpage operation, web page operation.
What it loads into context
Frontmatter
171 tokensAlways available to the agent
SKILL.md
2,217 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,087 bytesSKILL.mdcore10,087 bytes
Read SKILL.md
# Browser Operator
This is a Hermes-native `browser-operator` workflow skill.
## Why This Exists
`browser-operator` exists because native browser tools act on a live page with no scope, sign-in boundary, or trace requirement of their own: it fixes the URL, allowed actions, and stop condition, sends sign-ins and saved cards to Hermes' credential vault so secrets never pass through chat, and counts only observed page evidence.
## Do Not Use When
- An ordinary read of a public page with no sign-in, form, or purchase; use the native browser tools directly unless OMH's browser adapter bridge is enabled, which blocks them.
- The question is whether a page looks right at each viewport; use `omh-visual-qa`.
- A web lookup or a cited answer rather than an interaction with a page; use `omh-web-research`.
- A page step that moves money -- a checkout, a payment, a booking deposit, a top-up; use `omh-spend-gate`, which shows the pre-spend card and takes the person's typed yes even when Hermes prompts on its own.View the complete source on GitHubomh-build-failure-triage
When your agent uses it
[omh] Build or CI failure to triage: classify build, typecheck, lint, test, CI, and DCO failures into minimal safe fix handoffs. Use when the user says: build-failure-triage, build failure triage, build failure, build-failure, build fix, build failed, build failing, compile error.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
2,698 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,851 bytesSKILL.mdcore11,851 bytesSKILL.mdcore11,851 bytes
Read SKILL.md
# Build Failure Triage
This is a Hermes-native `build-failure-triage` workflow skill.
## Why This Exists
`build-failure-triage` adapts ECC's build-fix and PR-test-analysis posture into an OMH-native workflow so failed checks become evidence-backed minimal handoffs instead of ad hoc debugging or false-green verification claims.
## Do Not Use When
- The user needs a pre-merge evidence matrix for passing or missing checks; use `omh-verification-gate`.
- The user needs a code review of changed behavior rather than failing command triage; use `omh-code-review`.
- The user needs broad production readiness; use `omh-production-audit`.
- The user asks for incident or SLO review after deployment; use `omh-reliability-review`.View the complete source on GitHubomh-buzz
When your agent uses it
[omh] Buzz community agent setup or relay trouble: connect and operate Hermes as a native Buzz community agent, deliver local media with verified relay receipts, or diagnose a self-hosted Buzz relay without inventing transport evidence. Aliases: omh-buzz. Use when the user says: connect Hermes to Buzz, Buzz community agent, Buzz gateway setup, Buzz media attachment, Buzz relay self-hosting, Buzz connection diagnostics, 버즈 커뮤니티 연결, Buzz 메시지 첨부.
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
1,670 tokensWhen the skill is activated
Reference documents
1,520 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Choose One Internal Lane
- Ownership Boundary
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,145 bytesreferences/media.mddoc2,571 bytesreferences/self-host.mddoc1,835 bytesreferences/setup.mddoc2,967 bytes
Read SKILL.md
# Buzz
This is a Hermes-native `buzz` workflow skill.
## Why This Exists
Hermes already owns the Buzz transport, but users need one discoverable OMH entry point that safely selects setup, attachment, or self-host operations and reports only the evidence actually observed.
## Do Not Use When
- The user wants a Buzz-managed ACP runtime rather than Hermes' native Buzz gateway.
- The request is general media editing with no Buzz delivery target.
- The request is generic Docker or Nostr advice unrelated to a Buzz relay.
- The user is only asking whether OMH supports Buzz, with no request to run the workflow.View the complete source on GitHubomh-cancel
When your agent uses it
[omh] Aborting an active workflow: ending active workflow state cleanly. Use when the user says: cancel, stop the workflow, abort the run, cancel the loop.
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
1,441 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,501 bytesSKILL.mdcore6,501 bytes
Read SKILL.md
# Cancel
This is a Hermes-native `cancel` workflow skill.
## Why This Exists
`cancel` exists so a request to stop ends the right thing: OMH clears the state this session owns, and work the host owns stops through the person's own host command, so nothing reads as stopped before a record or the host's own reply says it is.
## Do Not Use When
- The workflow finished and its outcome should be kept; record it with omh state finish instead of clearing it.
- The user wants to see what is still running rather than stop it; use `omh-running-work-board`.
- The user means cancelling something in their own product or accounts, such as an order, a subscription, or a meeting, rather than OMH or host work.
View the complete source on GitHubomh-capability-toggle
When your agent uses it
[omh] Tailoring enabled OMH families: turning one OMH capability family on or off so an install can be tailored instead of taken whole. Use when the user says: capability-toggle, capability policy, disable memory, enable memory, disable coding orchestration, disable a capability family, enable a capability family, 메모리 기능 꺼줘.
What it loads into context
Frontmatter
137 tokensAlways available to the agent
SKILL.md
1,339 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,273 bytes
Read SKILL.md
# Capability Toggle
This is a Hermes-native `capability-toggle` workflow skill.
## Why This Exists
`capability-toggle` exists because OMH shipped one binary install lever -- 9 core skills or all of them -- so a user who wanted the coding surface but not the memory surface had to take both. It turns that into a per-family choice without uninstalling OMH.
## Do Not Use When
- The user wants to run the workflow a family owns rather than change whether that family is offered.
- The user is asking to build an on/off switch inside their own product.
- The user wants OMH removed entirely, which is the uninstall path rather than a capability policy change.
- The user wants one skill hidden on one messaging platform or everywhere; that is Hermes' own hermes skills config, an interactive command the person runs in a terminal, and OMH writes no Hermes config.View the complete source on GitHubomh-code-review
When your agent uses it
[omh] Pull request or changes to vet: bug-first review with evidence. Use when the user says: code-review, review, audit, find bugs, release gate, claim audit, evidence audit, README claim.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
2,741 tokensWhen the skill is activated
Reference documents
9,707 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,633 bytesSKILL.mdcore12,633 bytesSKILL.mdcore12,633 bytesreferences/architecture-delta.mddoc5,026 bytesreferences/finding-validation.mddoc3,893 bytesreferences/native-review-contract.mddoc7,360 bytesreferences/review-dispatch.mddoc11,603 bytesreferences/review-lenses.mddoc5,315 bytesreferences/review-response.mddoc2,425 bytesreferences/risk-selection.mddoc4,239 bytesreferences/smell-baseline.mddoc4,508 bytes
Read SKILL.md
# Code Review
This is a Hermes-native `code-review` workflow skill.
## Why This Exists
`code-review` exists to make review bug-first and evidence-grounded: findings must cite concrete files, diffs, commands, or artifacts before any summary or fix proposal.
## Do Not Use When
- The user asks to implement the fix rather than review existing code or claims.
- There is no diff, file set, claim, artifact, or expected behavior to review.
- The request is broad product critique, strategy, or planning rather than code or evidence review.
- A kanban review worker needs its card's transition decided: Hermes' bundled `sdlc-review` owns approve, request-changes, and escalate there, and this skill only supplies the findings that decision cites.View the complete source on GitHubomh-codebase-onboarding
When your agent uses it
[omh] Unfamiliar repository needing a guided tour: create a repo map, reading path, glossary, risk map, and first-task runway for unfamiliar codebases. Use when the user says: codebase-onboarding, codebase onboarding, repo onboarding, repository onboarding, codebase tour, code tour, new repo orientation, understand this repo.
What it loads into context
Frontmatter
171 tokensAlways available to the agent
SKILL.md
1,997 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Structural Code Search
- Runtime Evidence
Files
SKILL.mdcore9,051 bytesSKILL.mdcore9,051 bytesSKILL.mdcore9,051 bytesSKILL.mdcore9,051 bytesSKILL.mdcore9,051 bytes
Read SKILL.md
# Codebase Onboarding
This is a Hermes-native `codebase-onboarding` workflow skill.
## Why This Exists
`codebase-onboarding` adapts ECC's code-tour and onboarding surfaces into an OMH-native first-read workflow so unfamiliar repos become navigable before implementation pressure starts.
## Do Not Use When
- The user already named a concrete implementation task and acceptance criteria; use `ulw-work` or `omh-idea-to-deploy`.
- The user needs a whole-workspace capability inventory; use `omh-workspace-audit`.
- The user wants a code diff review; use `omh-code-review`.
View the complete source on GitHubomh-codebase-uml
When your agent uses it
[omh] Architecture picture of a codebase: turn a repository into one readable, interface-level PlantUML architecture picture - packages or modules, the public symbols other units actually import, bounded import edges - and get it rendered to a single PNG a chat surface can show. Use when the user says: codebase-uml, codebase uml, uml, plantuml, uml diagram, class diagram, package diagram, module diagram.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
2,340 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,179 bytesSKILL.mdcore10,179 bytesSKILL.mdcore10,179 bytesSKILL.mdcore10,179 bytes
Read SKILL.md
# Codebase Uml
This is a Hermes-native `codebase-uml` workflow skill.
## Why This Exists
`codebase-uml` exists so 'visualize our codebase' produces one deterministic, readable picture instead of a hand-drawn guess: the interface each unit exposes is ranked by who imports it, the layout is bounded before PlantUML sees it, and every omission the bounding made is printed on the image.
## Do Not Use When
- The user wants the local code index refreshed or a task-scoped handoff pack, not a picture; use `omh-codegraph-refresh`.
- The user wants a narrative first-read tour, reading path, or glossary; use `omh-codebase-onboarding`.
- The user wants a summary card, thumbnail, or explainer image of a PR, meeting, or release rather than a structural diagram; use `omh-image-cards`.
- The user describes a system, cloud, or infrastructure architecture in words and wants it drawn as a styled diagram, with no repository to read the structure from; load Hermes' bundled `architecture-diagram` skill instead of this one.View the complete source on GitHubomh-codegraph-refresh
When your agent uses it
[omh] Outdated code index or codemap: refresh local code intelligence, summarize repo structure, and prepare task-scoped codegraph handoff context without overclaiming execution. Use when the user says: codegraph-refresh, codegraph refresh, refresh codegraph, update codegraph, codegraph stale, stale codegraph, codegraph handoff, codegraph summary.
What it loads into context
Frontmatter
180 tokensAlways available to the agent
SKILL.md
1,903 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Structural Code Search
- Runtime Evidence
Files
SKILL.mdcore8,675 bytesSKILL.mdcore8,675 bytes
Read SKILL.md
# Codegraph Refresh
This is a Hermes-native `codegraph-refresh` workflow skill.
## Why This Exists
`codegraph-refresh` adapts ECC-style codemap freshness into OMH's local codegraph commands so operators can refresh navigation context before handoff without pretending code intelligence is execution evidence.
## Do Not Use When
- The user needs a narrative first-read tour of an unfamiliar repo; use `omh-codebase-onboarding`.
- The user already has accepted implementation criteria and wants code changes; use `ulw-work` or a coding handoff.
- The user asks for visual, frontend, or rendered UI QA; use `omh-frontend`, `omh-design-quality-gate`, or `omh-visual-qa`.
View the complete source on GitHubomh-commit-pr-authoring
When your agent uses it
[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with `Tested:` listing only commands observed to run and everything prepared but not run under `Not-tested:`. Use when the user says: commit-pr-authoring, commit message, commit messages, write the commit message, draft the commit message, commit body, squash message, pr body.
What it loads into context
Frontmatter
190 tokensAlways available to the agent
SKILL.md
2,101 tokensWhen the skill is activated
Reference documents
1,274 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,332 bytesreferences/commit-and-pr-conventions.mddoc5,419 bytes
Read SKILL.md
# Commit Pr Authoring
This is a Hermes-native `commit-pr-authoring` workflow skill.
## Why This Exists
`commit-pr-authoring` exists because nothing in the catalog authored the commit or the PR body. `code-review` reads a commit message as a thing to review and `github-event-ops` routes PR events, so the text an engineer writes several times a day had no owner, and nothing applied the observed-versus-prepared split to it.
## First Steps
- Read the PR template and the recent log, and record the convention before drafting.
- Build the evidence ledger: each command, observed with its exit status or not_observed.
## Do Not Use WhenView the complete source on GitHubomh-content-operator
When your agent uses it
[omh] Product or company copy to publish or rewrite: scope publish-ready writing, rewriting, summarization, translation, release-note, newsletter, customer-copy, social-copy, README-copy, and email-draft work with audience, tone, style, source, review, and hallucination gates. Use when the user says: content-operator, content operator, content workflow, writing workflow, publish-ready writing, publish ready writing, release notes, release note draft.
What it loads into context
Frontmatter
172 tokensAlways available to the agent
SKILL.md
1,876 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytesSKILL.mdcore8,809 bytes
Read SKILL.md
# Content Operator
This is a Hermes-native `content-operator` workflow skill.
## Why This Exists
`content-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
- The user wants a draft to stop sounding machine-written - strip AI tells or match their own voice - with no audience, source, or review gate to scope; load Hermes' bundled `humanizer` skill instead of this one.View the complete source on GitHubomh-context-budget-review
When your agent uses it
[omh] Context window or token budget at risk: plan compact context, token/cost budgets, summarization checkpoints, and overflow recovery before long agent work. Use when the user says: context-budget-review, context budget review, context budget, token budget review, token budget, prompt budget, prompt caching, prompt cache.
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
2,081 tokensWhen the skill is activated
Reference documents
1,548 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,923 bytesSKILL.mdcore9,923 bytesSKILL.mdcore9,923 bytesreferences/cache-placement.mddoc1,855 bytesreferences/route-capacity.mddoc5,017 bytes
Read SKILL.md
# Context Budget Review
This is a Hermes-native `context-budget-review` workflow skill.
## Why This Exists
`context-budget-review` ports ECC's context-budget and token-budget instincts into OMH as a compactness gate that protects long-running work without redefining success around a smaller task.
## Do Not Use When
- The user asks only what this Hermes session has used or cost so far; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user asks to continue a loopable goal; use `ulw-loop` unless budget planning is the explicit blocker.
- The task is a short one-step answer with no meaningful context risk.
View the complete source on GitHubomh-cto-loop
When your agent uses it
[omh] Engineering leadership over roadmap and risk: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence. Use when the user says: cto-loop, cto loop, cto, cto pm, pm dev qa security ops, roadmap technical tradeoffs, technical tradeoff, delivery risk.
What it loads into context
Frontmatter
147 tokensAlways available to the agent
SKILL.md
1,408 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,605 bytesSKILL.mdcore6,605 bytes
Read SKILL.md
# Cto Loop
This is a Hermes-native `cto-loop` workflow skill.
## Why This Exists
`cto-loop` exists to keep `leadership` 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 a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly or use `omh-decide` for a decision brief instead of starting a leadership operating loop.
## Examples
View the complete source on GitHubomh-curriculum-design
When your agent uses it
[omh] Team training or course that needs a syllabus: turn a learning goal into a teachable curriculum, assessment plan, and learner-ready sequence. Use when the user says: curriculum design, learning objectives, assessment plan, 커리큘럼 설계, 학습 목표, 평가 계획.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
1,520 tokensWhen the skill is activated
Reference documents
1,493 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,395 bytesSKILL.mdcore7,395 bytesreferences/procedure.mddoc7,012 bytes
Read SKILL.md
# Curriculum Design
This is a Hermes-native `curriculum-design` workflow skill.
## Why This Exists
`curriculum-design` makes outcomes, sequence, assessment, and constraints reviewable before materials or LMS work.
## Do Not Use When
- The user wants an explanation of a supplied academic paper rather than a teachable sequence; use `omh-paper-learning`.
- The user needs a deck, workbook, PDF, or other exported learning artifact; route packaging to `omh-materials-package` after the curriculum is accepted.
- The user asks to create or publish an LMS course, enroll students, grade work, or change course settings; use `omh-apps` with explicit authorization and observed evidence.
- The user needs only a short rewrite or one isolated worksheet prompt, not curriculum structure; use `omh-content-operator`.View the complete source on GitHubomh-data-analysis
When your agent uses it
[omh] Dataset or table to analyze: scope supplied data with provenance, causal-claim, and hallucination guards. Use when the user says: data-analysis, data analysis, dataset analysis, csv analysis, json analysis, log analysis, table analysis, analyze csv.
What it loads into context
Frontmatter
122 tokensAlways available to the agent
SKILL.md
1,632 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,699 bytesSKILL.mdcore7,699 bytes
Read SKILL.md
# Data Analysis
This is a Hermes-native `data-analysis` workflow skill.
## Why This Exists
`data-analysis` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-data-pipelines
When your agent uses it
[omh] Data pipeline work -- an ETL or streaming job, a backfill or replay, duplicate events, a schema change downstream, a lineage question, a data-quality regression: make every rerun idempotent, bound every replay, and gate each load on observed checks. Use when the user says: data-pipelines, data pipeline, data pipelines, etl, elt, etl pipeline, etl job, etl backfill.
What it loads into context
Frontmatter
190 tokensAlways available to the agent
SKILL.md
2,166 tokensWhen the skill is activated
Reference documents
589 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,574 bytesSKILL.mdcore9,574 bytesSKILL.mdcore9,574 bytesreferences/pipeline-method.mddoc2,587 bytes
Read SKILL.md
# Data Pipelines
This is a Hermes-native `data-pipelines` workflow skill.
## Why This Exists
`data-pipelines` exists because pipeline work had no owner: `backend` owns a service's schema migration, `data-analysis` analyzes data it is handed, and `relational-db` owns a database's locks and indexes, while a backfill that duplicated events or a schema change with unknown readers reached memory and event lanes with no idempotency contract or replay bound at all.
## First Steps
- Ask what makes a row unique at the sink before planning any rerun.
- Bound the window and the targets before ordering any replay or backfill step.
## Do Not Use WhenView the complete source on GitHubomh-data-share-review
When your agent uses it
[omh] Before data leaves the team -- a dataset, log, ticket export or transcript excerpt bound for a vendor, a public issue, a model provider or a training corpus: classify every field, minimize first, pseudonymize with the mapping kept local, and call it redacted only after an observed residual scan. Use when the user says: data-share-review, data share review, pii redaction, redact pii, pseudonymize, de-identify, anonymize the dataset, residual pii.
What it loads into context
Frontmatter
219 tokensAlways available to the agent
SKILL.md
2,735 tokensWhen the skill is activated
Reference documents
969 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,014 bytesSKILL.mdcore12,014 bytesreferences/data-share-method.mddoc4,235 bytes
Read SKILL.md
# Data Share Review
This is a Hermes-native `data-share-review` workflow skill.
## Why This Exists
`data-share-review` exists because data leaving the team had no owner: Hermes redacts identifiers in gateway chat and secrets in tool output, `omh-security-safety-review` reviews an agent's own exposure, and `omh-legal-compliance-review` reads the obligations, while nothing minimized a file's fields, kept its pseudonym mapping local, and refused to call it redacted before a scan of what actually leaves.
## First Steps
- Ask where the file goes and what the destination needs it for before touching a field.
- Inventory the fields from the header and the schema before planning any masking.
## Do Not Use WhenView the complete source on GitHubomh-decide
When your agent uses it
[omh] Team or business decision between options: tradeoffs, a recommendation, and a decision note you can act on. Use when the user says: strategy-brief, strategy brief, strategy memo, product strategy, strategic options, decision note, leadership strategy, next strategy.
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
1,604 tokensWhen the skill is activated
Reference documents
1,557 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,567 bytesSKILL.mdcore7,567 bytesreferences/capacity-planning.mddoc3,369 bytesreferences/decision-records.mddoc3,505 bytes
Read SKILL.md
# Strategy Brief
This is a Hermes-native `strategy-brief` workflow skill.
## Why This Exists
`strategy-brief` exists to keep `strategy` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The strategic question is whether an early idea's customer problem and segment are real, and no validated discovery receipt exists yet; use `omh-product-discovery-validation`.
- The question is how to run a hiring process — scorecards, interview loops, candidate comparison — rather than whether to hire at all; use `omh-people-ops`.
- The user wants Jev's typed probabilities for a yes/no, pick-one, or scored question over supplied text rather than tradeoffs and a recommendation; use `omh-jev-ask`.
View the complete source on GitHubomh-decision-prototype
When your agent uses it
[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.
What it loads into context
Frontmatter
194 tokensAlways available to the agent
SKILL.md
719 tokensWhen the skill is activated
Reference documents
5,066 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore3,441 bytesreferences/artifact-shapes.mddoc4,675 bytesreferences/full-contract.mddoc10,205 bytesreferences/procedure.mddoc7,772 bytesreferences/spike-composition.mddoc2,646 bytes
Read SKILL.md
# Decision Prototype
Required: one decision, a bounded experiment, an isolated scratch boundary, and a measurement method. Output: a decision record, prepared handoff, observation ledger, and receipt. When Hermes' bundled `spike` skill is loaded for the same question, build the way it says and keep these records: `references/spike-composition.md`. For a logic, state, or layout question, or prototype code a later plan may reference, load `references/artifact-shapes.md`.
**Do Not Use When:** The user wants an idea's feasibility probed across several questions with throwaway spikes, with no single decision for a plan to consume; load Hermes' bundled `spike` skill instead of this one.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval. **Completion:** Follow the full-contract checklist.
Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Agent/operator: `omh runtime workflow-artifact decision-prototype prepare --input <json-file-or->` prepares bounded metadata only. Shared operator reference: `skill_view(name='omh-routing', file_path='references/workflow-artifacts.md')`.
Contract: `references/full-contract.md`. Procedure: `references/procedure.md`.
View the complete source on GitHubomh-decision-recall
When your agent uses it
[omh] Previously rejected options to revisit: recall scoped reviewed rejected decisions without elevating them to approved memory. Use when the user says: decision-recall, rejected decision recall, rejected decisions, why was this rejected, previously rejected alternative, 거절된 결정, 기각된 대안.
What it loads into context
Frontmatter
132 tokensAlways available to the agent
SKILL.md
1,267 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,135 bytesSKILL.mdcore6,135 bytesSKILL.mdcore6,135 bytes
Read SKILL.md
# Decision Recall
This is a Hermes-native `decision-recall` workflow skill.
## Why This Exists
`decision-recall` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-deliverable-package
When your agent uses it
[omh] Attachment and deliverable status tracking: track PPT, PDF, XLSX, DOCX, HWP, Markdown, and attachments through prepared, generated, QA, approved, attached, archived, and published states. Use when the user says: deliverable-package, deliverable mode, file attachment, attach file, attachment status, file delivery, file deliverable status, generated file.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
1,918 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,984 bytesSKILL.mdcore8,984 bytesSKILL.mdcore8,984 bytesSKILL.mdcore8,984 bytes
Read SKILL.md
# Deliverable Package
This is a Hermes-native `deliverable-package` workflow skill.
## Why This Exists
`deliverable-package` exists because a requested file moves through prepared, generated, QA-checked, approved, and attached states that no single tool reports together: it tracks each file through them and reports a state only from that state's own evidence, never from an earlier one's.
## Do Not Use When
- Planning a deck, PDF, workbook, or document from source inputs before any file exists (its outline, target formats, and QA ladder); use `omh-materials-package`.
- A text-only report, executive brief, or slide outline with no file to produce; use `omh-report-package`.
## ExamplesView the complete source on GitHubomh-deploy-and-monitor
When your agent uses it
[omh] Release rollout needing health signals: release checklist, deploy decision, health signals, rollback gate, and post-deploy status. Use when the user says: deploy-and-monitor, deploy and monitor, deploy monitor, deployment monitoring, release monitor, post deploy, post-deploy, rollback.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,883 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,874 bytesSKILL.mdcore8,874 bytesSKILL.mdcore8,874 bytes
Read SKILL.md
# Deploy And Monitor
This is a Hermes-native `deploy-and-monitor` workflow skill.
## Why This Exists
`deploy-and-monitor` exists to keep `monitoring` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- An incident has already been declared and the work is commanding it -- severity, commander, running timeline, recovery verification -- rather than watching a release; use `omh-live-incident-response`.
- The ask is deciding a release before it ships -- what goes in, its version and tag, the canary stages, or which command rolls it back; use `omh-release-cut`, which writes the rollback trigger down before it is needed.
- The change is to declared infrastructure itself -- a Terraform plan, a Kubernetes manifest, a Helm chart -- and needs its drift, blast radius, and cost delta read before it is applied; use `omh-iac-change`.
View the complete source on GitHubomh-design-orchestration
When your agent uses it
[omh] Entire product design problem to delegate: prepare a bounded design direction, existing-lane composition, and executor-neutral handoff. Use when the user says: design-orchestration, design orchestration, design ownership, handle this product design, take on the design, デザインを任せる, デザイン全体を任せ, プロダクトデザインを任せ.
What it loads into context
Frontmatter
185 tokensAlways available to the agent
SKILL.md
1,878 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,064 bytesSKILL.mdcore9,064 bytes
Read SKILL.md
# Design Orchestration
This is a Hermes-native `design-orchestration` workflow skill.
## Why This Exists
`design-orchestration` lets Hermes users say that they want design handled without making them manually compose four specialist lanes or confusing preparation with completed visual work.
## Do Not Use When
- The request is directly about premium multi-format quality or publishing; use `omh-design-quality-gate`.
- The request is directly about frontend implementation, layout, responsive behavior, or a design system; use `omh-frontend`.
- The request is directly about WCAG, keyboard, screen-reader, or semantic accessibility; use `omh-accessibility-audit`.
- The request is directly about screenshots, visual regression, pixel diff, rendered layout, or a verdict; use `omh-visual-qa`.View the complete source on GitHubomh-design-quality-gate
When your agent uses it
[omh] Deliverable demands premium polish: enforce superior content, design, layout, publishing, and visual QA gates. Use when the user says: design-quality-gate, design quality gate, ui ux pro max, design pro max, frontend pro max, visual qa pro, premium design, high quality design.
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
2,148 tokensWhen the skill is activated
Reference documents
1,459 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,982 bytesSKILL.mdcore9,982 bytesSKILL.mdcore9,982 bytesSKILL.mdcore9,982 bytesreferences/design-critique-rubric.mddoc6,276 bytes
Read SKILL.md
# Design Quality Gate
This is a Hermes-native `design-quality-gate` workflow skill.
## Why This Exists
`design-quality-gate` makes high-stakes visual deliverables premium and trustworthy by treating taste, content, layout, accessibility, and render QA as first-class evidence.
## Do Not Use When
- Basic image prompt card only; use `omh-image-cards`.
- The artifact is a throwaway probe whose quality is irrelevant to the decision it answers; use `omh-decision-prototype`.
- Ordinary file packaging/export plan only; use `omh-materials-package` or `omh-deliverable-package`.
- Pure backend, CLI, data, or text-only research with no visual surface.View the complete source on GitHubomh-docs
When your agent uses it
[omh] Explaining OMH itself: current-source-first documentation for OMH itself: product identity, public capability catalog, model routing, local state, and long-term memory. Use when the user says: product-docs, OMH documentation, oh-my-hermes documentation, what is OMH, what is oh-my-hermes, how does OMH work, OMH capability catalog, OMH skill catalog.
What it loads into context
Frontmatter
173 tokensAlways available to the agent
SKILL.md
1,340 tokensWhen the skill is activated
Reference documents
2,518 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Default Behavior
- Source Route
- Public Product vs Local Install
- Safety and Mutation Boundary
- Answer Contract
- Workflow Lane
- Completion Checklist
- Recovery Notes
Files
SKILL.mdcore6,377 bytesSKILL.mdcore6,377 bytesSKILL.mdcore6,377 bytesSKILL.mdcore6,377 bytesreferences/capability-map.mddoc2,728 bytesreferences/long-term-memory.mddoc2,337 bytesreferences/model-routing-and-local-state.mddoc3,763 bytesreferences/product-and-sources.mddoc2,838 bytes
Read SKILL.md
# OMH Docs
Use this skill to answer questions about OMH itself from current sources. It
defaults to passive inspection; it is not a generic documentation writer,
workflow picker, or settings workflow.
## Default Behavior
1. Classify the question as a public-product fact, a current-local-install
fact, or both. Keep those claim sets separate in the answer.
2. Retrieve only the sources needed for the question. Current public facts must
come from official `rlaope/oh-my-hermes` sources; current local facts must
come from passive CLI output, or narrowly scoped non-secret metadata. If a
diagnostic command records state, disclose that side effect before running it.View the complete source on GitHubomh-doctor
When your agent uses it
[omh] OMH install misbehaving: diagnosing oh-my-hermes installation health. Use when the user says: doctor, diagnose omh, installation health.
What it loads into context
Frontmatter
98 tokensAlways available to the agent
SKILL.md
1,131 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore5,503 bytesSKILL.mdcore5,503 bytes
Read SKILL.md
# Doctor
This is a Hermes-native `doctor` workflow skill.
## Why This Exists
`doctor` exists to turn confusing install/setup states into grouped, local health evidence and the next repair action without treating a check as a fix.
## Do Not Use When
- The user is asking for a general product explanation rather than local health diagnostics.
- The requested change is a repository bug fix, not an installed-environment check.
- The wrapper wants to claim Hermes reload, skill execution, or plugin behavior that was not observed.
View the complete source on GitHubomh-executor-runtime-readiness
When your agent uses it
[omh] Unsure whether Codex or Claude Code is ready: executor runtime readiness - compare Codex, Claude Code, Hermes coding, and oh-my runtimes by tools and handoff mode; use external-connector-readiness for a named plugin or API, and toolbelt-readiness for the whole capability inventory. Use when the user says: executor-runtime-readiness, executor readiness, runtime readiness, codex readiness, claude code readiness, hermes coding readiness, executor tools, missing tools.
What it loads into context
Frontmatter
178 tokensAlways available to the agent
SKILL.md
2,291 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,561 bytesSKILL.mdcore10,561 bytes
Read SKILL.md
# Executor Runtime Readiness
This is a Hermes-native `executor-runtime-readiness` workflow skill.
## Why This Exists
`executor-runtime-readiness` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-external-connector-readiness
When your agent uses it
[omh] Evaluating a plugin, connector, or API for adoption: external connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
What it loads into context
Frontmatter
206 tokensAlways available to the agent
SKILL.md
3,650 tokensWhen the skill is activated
Reference documents
720 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore17,435 bytesSKILL.mdcore17,435 bytesreferences/memory-provider-trial.mddoc3,408 bytes
Read SKILL.md
# External Connector Readiness
This is a Hermes-native `external-connector-readiness` workflow skill.
## Why This Exists
`external-connector-readiness` exists because adopting a plugin, connector, API, or memory provider changes what the agent can reach, spend, and remember, and a host's install-time scan or a vendor's docs answer only part of that: it scores capability, auth, cost, freshness, safety, and fallback for each candidate, and reports a trial only from what was observed.
## Do Not Use When
- Choosing which coding owner runs a task; use `omh-executor-runtime-readiness`.
- Finding which tool, credential, or install is missing for work already chosen; use `omh-toolbelt-readiness`.
- A read-only live lookup or an external write through a connector already adopted; use `omh-live-info` or `omh-apps`.
View the complete source on GitHubomh-failure-signal-audit
When your agent uses it
[omh] Hidden or swallowed errors suspected: find swallowed errors, unsafe fallbacks, hidden UI/runtime failures, and missing propagation before they become false green status. Use when the user says: failure-signal-audit, failure signal audit, silent failure, silent failures, silent failure hunter, swallowed error, swallowed errors, empty catch.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,853 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,819 bytesSKILL.mdcore8,819 bytesSKILL.mdcore8,819 bytesSKILL.mdcore8,819 bytesSKILL.mdcore8,819 bytes
Read SKILL.md
# Failure Signal Audit
This is a Hermes-native `failure-signal-audit` workflow skill.
## Why This Exists
`failure-signal-audit` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-feedback-triage
When your agent uses it
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow. Use when the user says: feedback-triage, customer-feedback-triage, feedback triage, customer feedback, feedback cluster, bug or feature, feature request triage, payment failure feedback.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,474 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytesSKILL.mdcore7,007 bytes
Read SKILL.md
# Feedback Triage
This is a Hermes-native `feedback-triage` workflow skill.
## Why This Exists
`feedback-triage` exists to keep customer and community signals from jumping straight into roadmap or coding; it clusters evidence, ranks signals, and chooses the next workflow.
## Do Not Use When
- The request already contains an accepted product decision and asks for implementation.
- There are no feedback items, source boundary, or product area to classify.
- The user wants current market research rather than triage of supplied signals.
- The triage result asks for a retention or activation intervention rather than another cluster; use `omh-lifecycle-growth`.View the complete source on GitHubomh-files
When your agent uses it
[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.
What it loads into context
Frontmatter
170 tokensAlways available to the agent
SKILL.md
2,071 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,855 bytesSKILL.mdcore9,855 bytes
Read SKILL.md
# Workspace File Operator
This is a Hermes-native `workspace-file-operator` workflow skill.
## Why This Exists
`workspace-file-operator` exists because a delete, overwrite, or bulk move often has no undo point: it scopes the path, confirms each destructive step, records beforehand whether a checkpoint covers the target (Hermes takes none unless checkpoints are on), and reports only what file evidence shows.
## Do Not Use When
- An ordinary list, search, read, or one-file edit inside a known folder; use the native file tools directly.
- The request converts files or produces a deck, PDF, or attachment; use `omh-materials-package` or `omh-deliverable-package`.
## ExamplesView the complete source on GitHubomh-finance-analysis
When your agent uses it
[omh] Company budget overrun, cash risk, or close issue: turn finance and accounting inputs into a decision-ready variance, cash, and close-risk brief. Use when the user says: finance analysis, budget variance, budget vs actual, month-end close, 재무 분석, 예산 대비 실적, 월마감.
What it loads into context
Frontmatter
174 tokensAlways available to the agent
SKILL.md
1,591 tokensWhen the skill is activated
Reference documents
1,267 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,537 bytesSKILL.mdcore7,537 bytesSKILL.mdcore7,537 bytesSKILL.mdcore7,537 bytesSKILL.mdcore7,537 bytesreferences/procedure.mddoc5,962 bytes
Read SKILL.md
# Finance Analysis
This is a Hermes-native `finance-analysis` workflow skill.
## Why This Exists
`finance-analysis` prepares a source-bounded decision brief without claiming an authoritative financial action.
## Do Not Use When
- The request is for a current quote, exchange rate, crypto price, or other live market lookup; use `omh-live-info`.
- The user wants generic exploration of a supplied CSV or table without accounting periods, controls, or finance decision framing; use `omh-data-analysis`.
- The user asks to post journal entries, reconcile accounts, approve payments, submit tax filings, or configure an accounting system; use `omh-apps` for an explicit observed action path.
- The user wants pipeline coverage, deal health, or a seller forecast scenario rather than authoritative revenue or close reporting; use `omh-sales-pipeline-review`.View the complete source on GitHubomh-frontend
When your agent uses it
[omh] Building or polishing a web or terminal UI: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, in the frontend, on the frontend, to the frontend, web ui.
What it loads into context
Frontmatter
185 tokensAlways available to the agent
SKILL.md
4,634 tokensWhen the skill is activated
Reference documents
17,825 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore21,137 bytesSKILL.mdcore21,137 bytesSKILL.mdcore21,137 bytesSKILL.mdcore21,137 bytesSKILL.mdcore21,137 bytesSKILL.mdcore21,137 bytesreferences/chart-styling.mddoc5,026 bytesreferences/component-registry-adoption.mddoc8,923 bytesreferences/design-system-contract.mddoc12,739 bytesreferences/forms-and-input.mddoc8,728 bytesreferences/reference-token-extraction.mddoc2,835 bytesreferences/rendered-scene-craft.mddoc3,980 bytesreferences/screenshot-loop.mddoc5,533 bytesreferences/scroll-motion-libraries.mddoc7,119 bytesreferences/taste-foundations.mddoc11,519 bytesreferences/tui-craft.mddoc6,678 bytesreferences/web-vitals-budgets.mddoc3,688 bytes
Read SKILL.md
# Frontend
This is a Hermes-native `frontend` workflow skill.
## Why This Exists
`frontend` gives OMH a first-class web UI creation and polishing workflow so Hermes can prepare high-quality layout, design-system, accessibility, performance, and visual-QA handoffs without becoming the hidden coding or browser runtime.
## Do Not Use When
- The user needs a broad premium-quality gate across web, deck, PDF, poster, or publishing outputs; use `omh-design-quality-gate`.
- The user wants a disposable wireframe or mocked interaction to settle one interaction question before planning; use `omh-decision-prototype`.
- The user only needs a file, deck, PDF, spreadsheet, HWP, or attachment package; use `omh-materials-package` or `omh-deliverable-package`.
- The user only needs an image card or infographic prompt; use `omh-image-cards`.View the complete source on GitHubomh-frontend-refactor
When your agent uses it
[omh] Oversized or tangled UI component: behavior-preserving refactor of UI code - preview the full change plan first, apply as a second explicit step, and work impact-ordered from state architecture down to naming polish. Use when the user says: frontend-refactor, front-refactor, frontend refactor, refactor this component, refactor the component, refactor my component, component refactor, react refactor.
What it loads into context
Frontmatter
193 tokensAlways available to the agent
SKILL.md
2,729 tokensWhen the skill is activated
Reference documents
1,875 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,783 bytesSKILL.mdcore12,783 bytesreferences/refactor-passes.mddoc4,636 bytesreferences/state-discipline.mddoc3,746 bytes
Read SKILL.md
# Frontend Refactor
This is a Hermes-native `frontend-refactor` workflow skill.
## Why This Exists
`frontend-refactor` exists so UI restructuring runs as a previewed, behavior-locked, impact-ordered process instead of ad-hoc rewrites: the plan comes before any edit, state fixes come before polish, and every change carries its safety reason.
## Do Not Use When
- The target is not UI code, or the smell is generic slop, duplication, or dead code outside a component tree; use `omh-ai-slop-cleaner`.
- The user wants new UI built or redesigned rather than restructured; use `omh-frontend`.
- The user wants findings and a verdict without changing the code; use `omh-code-review`.
- The restructuring crosses module boundaries or changes architecture beyond the component tree; use `omh-refactor-plan` for the phased execution shape, or `ulw-plan` first when the direction itself is still contested.View the complete source on GitHubomh-gateway-intent-card
When your agent uses it
[omh] Bot replies via Discord, Slack, or Telegram: normalize Discord, Slack, Telegram, and other gateway sessions into origin, thread, delivery, silent, attachment, and status-update policy. Use when the user says: gateway-intent-card, gateway intent, discord thread, slack thread, telegram delivery, discord delivery policy, slack delivery policy, telegram delivery policy.
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
1,375 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,503 bytesSKILL.mdcore6,503 bytes
Read SKILL.md
# Gateway Intent Card
This is a Hermes-native `gateway-intent-card` workflow skill.
## Why This Exists
`gateway-intent-card` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-geospatial-analysis
When your agent uses it
[omh] Spatial layers to intersect: execute CRS-safe polygon overlay with measured areas, validated geometry and reproducible GeoJSON outputs. Use when the user says: geospatial-analysis, geospatial overlay, spatial intersection, intersect geojson layers, compute overlap area.
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
1,184 tokensWhen the skill is activated
Reference documents
3,778 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/scripts/analyze.py
Files
SKILL.mdcore5,875 bytesSKILL.mdcore5,875 bytesSKILL.mdcore5,875 bytesSKILL.mdcore5,875 bytesreferences/execution-and-qa.mddoc4,427 bytesreferences/full-contract.mddoc3,113 bytesreferences/procedure.mddoc3,655 bytestoolkit/LICENSE.upstreamasset1,305 bytestoolkit/README.mddoc6,412 bytestoolkit/examples/input.jsonasset501 bytestoolkit/examples/overlay.jsonasset351 bytestoolkit/scripts/analyze.pyruns17,267 bytestoolkit/upstream-manifest.jsonasset3,163 bytes
Read SKILL.md
# Geospatial Analysis
Required: input and overlay polygon layers, explicit source and metric target CRS, new output directory and execution budget. Output: result GeoJSON, measured summary JSON, replay and provenance manifest.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
Polygon computations can return plausible but wrong numbers when CRS, coordinate units or geometry are invalid. This skill couples fail-closed checks to a runnable optional overlay producer and inspectable replay artifacts.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md` before executing `toolkit/scripts/analyze.py`; installation and skill discovery never run it.
- Confirm the two layers, explicit EPSG declarations, study extent, projected metre CRS, output directory and finite host timeout; never guess a missing CRS.View the complete source on GitHubomh-git-workflow
When your agent uses it
[omh] Git branch in trouble -- a merge conflict, a commit that broke something, history to repair: plan the resolution, the bisect, or the rewrite, name what is already pushed first, and force-push only with `--force-with-lease`. Use when the user says: git-workflow, git workflow, merge conflict, merge conflicts, rebase conflict, resolve the conflict, resolve this conflict, conflict markers.
What it loads into context
Frontmatter
191 tokensAlways available to the agent
SKILL.md
2,061 tokensWhen the skill is activated
Reference documents
1,074 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,090 bytesreferences/git-repair-method.mddoc4,304 bytes
Read SKILL.md
# Git Workflow
This is a Hermes-native `git-workflow` workflow skill.
## Why This Exists
`git-workflow` exists because conflict resolution, bisect, and history repair had no owner: "resolve this merge conflict" reached a file operator and "clean up this branch's history" a live-information lane, while this repository's own incidents -- a stack that replayed its base commits, a commit landing on another session's branch -- each had a known correct procedure.
## First Steps
- Name what is already pushed: each branch involved with its local head, its remote head, and whether others may have fetched it.
- Before any step that rewrites history, name its recovery point.
## Do Not Use WhenView the complete source on GitHubomh-github-event-ops
When your agent uses it
[omh] Incoming GitHub PR, issue, or CI event: GitHub event operations: route PR, issue, CI, and review webhook events into triage, review, or fix handoff cards. Use when the user says: github-event-ops, github event ops, github ops, github triage, github pr, github review, github action, github actions.
What it loads into context
Frontmatter
189 tokensAlways available to the agent
SKILL.md
1,939 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,628 bytesSKILL.mdcore8,628 bytes
Read SKILL.md
# Github Event Ops
This is a Hermes-native `github-event-ops` workflow skill.
## Why This Exists
`github-event-ops` exists because a GitHub event arrives as a payload, not a decision: it sorts the event into review, triage, or a fix hand-off, re-reads remote state rather than trusting the payload, and never reports a label, rerun, or review the run did not observe.
## Do Not Use When
- One issue to file from a bug report or an idea, with no incoming event to route; use `omh-github-issue-intake`.
- A failing build log to diagnose, with no event routing left to decide; use `omh-build-failure-triage`.
- The event is a security advisory, a CVE in a dependency, or a leaked credential; use `omh-security-event-response`, which orders containment and closes only on an observed rotation or fix.
- The PR is a dependabot or renovate version bump with no advisory; use `omh-refactor-plan`, which decides whether it is safe to merge from the breaking changes against this repository's call sites.View the complete source on GitHubomh-github-issue-intake
When your agent uses it
[omh] Chat report that should become a GitHub issue: turn a public chat report into a confirmed, verified issue package. Use when the user says: github-issue-intake, github issue intake, issue intake, file this as an issue, file a github issue, open a github issue, create a github issue, submit a github issue.
What it loads into context
Frontmatter
157 tokensAlways available to the agent
SKILL.md
2,152 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,283 bytesSKILL.mdcore10,283 bytesSKILL.mdcore10,283 bytesSKILL.mdcore10,283 bytes
Read SKILL.md
# Github Issue Intake
This is a Hermes-native `github-issue-intake` workflow skill.
## Why This Exists
`github-issue-intake` exists so a public support-chat report can become a verified GitHub issue through one bounded, confirmation-gated lane instead of ad hoc chat narration or an unscoped bot write.
## Do Not Use When
- The report only wants classification or signal clustering; use feedback-triage instead.
- The event concerns an already-existing issue, PR, review, or CI run; use github-event-ops instead.
- The user wants implementation; coding stays a separate follow-up lane with its own maintainer authority.
- The report describes a security vulnerability; redirect to the private SECURITY.md path.View the complete source on GitHubomh-harness-session-inventory
When your agent uses it
[omh] Lost track of agent sessions and worktrees: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory.
What it loads into context
Frontmatter
153 tokensAlways available to the agent
SKILL.md
1,727 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,120 bytesSKILL.mdcore8,120 bytesSKILL.mdcore8,120 bytesSKILL.mdcore8,120 bytes
Read SKILL.md
# Harness Session Inventory
This is a Hermes-native `harness-session-inventory` workflow skill.
## Why This Exists
`harness-session-inventory` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-iac-change
When your agent uses it
[omh] Infrastructure-as-code change -- Terraform, OpenTofu, Pulumi, a Kubernetes manifest, a Helm chart: read the drift, the blast radius and the cost delta from the saved plan, then stage the apply behind a health gate with a rollback per stage. Use when the user says: iac-change, iac change, infrastructure as code, infrastructure-as-code, terraform plan, terraform apply, terraform state, terraform drift.
What it loads into context
Frontmatter
190 tokensAlways available to the agent
SKILL.md
2,189 tokensWhen the skill is activated
Reference documents
694 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,885 bytesSKILL.mdcore9,885 bytesreferences/iac-change-method.mddoc2,991 bytes
Read SKILL.md
# Iac Change
This is a Hermes-native `iac-change` workflow skill.
## Why This Exists
`iac-change` exists because infrastructure changes had no owner: `deploy-and-monitor` watches an application release, `release-cut` decides one, and `inference-serving` deploys a model server, while a Terraform plan with drift, a Helm chart change, or a manifest edit reached a generic planner with no blast radius, cost delta, or staged apply at all.
## First Steps
- Ask for the saved plan or the diff output before assessing anything.
- Separate existing drift from the proposed change before ordering stages.
## Do Not Use WhenView the complete source on GitHubomh-idea-to-deploy
When your agent uses it
[omh] App idea headed for launch: shape an app idea into decisions, delivery handoff, verification, release, and monitoring status. Use when the user says: idea-to-deploy, idea to deploy, from idea to deploy, plan to deploy, idea to launch, ship this idea, ship this feature, launch this feature.
What it loads into context
Frontmatter
150 tokensAlways available to the agent
SKILL.md
1,715 tokensWhen the skill is activated
Reference documents
1,771 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,052 bytesSKILL.mdcore8,052 bytesreferences/project-bootstrap.mddoc8,329 bytes
Read SKILL.md
# Idea To Deploy
This is a Hermes-native `idea-to-deploy` workflow skill.
## Why This Exists
`idea-to-deploy` exists to keep `delivery` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The task is already a concrete repo change whose stopping point is one PR-ready cycle, not product or release operations; use `ulw-work`.
- The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or a direct answer/diagnosis; handle it directly instead of opening a product delivery loop.
## ExamplesView the complete source on GitHubomh-image-cards
When your agent uses it
[omh] Infographic card for meeting notes, a report, or PR: image prompt cards - turn meetings, reports, PRs, issues, research, and releases into domain-aware image prompt cards. Use when the user says: img-summary, img summary, visual prompt card, image card, image generation, image edit, edit this image, remove the background.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
3,050 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytesSKILL.mdcore14,268 bytes
Read SKILL.md
# Img Summary
This is a Hermes-native `img-summary` workflow skill.
## Why This Exists
`img-summary` exists so Hermes can turn common communication work into provider-neutral image-card prompts while adapting format, domain mood, background, texture, lighting, camera, and poster grammar, and keeping generation, QA, and delivery as observed-only evidence.
## Do Not Use When
- The user needs a deck, PDF, spreadsheet, HWP, Markdown package, or binary file export plan; use `omh-materials-package`.
- The user wants a text-only report, leadership brief, or PPT-ready outline; use `omh-report-package`.
- The user asks OMH to directly generate, inspect, upload, or post an image without a wrapper-supplied observed evidence path.
View the complete source on GitHubomh-inference-serving
When your agent uses it
[omh] Self-hosted LLM serving on GPUs: choose the serving engine and quantization from decision tables, prepare deployment as an idempotent runbook with observed-only verification, and measure the endpoint with the standard TTFT/TPOT/goodput protocol. Use when the user says: inference-serving, inference serving, serve this model, serve the model, model serving, serving endpoint, vllm, llama.cpp.
What it loads into context
Frontmatter
186 tokensAlways available to the agent
SKILL.md
2,034 tokensWhen the skill is activated
Reference documents
1,424 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,101 bytesreferences/serving-bench.mddoc2,279 bytesreferences/serving-runbooks.mddoc3,547 bytes
Read SKILL.md
# Inference Serving
This is a Hermes-native `inference-serving` workflow skill.
## Why This Exists
`inference-serving` exists so serving an LLM runs as one decided, gated, measured process instead of scattered flag folklore: the engine choice is a table, the deployment is an idempotent runbook whose only completion evidence is the observed verification, and the benchmark speaks the standard metric vocabulary.
## Do Not Use When
- A new model generation needs recognition, calibration, routing, and pricing onboarding; use `omh-model-optimization`.
- The user wants their own machine's model routing or providers configured; use `omh-model-setup`.
- The question is whether a coding runtime/executor can run at all; use `omh-executor-runtime-readiness`.
- The goal is application or system performance rather than the serving endpoint itself; use `ulw-perf`.View the complete source on GitHubomh-instinct-ledger
When your agent uses it
[omh] Recurring lessons worth promoting: turn repeated project or cross-project lessons into atomic, confidence-scored instinct candidates with scoped promotion and export boundaries. Use when the user says: instinct-ledger, instinct ledger, project instincts, project-scoped instincts, project scoped instincts, global instincts, instinct review, instinct candidate.
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
1,760 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,409 bytesSKILL.mdcore8,409 bytesSKILL.mdcore8,409 bytes
Read SKILL.md
# Instinct Ledger
This is a Hermes-native `instinct-ledger` workflow skill.
## Why This Exists
`instinct-ledger` exists because a lesson seen once is an anecdote and one seen across runs or projects is a candidate rule: it records each as one atomic instinct with its trigger, action, scope, confidence, and evidence, and promotes one only through a reviewed store route, never by writing a host's memory or skills on its own.
## Do Not Use When
- A single missed route or one run's trace; use `omh-workflow-learning` first.
- Writing reviewed lessons into AGENTS guidance, prompts, or skills; use `omh-rules-distill`.
- A run that is stuck right now; use `omh-agent-debug` before drawing a lesson from it.
View the complete source on GitHubomh-internal-audit
When your agent uses it
[omh] Testing an internal control -- SOX, ICFR or ITGC: define the population and the sample, name the evidence that proves each item, re-perform the control, and grade any deficiency from stated likelihood, magnitude and compensating-control criteria, never by assertion. Use when the user says: internal-audit, internal audit, internal control, internal controls, internal control audit, control testing, test of controls, tests of controls.
What it loads into context
Frontmatter
195 tokensAlways available to the agent
SKILL.md
2,087 tokensWhen the skill is activated
Reference documents
549 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,989 bytesSKILL.mdcore9,989 bytesSKILL.mdcore9,989 bytesreferences/control-audit-method.mddoc2,540 bytes
Read SKILL.md
# Internal Audit
This is a Hermes-native `internal-audit` workflow skill.
## Why This Exists
`internal-audit` exists because control-testing methodology had no owner: `finance-analysis` reports figures and names control exceptions, `tech-debt-audit` audits code, and `production-audit` audits a release, while population, sampling, re-performance, and deficiency severity had nothing that derived a grade from criteria.
## First Steps
- Ask what the control is meant to prevent or detect, and over which population and period it operates.
- Ask for the sampling guidance and the materiality threshold before sizing any sample or grading anything.
## Do Not Use WhenView the complete source on GitHubomh-jev-action-check
When your agent uses it
[omh] Risky command screened by Jev: Jev action check before a risky command: secrets, outbound sends, blast radius; can only add a hold. Use when the user says: jev-action-check, jev action check, ask jev if this command is safe, jev risk check.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
666 tokensWhen the skill is activated
Reference documents
1,280 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,871 bytesreferences/full-contract.mddoc3,723 bytesreferences/preset.mddoc1,422 bytes
Read SKILL.md
# Jev Action Check
Required: the command, working directory, and stated task. Output: hold, refuse_recommended, or no_extra_hold with its rule.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`. Preset: `references/preset.md`.
## Procedure
1. Name what leaves the machine: the command, the working directory, and the stated task.
2. Call `omh_jev_ask` with `preset: action_check/v1` and `state` {command, cwd, stated_task} before anything runs.
3. Report the outcome and rule; on `hold` or `refuse_recommended` ask the user before running, and on `no_extra_hold` the host's normal approval still applies.
View the complete source on GitHubomh-jev-ask
When your agent uses it
[omh] User named Jev for yes/no or pick-one probabilities: Jev ask: typed yes/no, pick-one, or scored questions to Jev with your own key; returns probabilities, never prose. Use when the user says: jev-ask, ask jev, jev question, jev score.
What it loads into context
Frontmatter
169 tokensAlways available to the agent
SKILL.md
700 tokensWhen the skill is activated
Reference documents
965 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,937 bytesreferences/full-contract.mddoc4,199 bytes
Read SKILL.md
# Jev Ask
Required: text to judge and independent typed questions. Output: Jev's probabilities, served model, and cost, or a non-answer status.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`.
## Procedure
1. Check the rail: the user asked for Jev in this turn, and say in one line what `state` will carry.
2. Write independent, self-contained questions over one `state`: Noul with `criteria.true`/`criteria.false`, Choice with an `unknown` option, Score with ordered levels.
3. Call `omh_jev_ask` with `questions` (default model `jev-latest`; pin `jev-1.13.0` when a threshold was tuned).
4. Report each number verbatim with the served model, attempts, and `cost_usd` plus `cost_source`; 0.4 to 0.6 is uncertain.View the complete source on GitHubomh-jev-done-check
When your agent uses it
[omh] Completion claim tested by Jev: Jev done check: does the gathered evidence support the completion claim? It can only object. Use when the user says: jev-done-check, jev done check, ask jev if this is done, jev evidence check.
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
650 tokensWhen the skill is activated
Reference documents
1,124 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,801 bytesreferences/full-contract.mddoc3,522 bytesreferences/preset.mddoc1,143 bytes
Read SKILL.md
# Jev Done Check
Required: each completion claim, observed evidence, and the goal. Output: objections per claim, or no_objection.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`. Preset: `references/preset.md`.
## Procedure
1. Name what leaves the machine: each claim, an excerpt of observed output, and the goal.
2. Call `omh_jev_ask` with `preset: done_check/v1` and `state` {claim, evidence_excerpt, goal}, one ask per claim, at most 6.
3. Report each objection with its claim and rule; fix or withdraw an objected claim before reporting completion.
View the complete source on GitHubomh-jev-failure-triage
When your agent uses it
[omh] Failing run handed to Jev for a next move: Jev failure triage: retry, fix a dependency, ask for access, or change approach on a failing run. Use when the user says: jev-failure-triage, jev failure triage, ask jev if this failure is transient.
What it loads into context
Frontmatter
182 tokensAlways available to the agent
SKILL.md
705 tokensWhen the skill is activated
Reference documents
1,211 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,971 bytesreferences/full-contract.mddoc3,674 bytesreferences/preset.mddoc1,210 bytes
Read SKILL.md
# Jev Failure Triage
Required: the failing command, an error excerpt, and the retry count. Output: `failure_triage/v1` next move with its rule.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`. Preset: `references/preset.md`.
## Procedure
1. Name what leaves the machine: the command and an error excerpt (plus earlier attempt excerpts when repeating).
2. Call `omh_jev_ask` with `preset: failure_triage/v1`, `state` {error_excerpt, last_command, earlier_attempts}, and `attempts_so_far`.
3. Report `policy_result.outcome` and its rule beside the raw answers.
4. Hand the fix to `build-failure-triage` or `agent-debug`; a rerun still needs the host's approval.View the complete source on GitHubomh-jev-review-gate
When your agent uses it
[omh] Wants Jev risk flags on a diff under review: Jev review flags for a diff: auth, tests, migration risk, severity; flags only, never approves a merge. Use when the user says: jev-review-gate, jev review gate, ask jev to review this diff.
What it loads into context
Frontmatter
172 tokensAlways available to the agent
SKILL.md
667 tokensWhen the skill is activated
Reference documents
1,149 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,823 bytesSKILL.mdcore2,823 bytesreferences/full-contract.mddoc3,531 bytesreferences/preset.mddoc1,140 bytes
Read SKILL.md
# Jev Review Gate
Required: one file's diff per ask. Output: `review_flags/v1` advisory flags and severity; never an approval.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`. Preset: `references/preset.md`.
## Procedure
1. State the files and the cost before the first ask; source diffs leave the machine.
2. Call `omh_jev_ask` with `preset: review_flags/v1` and `state` {file, diff}, one file per ask, at most 8.
3. Report each file's flags, the union of flags, and the highest severity as advisory (Jev) lines in the review.
View the complete source on GitHubomh-jev-route
When your agent uses it
[omh] Undecided OMH route handed to Jev: Jev route pick: answer an OMH route question about which workflow fits, recorded without re-routing. Use when the user says: jev-route, ask jev which workflow, jev pick the workflow.
What it loads into context
Frontmatter
148 tokensAlways available to the agent
SKILL.md
648 tokensWhen the skill is activated
Reference documents
885 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Procedure
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,820 bytesreferences/full-contract.mddoc3,808 bytes
Read SKILL.md
# Jev Route
Required: an undecidable route's `route_question` block and the user's message. Output: Jev's pick as a clarification and a recorded answer.
Read `skill_view(name='omh-routing', file_path='references/jev-rail.md')` before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Contract: `references/full-contract.md`.
## Procedure
1. Confirm the route carries `route_question` and the ladder lists `omh_jev_ask`; tell the user their message leaves the machine.
2. Call `omh_jev_ask` with the block unchanged as `route_question` and the message as `state`.
3. Offer Jev's top pick to the user as a question; the block's thresholds only shape the wording.
4. Record it with `omh_route_answer`, `answered_by: omh_jev_ask`, and the returned `ask_id`.View the complete source on GitHubomh-jit-learn
When your agent uses it
[omh] Blocked on a project by a knowledge gap: just-in-time learning workflow: select and confirm an immediate learning target, research credible sources, and prepare an application-first brief without popularity ranking. Use when the user says: jit-learn, learn next, learn now, blocker-specific learning target, highest-leverage learning target, immediate learning payoff, immediately applicable learning brief, source-backed learning brief.
What it loads into context
Frontmatter
185 tokensAlways available to the agent
SKILL.md
2,715 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Just-in-Time Learning Protocol
- Learning Brief Contract
- Runtime Evidence
Files
SKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytesSKILL.mdcore13,424 bytes
Read SKILL.md
# Jit Learn
This is a Hermes-native `jit-learn` workflow skill.
## Why This Exists
`jit-learn` exists to choose what is worth learning for the user's present problem and convert credible sources into an immediate application path, instead of returning a generic self-help shelf or a popularity list.
## Do Not Use When
- The user asks OMH to learn from workflow outcomes, missed routes, or evaluation traces; use `omh-workflow-learning`.
- The learning goal is already chosen and the user wants a multi-week syllabus, instructional sequence, or assessment plan; use `omh-curriculum-design`.
- The user supplied a paper, PDF, arXiv entry, or excerpt and wants it explained; use `omh-paper-learning`.
- The requested output is a typed source candidate inventory or acquisition status rather than a fitted learning brief; use `omh-source-finder`.View the complete source on GitHubomh-legal-compliance-review
When your agent uses it
[omh] Business contract, NDA, or policy with legal risk: surface contract and compliance risks, questions, and escalation points before a legal decision or action. Use when the user says: contract review, contract liability clause, regulatory analysis, compliance review, contract redline, redline the contract, negotiation preparation, negotiation strategy.
What it loads into context
Frontmatter
167 tokensAlways available to the agent
SKILL.md
1,782 tokensWhen the skill is activated
Reference documents
2,537 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,567 bytesSKILL.mdcore8,567 bytesSKILL.mdcore8,567 bytesreferences/negotiation-preparation.mddoc3,454 bytesreferences/procedure.mddoc8,258 bytes
Read SKILL.md
# Legal Compliance Review
This is a Hermes-native `legal-compliance-review` workflow skill.
## Why This Exists
`legal-compliance-review` prepares scoped issues for human legal review without claiming counsel or filing authority.
## Do Not Use When
- The user needs a final jurisdiction-specific legal opinion, legal representation, or authoritative filing decision; prepare the issue and counsel brief instead.
- The review is about code, secrets, permissions, prompt injection, dependencies, or unsafe tool behavior; use `omh-security-safety-review`.
- The request is a plain-language rewrite without a legal-risk review objective; use `omh-content-operator`.
- The user asks to sign, accept, submit, file, publish, or change a policy or contract in an external system; use `omh-apps` only after explicit authority.View the complete source on GitHubomh-lifecycle-growth
When your agent uses it
[omh] Churn or weak activation among users: turn an observed onboarding, activation, retention, re-engagement, referral, or monetization problem into one consent-safe in-app journey or growth experiment plan with a bounded readout and an explicit decision. Use when the user says: lifecycle-growth, lifecycle growth, lifecycle marketing, lifecycle messaging, in-app journey, in-app message campaign, onboarding journey, onboarding nudge.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
601 tokensWhen the skill is activated
Reference documents
4,701 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,862 bytesreferences/full-contract.mddoc8,853 bytesreferences/procedure.mddoc13,741 bytes
Read SKILL.md
# Lifecycle Growth
Required: lifecycle objective, audience/events, consent, budget, and owner. Output: a brief, audience/safety policy, experiment, readout, and handoff.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval. **Completion:** Follow the full-contract checklist.
Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Agent/operator: `omh runtime workflow-artifact lifecycle-growth build --input <json-file-or->` builds bounded metadata only. Shared operator reference: `skill_view(name='omh-routing', file_path='references/workflow-artifacts.md')`.
Contract: `references/full-contract.md`. Procedure: `references/procedure.md`.
## Completion Checklist
View the complete source on GitHubomh-live-incident-response
When your agent uses it
[omh] Production is down or an incident is open: command an incident that is still open -- severity as declared live state, commander and roles, an append-only timeline, a recorded temporary mitigation, verified recovery, and the customer notice. Use when the user says: live-incident-response, live incident response, incident response, active incident, ongoing incident, open incident, incident open, incident commander.
What it loads into context
Frontmatter
189 tokensAlways available to the agent
SKILL.md
2,379 tokensWhen the skill is activated
Reference documents
1,329 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,366 bytesreferences/incident-command-method.mddoc6,192 bytes
Read SKILL.md
# Live Incident Response
This is a Hermes-native `live-incident-response` workflow skill.
## Why This Exists
`live-incident-response` exists because an incident that is still open had no owner. `support-operations` sent an active incident to `reliability-review`, and `reliability-review` reviews incident notes after the fact, so the one skill that saw the request handed it to a postmortem while the outage was still running.
## Do Not Use When
- The incident is over and the request is the postmortem, the SLO or error-budget consequence, or remediation follow-up; use `omh-reliability-review`.
- The request is one customer's support case needing a reply, a severity opinion, and an escalation path, with no incident declared; use `omh-support-operations`.
- The request is a release being rolled out and watched -- deploy checklist, health signals, rollback criteria -- and nothing has been declared broken; use `omh-deploy-and-monitor`.
- The request is to send the page, publish the status-page update, or deliver the customer notice; use `omh-apps`, which records a send as observed only on a returned result.View the complete source on GitHubomh-live-info
When your agent uses it
[omh] Live rate, score, or local time a work task needs: policy overlay for live lookups - add provider, freshness, units, and source-quality gates after preferring native live-data tools for ordinary weather, finance, sports, maps, and time-zone requests. Use when the user says: live-info-operator, live info operator, live information, real time information, real-time information, weather today, current weather, weather forecast.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
1,593 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,487 bytesSKILL.mdcore7,487 bytesSKILL.mdcore7,487 bytesSKILL.mdcore7,487 bytesSKILL.mdcore7,487 bytesSKILL.mdcore7,487 bytes
Read SKILL.md
# Live Info Operator
This is a Hermes-native `live-info-operator` workflow skill.
## Why This Exists
`live-info-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-llm-app-dev
When your agent uses it
[omh] LLM-powered feature to build: LLM app development: prepare a build handoff for an LLM-powered feature with a pinned provider boundary, schema-first outputs, versioned prompt files, grounded retrieval, and an eval suite as a shipped deliverable. Use when the user says: llm-app-dev, llm app development, llm application development, build an llm app, build an llm feature, llm feature development, build a rag pipeline, rag pipeline.
What it loads into context
Frontmatter
208 tokensAlways available to the agent
SKILL.md
3,522 tokensWhen the skill is activated
Reference documents
9,993 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore16,618 bytesSKILL.mdcore16,618 bytesreferences/build-rails.mddoc11,778 bytesreferences/eval-harness.mddoc13,052 bytesreferences/public-board.mddoc7,899 bytesreferences/stateful-contracts.mddoc16,259 bytes
Read SKILL.md
# Llm App Dev
This is a Hermes-native `llm-app-dev` workflow skill.
## Why This Exists
`llm-app-dev` exists because the failure modes of an LLM feature are not the failure modes of the code around it. A floating model alias, a prompt buried in a string literal, an output scraped out of prose with a regex, and a retrieval layer nobody measured all pass code review and all fail in production, and without a golden set nobody can tell whether the next prompt edit helped or hurt.
## Do Not Use When
- The subject is comparing executors or agent harnesses - Codex against Claude Code against Hermes coding - rather than evaluating the product's own model calls; use `omh-agent-evaluation`.
- An agent run is already stuck, looping, or drifting and needs diagnosis; use `omh-agent-debug`.
- The subject is the harness's own context window, prompt caching, or token budget rather than the application being built; use `omh-context-budget-review`.
- The request is a prompt-injection, secret-handling, or dependency risk gate on work that already exists; use `omh-security-safety-review`.View the complete source on GitHubomh-localization-review
When your agent uses it
[omh] Translated product or content release: make a product or content release locale-ready with terminology, cultural-fit, and quality-review guidance. Use when the user says: localization review, translation QA, locale glossary, 현지화 검토, 번역 QA, 용어집.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,490 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,143 bytesSKILL.mdcore7,143 bytesSKILL.mdcore7,143 bytesSKILL.mdcore7,143 bytesSKILL.mdcore7,143 bytesSKILL.mdcore7,143 bytes
Read SKILL.md
# Localization Review
This is a Hermes-native `localization-review` workflow skill.
## Why This Exists
`localization-review` makes terminology, context, cultural fit, and locale QA reviewable without treating a drafted translation as a published or visually validated release.
## Do Not Use When
- The request is a short sentence or word translation or rewrite with no product or locale QA context; answer directly or use `omh-content-operator`.
- The user needs fresh rendered UI evidence, clipping checks, or a visual PASS/REVISE/BLOCK verdict; use `omh-visual-qa`.
- The user asks to edit locale files, push a translation-management-system job, publish strings, or configure localization settings; use `omh-files` or `omh-apps` with explicit target and authority.
- The request asks for a regulatory or contractual conclusion about translated legal text; use `omh-legal-compliance-review`.View the complete source on GitHubomh-long-document-reading
When your agent uses it
[omh] Huge PDF or document to read in full: read a very large PDF, contract, manual, or report through Hermes in page-anchored ranges with a coverage ledger. Use when the user says: long-document-reading, long document reading, summarize this pdf, read this pdf, process this pdf, go through this pdf, summarize this document, read this document.
What it loads into context
Frontmatter
173 tokensAlways available to the agent
SKILL.md
3,773 tokensWhen the skill is activated
Reference documents
1,459 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Long Document Reading Protocol
- Runtime Evidence
Files
SKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesSKILL.mdcore16,125 bytesreferences/hermes-pdf-limits.mddoc5,553 bytes
Read SKILL.md
# Long Document Reading
This is a Hermes-native `long-document-reading` workflow skill.
## Why This Exists
`long-document-reading` exists because a 300-page PDF is about 500,000 characters and Hermes' `read_file` returns 100,000 per call with no page numbers, re-converting the whole file each time; five unanchored reads then sit in the conversation until the ratio-based compressor summarizes them without a page number, so without a ledger the session either truncates, loses the early ranges to compaction, or claims a summary of pages it never read.
## Do Not Use When
- The document is a research paper and the user wants it explained by level; use `omh-paper-learning`.
- The request asks to convert, export, split into a new file, compare two PDFs, or extract tables into CSV; use `omh-materials-package`.
- The input is an image, screenshot, receipt, audio, or video rather than a document; use `omh-media-input`.
- The user is still looking for the document or its download link; use `omh-source-finder`.View the complete source on GitHubomh-market-research
When your agent uses it
[omh] Market sizing or customer/competitive analysis: investigate a scoped market with TAM/SAM/SOM sensitivity, attributed customer evidence, and comparable competitor/pricing profiles before a decision brief. Use when the user says: market-research, market sizing, tam sam som, bottom up market sizing, market size sensitivity, customer evidence analysis, jtbd evidence matrix, competitor pricing profiles.
What it loads into context
Frontmatter
188 tokensAlways available to the agent
SKILL.md
1,358 tokensWhen the skill is activated
Reference documents
4,568 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Files
SKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesSKILL.mdcore6,807 bytesreferences/competitive-pricing.mddoc2,540 bytesreferences/customer-evidence.mddoc2,423 bytesreferences/findings-template.mddoc2,855 bytesreferences/full-contract.mddoc3,544 bytesreferences/market-sizing.mddoc3,345 bytesreferences/procedure.mddoc7,150 bytes
Read SKILL.md
# Market Research
Required: decision and audience, buyer segment and geography, period currency units and source cutoff, available evidence and source boundary, research budget and stop condition. Output: market scope and source ledger, TAM SAM SOM model and sensitivity, customer evidence and JTBD matrix, comparable competitor and pricing profiles, decision-ready market findings.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
`omh-market-research` turns a broad market question into bounded sizing, customer evidence, and comparable competitive analysis that a decision owner can inspect without mistaking secondary research for validation.
## First Steps
- Confirm the decision, buyer/segment, geography, period, currency/base year, units/denominator, source cutoff, budget, and stop condition before retrieval. Mark missing inputs unknown; ask the one that changes the analysis first.
- Read `references/findings-template.md` to open the ledger, then load only the needed methods: `references/market-sizing.md`, `references/customer-evidence.md`, or `references/competitive-pricing.md`. Do not manufacture empty analysis lanes for an out-of-scope question.View the complete source on GitHubomh-materials-package
When your agent uses it
[omh] PPT, PDF, Excel, or HWP output to produce: decks, PDFs, spreadsheets, documents, HWP, Markdown, and binary export handoffs. Use when the user says: materials-package, material package, materials package, document package, deck file, binary export, file export, render qa.
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
2,173 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytesSKILL.mdcore9,634 bytes
Read SKILL.md
# Materials Package
This is a Hermes-native `materials-package` workflow skill.
## Why This Exists
`materials-package` exists so Hermes can handle document, deck, spreadsheet, PDF, Word, Keynote, HWP, and Markdown work as a first-class material-processing workflow without becoming a hidden file generator.
## Do Not Use When
- The user only needs a weekly/monthly report outline; use `omh-report-package`.
- The user asks for recurring meeting minutes or scrum history; use `omh-operating-rhythm`.
- The request is code documentation, README, or project wiki maintenance; use the docs/wiki workflow.
- The user wants an operation done on one existing file - fill a PDF form, merge or split PDFs, or edit the text of a Word document, the slides of a deck, or the cells of a workbook - rather than a material plan with an export and QA ladder; load Hermes' bundled `pdf`, `docx`, `powerpoint`, or `xlsx` skill for that file instead of this one.View the complete source on GitHubomh-media-input
When your agent uses it
[omh] Audio, video, or screenshot to process: user-sent media - audio, video, YouTube links, screenshots, receipts, OCR, meeting recordings, transcripts, timestamps, and clip summaries, gated for source, permission, and hallucination risk. Use when the user says: media-input-operator, media input operator, media input, audio transcription, audio transcript, transcribe audio, transcribe this audio, meeting recording.
What it loads into context
Frontmatter
158 tokensAlways available to the agent
SKILL.md
2,042 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,605 bytesSKILL.mdcore9,605 bytesSKILL.mdcore9,605 bytesSKILL.mdcore9,605 bytesSKILL.mdcore9,605 bytesSKILL.mdcore9,605 bytes
Read SKILL.md
# Media Input Operator
This is a Hermes-native `media-input-operator` workflow skill.
## Why This Exists
`media-input-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-meeting-brief
When your agent uses it
[omh] Upcoming work meeting that lacks an agenda: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.
What it loads into context
Frontmatter
130 tokensAlways available to the agent
SKILL.md
1,367 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,623 bytesSKILL.mdcore6,623 bytesSKILL.mdcore6,623 bytes
Read SKILL.md
# Meeting Brief
This is a Hermes-native `meeting-brief` workflow skill.
## Why This Exists
`meeting-brief` exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.
## Do Not Use When
- The user needs observed meeting minutes, decisions, or action items but has not provided notes.
- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.
- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.
- The meeting already happened, its notes or transcript are in hand, and the user wants decisions, owners, follow-ups, or tickets drawn from them; load Hermes' bundled `meeting-action-items` skill instead of this one.View the complete source on GitHubomh-memory-new
When your agent uses it
[omh] Project fact to remember across future sessions: capture one bounded durable project or product memory candidate through explicit remember, refuse, or defer review; for existing Hermes memory use omh-memory-sync, and for a past decision use decision-recall. Use when the user says: memory-new, new memory, project memory, product memory, remember this project, remember this product, do not save, do not save this token.
What it loads into context
Frontmatter
157 tokensAlways available to the agent
SKILL.md
2,405 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Candidate Decision
- Memory Boundaries
- When to Use
- Catalog Metadata
- Harness
- Runtime Evidence
Files
SKILL.mdcore11,554 bytesSKILL.mdcore11,554 bytesSKILL.mdcore11,554 bytes
Read SKILL.md
# Memory New
This is a Hermes-native `memory-new` workflow skill.
## Why This Exists
`memory-new` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-memory-sync
When your agent uses it
[omh] Outdated or wrong Hermes memory entries: English-canonical Hermes memory-review guidance: inspect USER.md and MEMORY.md claims and prepare a native write diff without invoking, applying, or observing a native write; for a new fact use memory-new, and for a past decision use decision-recall. Use when the user says: memory-sync, memory curation, memory review, memory inspect, memory check, memory update, context cleanup, curate memory.
What it loads into context
Frontmatter
190 tokensAlways available to the agent
SKILL.md
4,285 tokensWhen the skill is activated
Reference documents
754 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- English-Canonical Interview Protocol
- Open Records
- Memory Boundaries
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore19,566 bytesSKILL.mdcore19,566 bytesSKILL.mdcore19,566 bytesSKILL.mdcore19,566 bytesSKILL.mdcore19,566 bytesreferences/source-recovery.mddoc3,494 bytes
Read SKILL.md
# Memory Sync
This is a Hermes-native `memory-sync` workflow skill.
## Why This Exists
`memory-sync` exists because Hermes' memory files are small, capped, and written by more than one hand -- the model, Hermes' own background review, and the person -- so a stale or wrong entry rides in every prompt until someone checks it: this review walks the entries with the person one claim at a time, prepares one diff they approve, and reports only the write Hermes itself returns.
## Do Not Use When
- The user states a new fact to remember; capture it with `omh-memory-new`.
- The user asks what was decided or rejected before; use `omh-decision-recall`.
- The user wants a memory provider enabled, switched, paused, or removed; use `omh-external-connector-readiness`, which owns the provider slot.
View the complete source on GitHubomh-meta-router
When your agent uses it
[omh] Message opens with /omh and a task: meta-routing guidance for a leading /omh command: reason over the imperative task, consult the live workflow catalog, and select or chain the right workflow(s).
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,585 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,546 bytes
Read SKILL.md
# Meta Router
This is a Hermes-native `meta-router` workflow skill.
## Why This Exists
`meta-router` exists to turn a leading /omh command into a live catalog lookup: it reasons over the imperative task, selects or chains concrete workflows, and keeps the decision inside the observed/prepared evidence boundary instead of guessing from memory.
## Do Not Use When
- The /omh token is not the leading command token.
- The message is a bare picker alias or an OMH catalog/entrypoint question — those belong to oh-my-hermes.
## ExamplesView the complete source on GitHubomh-mobile-release
When your agent uses it
[omh] Releasing an iOS or Android app through the stores -- signing, the privacy manifest, a TestFlight or Play beta, a staged rollout, a hotfix: prepare each gate the store enforces, and plan the halt and the next build before the rollout starts, because a store release cannot be rolled back. Use when the user says: mobile-release, mobile release, mobile app release, ios release, android release, app store release, app store submission, submit to the app store.
What it loads into context
Frontmatter
202 tokensAlways available to the agent
SKILL.md
2,158 tokensWhen the skill is activated
Reference documents
637 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,810 bytesSKILL.mdcore9,810 bytesreferences/mobile-release-method.mddoc2,906 bytes
Read SKILL.md
# Mobile Release
This is a Hermes-native `mobile-release` workflow skill.
## Why This Exists
`mobile-release` exists because store releases had no owner: `release-cut` decides a service release that can roll back, `deploy-and-monitor` watches a deploy, and `production-audit` audits readiness platform-neutrally, while signing, a privacy manifest, a TestFlight beta or a Play staged rollout had nothing that knew the store's gates.
## First Steps
- Ask which platforms, which version and build number, and how signing is held today.
- Ask what halts the rollout, before planning any rollout step.
## Do Not Use WhenView the complete source on GitHubomh-model-finetuning
When your agent uses it
[omh] Fine-tuning a model on your own data -- SFT, DPO, RLVR or a LoRA adapter: decide first whether prompting or retrieval already closes the gap, choose the method from the data you have, and promote a checkpoint only when it beats the untuned baseline on a held-out eval. Use when the user says: model-finetuning, model finetuning, model fine-tuning, fine-tune a model, fine-tune the model, fine tune a model, fine tune the model, fine-tune.
What it loads into context
Frontmatter
216 tokensAlways available to the agent
SKILL.md
2,207 tokensWhen the skill is activated
Reference documents
634 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,874 bytesSKILL.mdcore9,874 bytesSKILL.mdcore9,874 bytesreferences/finetuning-method.mddoc2,830 bytes
Read SKILL.md
# Model Finetuning
This is a Hermes-native `model-finetuning` workflow skill.
## Why This Exists
`model-finetuning` exists because producing a model had no owner: `model-optimization` onboards a model into OMH, `inference-serving` serves one that exists, and `llm-app-dev` builds on top of one, while an SFT or DPO question reached `workflow-learning` with no baseline comparison and no way to answer that training is not needed.
## First Steps
- Ask what the untuned model and the best prompt score on the held-out examples before discussing any method.
- Ask what shape the data has -- demonstrations, preference pairs, or answers a program can check.
## Do Not Use WhenView the complete source on GitHubomh-model-optimization
When your agent uses it
[omh] Onboarding a newly released model generation: when a model family ships a new generation or changes its serving contract, walk the recognition, research, calibration, routing, and measurement process that keeps model handling honest and current. Use when the user says: model-optimization, model optimization, optimize for model, onboard new model, calibrate new model, new model calibration, model calibration.
What it loads into context
Frontmatter
164 tokensAlways available to the agent
SKILL.md
1,874 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,396 bytesSKILL.mdcore9,396 bytesSKILL.mdcore9,396 bytesSKILL.mdcore9,396 bytes
Read SKILL.md
# Model Optimization
This is a Hermes-native `model-optimization` workflow skill.
## Why This Exists
`model-optimization` exists so a new model release triggers one repeatable, evidence-ordered process instead of ad-hoc edits: recognition proves what the router sees, official-first research separates contracts from folklore, trait-to-counter keeps calibrations concrete, and the measurement close keeps them honest.
## Do Not Use When
- The user wants their own machine's model routing configured or providers connected; use `omh-model-setup`.
- The goal is measurable performance of an application or system, not model handling; use `ulw-perf`.
- The user wants benchmark-superiority or provider-readiness claims without measurements.
View the complete source on GitHubomh-model-setup
When your agent uses it
[omh] Model and provider configuration changes: diagnose role-slot model configuration, guide provider connection, and apply changes only after diff approval. Use when the user says: model-setup, hermes model setup, set up my models, set up my model, configure my models, configure model provider, connect my model provider, set up model role slots.
What it loads into context
Frontmatter
146 tokensAlways available to the agent
SKILL.md
3,771 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore17,190 bytesSKILL.mdcore17,190 bytesSKILL.mdcore17,190 bytesSKILL.mdcore17,190 bytesSKILL.mdcore17,190 bytes
Read SKILL.md
# Model Setup
This is a Hermes-native `model-setup` workflow skill.
## Why This Exists
`model-setup` exists to turn local model history into a safe, user-confirmed activation flow: Hermes retains native aliases and providers, Maestro remains an external-handoff coordinator, and editable recommendations can fall through missing preferred models without turning metadata into availability or execution claims.
## Do Not Use When
- The user is asking which model Hermes currently is, not asking to inspect, change, connect, or route one.
- The request needs a repository code change rather than local model setup or recommendation review.
- The user wants anti-ban, cooldown-bypass, hidden retry, benchmark-superiority, or provider-entitlement claims.
View the complete source on GitHubomh-molecular-docking
When your agent uses it
[omh] Prepared PDBQT inputs: run bounded standalone Vina docking with real poses, scores and replay provenance; never infer efficacy or safety. Use when the user says: molecular-docking, rigid-receptor docking, PDBQT docking, ligand docking poses, AutoDock Vina.
What it loads into context
Frontmatter
144 tokensAlways available to the agent
SKILL.md
1,179 tokensWhen the skill is activated
Reference documents
4,704 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/scripts/dock.py
Files
SKILL.mdcore5,608 bytesSKILL.mdcore5,608 bytesreferences/execution-and-qa.mddoc5,357 bytesreferences/full-contract.mddoc2,848 bytesreferences/procedure.mddoc4,037 bytestoolkit/NOTICE.mddoc1,647 bytestoolkit/README.mddoc7,069 bytestoolkit/examples/settings.jsonasset581 bytestoolkit/scripts/dock.pyruns17,670 bytestoolkit/upstream-manifest.jsonasset6,050 bytes
Read SKILL.md
# Molecular Docking
Required: prepared receptor and ligand PDBQT paths, binding box and preparation provenance, approved local resource budget. Output: molecular_docking_preflight/v1, molecular_docking_run/v1 and real pose/score files.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
Input validation and tutorial numbers are not measured docking. Require a real engine search and digest-bound poses, finite energies and replay settings.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md`. Use the explicitly invoked standalone Vina Python helper, not an invented ToolUniverse tool or hidden core execution service.
- Recover prepared file paths, source/license and preparation receipts, angstrom binding box, seed, CPU, new output directory and host deadline. Never guess a site, silently prepare a molecule or install dependencies on skill load.View the complete source on GitHubomh-morning-brief
When your agent uses it
[omh] Mail and calendar brief configuration: morning brief SETUP (one-time) - connects mail and calendar MCP with read-and-draft-only scope and diff approval; produces the configuration, not the daily brief itself. Use when the user says: morning-brief, morning brief, connect my email for a morning brief, set up morning brief, configure morning brief, connect mail for morning brief, connect calendar for morning brief, set up my morning brief.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
1,892 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,088 bytesSKILL.mdcore9,088 bytes
Read SKILL.md
# Morning Brief
This is a Hermes-native `morning-brief` workflow skill.
## Why This Exists
`morning-brief` exists to connect mail and calendar access for an on-demand brief while keeping the connection strictly read and draft-only and credential entry outside chat, with explicit storage authorization.
## Do Not Use When
- The user wants Hermes to check their email or calendar right now rather than set up the connection.
- The connection is already configured and the user only wants today's brief, not a setup walkthrough.
- The request needs a repository code change rather than a local MCP config edit.
View the complete source on GitHubomh-native-debugging
When your agent uses it
[omh] Native program crashes or corrupts memory: prepare hypothesis-driven debugging of native binaries and instruct the executor to drive a DAP debugger instead of printf. Use when the user says: native-debugging, native debugging, native binary, segfault, segmentation fault, core dump, stack corruption, memory corruption.
What it loads into context
Frontmatter
172 tokensAlways available to the agent
SKILL.md
2,224 tokensWhen the skill is activated
Reference documents
1,308 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,101 bytesSKILL.mdcore10,101 bytesSKILL.mdcore10,101 bytesSKILL.mdcore10,101 bytesreferences/native-debug-loop.mddoc5,941 bytes
Read SKILL.md
# Native Debugging
This is a Hermes-native `native-debugging` workflow skill.
## Why This Exists
`native-debugging` closes OMH's zero-coverage low-level domain by preparing a hypothesis-driven, DAP-first debugging plan for native binaries, while OMH itself continues to execute nothing.
## Do Not Use When
- The failure is a build or CI failure rather than a runtime fault in a binary; use `omh-build-failure-triage`.
- The subject is an agent or workflow misbehaving rather than a native binary; use `omh-agent-debug`.
- The wrong result, flaky test, or lost update is in application code such as a Python or TypeScript service and needs its root cause reproduced; use `omh-app-debugging`.
- The change is Rust source work whose risk is `unsafe` or UB discipline; use `omh-rust`.View the complete source on GitHubomh-operating-rhythm
When your agent uses it
[omh] Team minutes, retros, and decision history to keep: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,533 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytesSKILL.mdcore7,322 bytes
Read SKILL.md
# Operating Rhythm
This is a Hermes-native `operating-rhythm` workflow skill.
## Why This Exists
`operating-rhythm` exists so recurring operating work has durable minutes, decisions, and follow-up history without pretending a meeting outcome was observed.
## Do Not Use When
- The user only needs a one-off meeting agenda before the meeting; use `omh-meeting-brief`.
- The request is a weekly status/risk summary rather than cadence history; use `omh-ops-review`.
- The user asks for report packaging, PPT outline, or reliability evidence review.
View the complete source on GitHubomh-ops-observability-card
When your agent uses it
[omh] Tracking cost, tokens, latency, or service health: prepare an operations command-board for wrapper-safe token, cost, latency, run history, queue, failure-mode, external metric-provider, and service-quality evidence boundaries. Use when the user says: ops-observability-card, observability card, operations command board, ops command board, service quality board, service quality, external metric provider, metric provider.
What it loads into context
Frontmatter
170 tokensAlways available to the agent
SKILL.md
1,883 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,002 bytesSKILL.mdcore9,002 bytes
Read SKILL.md
# Ops Observability Card
This is a Hermes-native `ops-observability-card` workflow skill.
## Why This Exists
`ops-observability-card` exists so service, loop, and automation operations get one board where each cost, latency, token, failure-mode, and metric-provider figure is marked observed or prepared, instead of an improvised dashboard.
## Do Not Use When
- The user asks what their own Hermes conversation has used or cost; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user wants one run's timing and context-budget report; use `omh-run-efficiency`.
- The user asks OMH to sign in to a metric provider, billing console, or dashboard and pull live figures; the card reads only supplied payloads and Hermes' own records.
View the complete source on GitHubomh-ops-review
When your agent uses it
[omh] Recurring operating status and blockers: status, risks, blockers, priorities, and follow-ups. Use when the user says: ops-review, ops review, weekly ops review, status review, operating review, release risks, risks and blockers, priorities.
What it loads into context
Frontmatter
140 tokensAlways available to the agent
SKILL.md
1,332 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,254 bytesSKILL.mdcore6,254 bytes
Read SKILL.md
# Ops Review
This is a Hermes-native `ops-review` workflow skill.
## Why This Exists
`ops-review` exists to keep `operations` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The review is over sales stages, forecast categories, deal aging, or seller forecast rather than generic operating status; use `omh-sales-pipeline-review`.
- The primary output is durable cadence history, minutes, a decision log, or action history; use `omh-operating-rhythm`.
## ExamplesView the complete source on GitHubomh-paper-learning
When your agent uses it
[omh] Paper or paper PDF to understand: explain a supplied paper or paper/PDF at a selected level while preserving full section coverage and source evidence boundaries. Use when the user says: paper-learning, paper learning, paper-explainer, paper explainer, paper explanation, explain this paper, explain this arxiv paper, paper walkthrough.
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
2,201 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytesSKILL.mdcore10,297 bytes
Read SKILL.md
# Paper Learning
This is a Hermes-native `paper-learning` workflow skill.
## Why This Exists
`paper-learning` exists so Hermes can act like a strong human tutor for papers: choose the right explanation level, walk through the full paper section by section, and keep PDF extraction and validation evidence honest.
## Do Not Use When
- The request asks to export, convert, render, or package a file; use `omh-materials-package`.
- The request asks for daily/weekly paper monitoring, digest, source inbox, or Scout/Analyst/Briefer operations; use `omh-research-department`.
- The request asks to find current papers or sources when no supplied paper exists; use `ulw-research`.
- The request asks for a visual/image card; use `omh-image-cards`.View the complete source on GitHubomh-parallel-tools
When your agent uses it
[omh] Parallel tool-call capability in doubt: report the version and whether MCP parallel tool calls are enabled, then apply the diff for parallel tool calls only after approval; an update only on request. Use when the user says: parallel-tools, parallel tools, hermes parallel tools setup, update hermes for parallel tools, check parallel tool support, enable parallel tool calls, verify parallel tools capability, check hermes version for parallel tools.
What it loads into context
Frontmatter
163 tokensAlways available to the agent
SKILL.md
1,819 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,769 bytesSKILL.mdcore8,769 bytes
Read SKILL.md
# Parallel Tools
This is a Hermes-native `parallel-tools` workflow skill.
## Why This Exists
`parallel-tools` exists to give a read-first answer to whether tools run in parallel and to name the one setting a user controls: built-in read-only tools already run concurrently, and an MCP server's tools do only when its `supports_parallel_tool_calls` is true.
## Do Not Use When
- The user wants a general Hermes update unrelated to parallel-tool capability.
- No version or capability question has been asked yet.
- The request needs a repository code change rather than a local version check.
View the complete source on GitHubomh-people-ops
When your agent uses it
[omh] Company hiring or HR process to structure: turn hiring and people context into a fair, structured recruiting or people-operations brief. Use when the user says: recruiting plan, hiring scorecard, interview scorecard, candidate debrief, 채용 계획, 면접 평가표, 후보자 비교.
What it loads into context
Frontmatter
156 tokensAlways available to the agent
SKILL.md
1,478 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,111 bytesSKILL.mdcore7,111 bytes
Read SKILL.md
# People Ops
This is a Hermes-native `people-ops` workflow skill.
## Why This Exists
`people-ops` keeps recruiting and people-process guidance fair, structured, and evidence bounded before any human decision or external HR action.
## Do Not Use When
- The request asks for a jurisdiction-specific employment-law conclusion, policy compliance ruling, or contract interpretation; use `omh-legal-compliance-review`.
- The user only needs a one-off job-ad, rejection, or interview-email rewrite; use `omh-content-operator`.
- The user asks to create ATS records, send invitations, book interviews, change employment status, or modify HRIS settings; use `omh-apps` with explicit authorization and observed results.
- The prompt asks the workflow to make an unsupported candidate decision from protected characteristics or missing interview evidence; retain the process and evidence gap instead.View the complete source on GitHubomh-physical-device-readiness
When your agent uses it
[omh] Agent control of a robot, 3D printer, or IoT relay: gate robots, 3D printers, IoT relays, sensors, and lab hardware before trials; use external-connector-readiness for provider or connector adoption and toolbelt-readiness for missing control tools. Use when the user says: physical-device-readiness, physical device readiness, device safety readiness, physical device safety, hardware safety gate, 3d printer readiness, 3D printer safety, snapmaker printer safety.
What it loads into context
Frontmatter
208 tokensAlways available to the agent
SKILL.md
2,115 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,987 bytesSKILL.mdcore9,987 bytes
Read SKILL.md
# Physical Device Readiness
This is a Hermes-native `physical-device-readiness` workflow skill.
## Why This Exists
`physical-device-readiness` exists because a robot, heater, or relay acts on the physical world, where a wrong command can hurt someone or damage property: it fixes the safety envelope, sensor and camera gates, dry runs, operator approval, and emergency stop before any trial, and turns the commands the agent must never run into a proposed deny list the user applies.
## Do Not Use When
- The device is reached through a provider or connector the user has not adopted yet; use `omh-external-connector-readiness`.
- The tool that would control the device is missing; use `omh-toolbelt-readiness`.
- The user asks to run the command, move the hardware, or start the print now; use `omh-terminal` or `omh-apps`, which need observed operator approval before any execution claim.
View the complete source on GitHubomh-plan
When your agent uses it
[omh] Software feature or bugfix not yet planned: structured planning before execution. Use when the user says: plan, implementation plan, make a plan, write a plan, write the plan, task breakdown, safe feature, safely add a feature.
What it loads into context
Frontmatter
115 tokensAlways available to the agent
SKILL.md
3,106 tokensWhen the skill is activated
Reference documents
1,319 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore14,405 bytesSKILL.mdcore14,405 bytesSKILL.mdcore14,405 bytesSKILL.mdcore14,405 bytesreferences/hermes-plan-mode.mddoc2,451 bytesreferences/project-constitution.mddoc3,427 bytes
Read SKILL.md
# Plan
This is a Hermes-native `plan` workflow skill.
## Why This Exists
`plan` exists so a feature or a fix gets its goals, non-goals, risks, acceptance criteria, and verification shape written down and accepted by the user before any code moves, with every step small enough to check and no implementation hidden inside the plan text.
## 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.
## ExamplesView the complete source on GitHubomh-product-brief
When your agent uses it
[omh] PRD or roadmap priorities to decide: turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.
What it loads into context
Frontmatter
178 tokensAlways available to the agent
SKILL.md
1,654 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,736 bytesSKILL.mdcore7,736 bytes
Read SKILL.md
# Product Brief
This is a Hermes-native `product-brief` workflow skill.
## Why This Exists
`product-brief` turns product evidence into a reviewable PRD and prioritization frame before delivery planning without treating a draft as an accepted roadmap commitment.
## Do Not Use When
- The input is unprocessed feedback, bug reports, or feature asks that first need clustering and evidence boundaries; use `omh-feedback-triage`.
- The product evidence is unvalidated, synthetic, or a founder belief and the problem gate has not returned validated; use `omh-product-discovery-validation` before a PRD.
- The input is a growth hypothesis that still needs an experiment and readout before it becomes a product requirement; use `omh-lifecycle-growth`.
- The user needs a company or product strategy decision across high-level options rather than a requirements or roadmap artifact; use `omh-decide`.View the complete source on GitHubomh-product-discovery-validation
When your agent uses it
[omh] Unvalidated early product idea: test whether a customer problem, segment, and business hypothesis deserve product investment, ending in kill, pivot, persevere, or inconclusive before any PRD. Use when the user says: product-discovery-validation, product discovery validation, product discovery, customer discovery, customer discovery plan, zero to one validation, validate the problem before building, problem solution interview.
What it loads into context
Frontmatter
195 tokensAlways available to the agent
SKILL.md
615 tokensWhen the skill is activated
Reference documents
4,147 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,944 bytesreferences/full-contract.mddoc7,358 bytesreferences/procedure.mddoc12,148 bytes
Read SKILL.md
# Product Discovery Validation
Required: problem, segment/evidence, owner, learning budget, and criteria. Output: a decision frame, evidence and customer plan, test portfolio, receipt, and GTM hypothesis.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval. **Completion:** Follow the full-contract checklist.
Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Agent/operator: `omh runtime workflow-artifact product-discovery-validation build --input <json-file-or->` builds bounded metadata only. Shared operator reference: `skill_view(name='omh-routing', file_path='references/workflow-artifacts.md')`.
Contract: `references/full-contract.md`. Procedure: `references/procedure.md`.
## Completion Checklist
View the complete source on GitHubomh-production-audit
When your agent uses it
[omh] Imminent production launch or release: evaluate release, deploy, security, observability, rollback, docs, and support readiness without claiming production access. Use when the user says: production-audit, production audit, production readiness, prod audit, prod readiness, ready for production, ready to ship, ship readiness.
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
1,560 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,422 bytesSKILL.mdcore7,422 bytesSKILL.mdcore7,422 bytes
Read SKILL.md
# Production Audit
This is a Hermes-native `production-audit` workflow skill.
## Why This Exists
`production-audit` gives OMH a preflight release surface so operators can see production risks before launch while OMH stays out of deploy and infrastructure execution.
## Do Not Use When
- The user wants to implement a feature or fix; prepare a coding handoff first.
- The user wants incident/SLO analysis after production behavior; use `omh-reliability-review`.
- The user wants a narrow code diff review; use `omh-code-review`.
View the complete source on GitHubomh-prompt-import-readiness
When your agent uses it
[omh] Importing prompt files for Hermes: prompt import readiness - review and normalize external CLI-agent prompt files before offering slash-command candidates; use external-connector-readiness for plugin or API adoption and toolbelt-readiness for missing runtime capabilities. Use when the user says: prompt-import-readiness, prompt import readiness, slash prompt import, slash prompts import, slash command prompt import, prompt library import, prompt folder import, prompt directory import.
What it loads into context
Frontmatter
191 tokensAlways available to the agent
SKILL.md
2,190 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytesSKILL.mdcore10,511 bytes
Read SKILL.md
# Prompt Import Readiness
This is a Hermes-native `prompt-import-readiness` workflow skill.
## Why This Exists
`prompt-import-readiness` exists because a prompt library from another CLI agent does not become Hermes commands by copying files: Hermes' own importer skips Claude Code's slash-command prompts and never reads Codex prompt files, its quick commands hold no prompt, and a new name can collide with a built-in command, a quick command, or a skill. This card inventories the sources, maps arguments, and settles each name before anything is written.
## Do Not Use When
- Adopting a plugin, connector, API, or memory provider; use `omh-external-connector-readiness`.
- A runtime capability or CLI the work needs is missing; use `omh-toolbelt-readiness`.
- Searching for an existing skill to reuse before writing one; use `omh-skill-scout`.
View the complete source on GitHubomh-provider-profile-posture
When your agent uses it
[omh] Provider credentials without exposure: prepare provider-profile metadata without reading secrets or calling providers. Use when the user says: provider-profile-posture, provider profile posture, provider profile readiness, secret presence confirmation, connector profile posture, 공급자 프로필 상태, 시크릿 존재 확인, 커넥터 준비 상태.
What it loads into context
Frontmatter
137 tokensAlways available to the agent
SKILL.md
1,360 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,788 bytesSKILL.mdcore6,788 bytes
Read SKILL.md
# Provider Profile Posture
This is a Hermes-native `provider-profile-posture` workflow skill.
## Why This Exists
`provider-profile-posture` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-refactor-plan
When your agent uses it
[omh] Decided cross-module refactor to phase: refactor planning - turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.
What it loads into context
Frontmatter
195 tokensAlways available to the agent
SKILL.md
2,202 tokensWhen the skill is activated
Reference documents
2,608 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,279 bytesreferences/dependency-upgrade.mddoc5,274 bytesreferences/interface-shaping.mddoc3,095 bytesreferences/refactor-phases.mddoc3,415 bytes
Read SKILL.md
# Refactor Plan
This is a Hermes-native `refactor-plan` workflow skill.
## Why This Exists
`refactor-plan` exists because boundary-changing refactors bounced between goal planning and behavior-preserving cleanup with neither owning the execution shape: the phase order, the per-phase rollback, and the files table that make a large refactor reviewable and abortable.
## Do Not Use When
- The refactor's direction is still contested or the goal itself needs consensus planning; use `ulw-plan`.
- The work is deletion-first cleanup with no boundary changes; use `omh-ai-slop-cleaner`.
- The plan is done and the claim is that work is complete; use `omh-verification-gate` for the evidence close.
- The version bump carries a security advisory, a CVE, or a leaked secret; use `omh-security-event-response`, which owns containment and closure.View the complete source on GitHubomh-relational-db
When your agent uses it
[omh] Database work on a relational store -- a slow query, an index to size, a migration on a big table, a lock taken during deploy, N+1 queries: plan it with the checks that prove it safe, and never call a migration ready without its lock behaviour and rollback. Use when the user says: relational-db, relational database, online migration, migration for a large table, lock-safe ddl, alter table, took a lock, table lock.
What it loads into context
Frontmatter
194 tokensAlways available to the agent
SKILL.md
2,230 tokensWhen the skill is activated
Reference documents
2,259 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,865 bytesSKILL.mdcore9,865 bytesSKILL.mdcore9,865 bytesreferences/engine-lock-tables.mddoc9,415 bytes
Read SKILL.md
# Relational Db
This is a Hermes-native `relational-db` workflow skill.
## Why This Exists
`relational-db` exists because the database work itself had no owner: `backend` owns `schema_migration_plan/v1` for a service change, and an index question, a lock taken during deploy, or an N+1 finding was answered by a data, deploy, or interview lane with no lock model at all.
## First Steps
- Ask for the engine, the version, and the table sizes before proposing any statement.
- For a migration, give every step its lock behaviour and its rollback before calling the plan ready.
## Do Not Use WhenView the complete source on GitHubomh-release-cut
When your agent uses it
[omh] Shipping a versioned release -- tag it, stage it behind a canary, or roll back the last deploy: decide what goes in, the version, the rollout stages, and a rollback with its trigger and exact command before it is needed. Use when the user says: release-cut, release cut, cut a release, cut the release, cut a new release, tag a release, tag the release, release candidate.
What it loads into context
Frontmatter
194 tokensAlways available to the agent
SKILL.md
2,096 tokensWhen the skill is activated
Reference documents
724 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,541 bytesSKILL.mdcore9,541 bytesreferences/release-and-rollback-method.mddoc3,137 bytes
Read SKILL.md
# Release Cut
This is a Hermes-native `release-cut` workflow skill.
## Why This Exists
`release-cut` exists because nothing owned deciding a release: `deploy-and-monitor` watches a rollout that is already happening, and a cut, a canary, or a rollback decision reached an image card or a watch lane with no rollback trigger at all.
## First Steps
- State what goes in, what is held back, and the version before proposing the cut.
- Name the rollback trigger and its exact command before the first stage ships.
## Do Not Use WhenView the complete source on GitHubomh-reliability-review
When your agent uses it
[omh] Postmortem for an outage or SLO miss: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
1,509 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,212 bytesSKILL.mdcore7,212 bytesSKILL.mdcore7,212 bytesSKILL.mdcore7,212 bytesSKILL.mdcore7,212 bytes
Read SKILL.md
# Reliability Review
This is a Hermes-native `reliability-review` workflow skill.
## Why This Exists
`reliability-review` exists to make SRE-style review strict: service reliability claims must point to metrics or references, and remediation remains separate from the review narrative.
## Do Not Use When
- The user only needs a generic status report or leadership deck.
- No service, incident, SLO, metric, or reliability source boundary is available.
- The request is implementation of remediation rather than review of reliability evidence.
- The incident is still open and the user needs severity declared, a commander assigned, a running timeline, and recovery verified; use `omh-live-incident-response` and review it once it is closed.View the complete source on GitHubomh-report-package
When your agent uses it
[omh] Periodic report for executives: weekly/monthly reports, executive briefs, PPT-ready outlines, and upload packages. Use when the user says: report-package, report package, weekly report, monthly report, executive report, exec brief, leadership deck, status package.
What it loads into context
Frontmatter
134 tokensAlways available to the agent
SKILL.md
1,647 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,790 bytesSKILL.mdcore7,790 bytesSKILL.mdcore7,790 bytes
Read SKILL.md
# Report Package
This is a Hermes-native `report-package` workflow skill.
## Why This Exists
`report-package` exists to make reporting a first-class operations surface: Hermes can produce clean report and slide outlines while keeping approvals, delivery, and binary deck export as separate evidence.
## Do Not Use When
- The user needs SLO, incident, or error-budget review; use `omh-reliability-review`.
- The user asks for a live `.pptx` deck file rather than a PPT-ready outline.
- The request is meeting minutes, scrum history, or action-item tracking.
View the complete source on GitHubomh-repro-audit
When your agent uses it
[omh] Evaluation logs versus reported paper conditions: audit supplied HellaSwag results with exact scores and review-gated evidence; never run a model. Use when the user says: repro-audit, hellaswag log, hellaswag results, hellaswag score.
What it loads into context
Frontmatter
125 tokensAlways available to the agent
SKILL.md
1,535 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytesSKILL.mdcore7,557 bytes
Read SKILL.md
# Repro Audit
This is a Hermes-native `repro-audit` workflow skill.
## Why This Exists
A displayed score is not evidence that evaluation conditions match. This workflow compares retained source claims without executing an evaluator or inventing missing conditions.
## First Steps
- Ask which metric the person means if acc versus acc_norm is not explicit; never substitute one for the other.
- Use only supplied local files. If no evaluation record is available, ask for one; do not run or fetch a model.
- For agent infrastructure, call `omh paper import-harness --results FILE --metric acc_norm --out NEW_CASE` for native Harness JSON; `--metric acc` is a separate profile.
- When authoring a normalized case instead, call `omh paper audit-init --out NEW_CASE [--metric acc_norm]`; omitted metric preserves the acc default. All conditions start unknown.View the complete source on GitHubomh-research-brief
When your agent uses it
[omh] Business question on market, competitors, pricing: business research brief - turns a market, competitor, pricing, or customer question into a structured evidence-vs-inference brief; for raw link gathering use ulw-research, and for ongoing multi-role research use research-department. Use when the user says: research-brief, business-research, business research, research brief, decision brief, pricing decision brief, decision-ready brief, source-backed business research.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
2,130 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytesSKILL.mdcore10,265 bytes
Read SKILL.md
# Research Brief
This is a Hermes-native `research-brief` workflow skill.
## Why This Exists
`research-brief` exists to keep `research` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
## Do Not Use When
- The user needs to decide whether a customer problem deserves product investment with evidence typing and customer re-entry; use `omh-product-discovery-validation`.
- The request is only fresh links, citations, or current facts without a business question or decision audience; use `ulw-research`.
- Sources have not yet been selected and the user wants source types, candidates, or acquisition state; use `omh-source-finder`.
View the complete source on GitHubomh-research-department
When your agent uses it
[omh] Recurring market or topic research: research operations department - coordinate Scout, Analyst, and Briefer work with source-inbox and status boundaries; for one decision brief use research-brief, and for typed candidates before research starts use source-finder. Use when the user says: research-department, research department, research ops department, research operations department, scout analyst briefer, scout analyst brief, daily research department, competitor research department.
What it loads into context
Frontmatter
194 tokensAlways available to the agent
SKILL.md
2,318 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytesSKILL.mdcore11,227 bytes
Read SKILL.md
# Research Department
This is a Hermes-native `research-department` workflow skill.
## Why This Exists
`research-department` exists so Hermes users can start complex research-ops patterns without manually designing profiles, cron, knowledge storage, synthesis tooling, and delivery glue, while OMH keeps every runtime claim observed-only.
## Do Not Use When
- The user only needs a one-off current-source lookup; use `ulw-research`.
- The user only needs a one-off business synthesis; use `omh-research-brief`.
- The request is pure scheduling with no source collection or synthesis; use `omh-automation-blueprint`.
- The user asks for coding implementation; prepare a selected executor/runtime handoff after the research plan is accepted.View the complete source on GitHubomh-routing
When your agent uses it
[omh] Choosing among OMH skills for a request: router guidance for using oh-my-hermes workflow skills inside Hermes Agent.
What it loads into context
Frontmatter
90 tokensAlways available to the agent
SKILL.md
2,911 tokensWhen the skill is activated
Reference documents
33,754 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Routing Contract
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- OMH Awareness Primer (Compact)
- OMH Orchestration Posture
- Priority Rules
- Direct Picker Aliases
- Install And CLI Boundary
- Wrapper Backend Summary
- Runtime Evidence
- Hermes Compatibility
- Progressive Disclosure References
- Recovery
Files
SKILL.mdcore13,591 bytesSKILL.mdcore13,591 bytesSKILL.mdcore13,591 bytesSKILL.mdcore13,591 bytesSKILL.mdcore13,591 bytesreferences/catalog-index.mddoc33,172 bytesreferences/coding-handoff-progress-reporting.mddoc4,945 bytesreferences/evidence-boundaries.mddoc2,670 bytesreferences/harness-registry.mddoc22,047 bytesreferences/human-voice.mddoc7,309 bytesreferences/jev-rail.mddoc6,255 bytesreferences/operator-maintenance.mddoc1,631 bytesreferences/skill-common-rail.mddoc15,630 bytesreferences/structural-code-search.mddoc3,848 bytesreferences/workflow-artifacts.mddoc2,640 bytesreferences/workflow-registry.mddoc33,837 bytesreferences/wrapper-routing.mddoc10,343 bytes
Read SKILL.md
# Oh My Hermes Router
Reasoning demand: `light`
Use this skill when the user mentions oh-my-hermes or a workflow keyword such as `deep-interview`, `ultraperf`, `ralplan`, `loop`, `product-docs`, `research`, `research-department`, `source-finder`, `paper-learning`, `long-document-reading`, `data-analysis`, `command-operator`, `connector-operator`, `live-info-operator`, `external-connector-readiness`, `physical-device-readiness`, `content-operator`, `media-input-operator`, `feedback-triage`, `finance-analysis`, `people-ops`, `legal-compliance-review`, `support-operations`, `curriculum-design`, `localization-review`, `sales-development`, `product-brief`, `materials-package`, `img-summary`, `design-quality-gate`, `frontend`, `accessibility-audit`, `visual-qa`, `browser-operator`, `workspace-file-operator`, `automation-blueprint`, `harness-session-inventory`, `agent-debug`, `failure-signal-audit`, `instinct-ledger`, `skill-scout`, `skill-health`, `workflow-learning`, `codebase-onboarding`, `codegraph-refresh`, `codebase-uml`, `context-budget-review`, `run-efficiency`, `provider-profile-posture`, `decision-recall`, `security-safety-review`, `application-threat-model`, `live-incident-response`, `code-review`, `build-failure-triage`, `ultrawork`, `ultraqa`, `doctor`.
## Routing Contract
This is best-effort Hermes prompt guidance. It does not override Hermes core routing and it does not claim exact runtime parity with another agent framework.
Normal users should talk to Hermes Agent or invoke installed Hermes skills. Do not ask chat users to run `omh`; it is bootstrap and backend infrastructure.
## Why This Exists
View the complete source on GitHubomh-rules-distill
When your agent uses it
[omh] Turn repeated lessons into written rules: extract repeated principles from skills, prompts, traces, reviews, and failures into reviewed rule candidates without auto-mutating guidance. Use when the user says: rules-distill, rules distill, distill rules, rule distillation, principle distill, skill principles, extract agent rules, turn traces into rules.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
2,061 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,670 bytesSKILL.mdcore9,670 bytesSKILL.mdcore9,670 bytesSKILL.mdcore9,670 bytesSKILL.mdcore9,670 bytesSKILL.mdcore9,670 bytes
Read SKILL.md
# Rules Distill
This is a Hermes-native `rules-distill` workflow skill.
## Why This Exists
`rules-distill` gives OMH a disciplined way to learn from large skill ecosystems like ECC without wholesale copying: extract principles, review them, then patch OMH only through explicit verified work.
## Do Not Use When
- The user wants a single workflow route regression; use `omh-workflow-learning`.
- The user wants durable factual project memory; use `omh-wiki` or memory curation.
- The user already approved a concrete code/doc change; use the implementation workflow.
- The ask is writing or keeping current the file an agent reads at startup -- AGENTS.md, CLAUDE.md, a Cursor rule; use `omh-agent-instructions`, which updates only its marked region.View the complete source on GitHubomh-run-efficiency
When your agent uses it
[omh] Run efficiency and context usage report: report supplied local run efficiency while provider data stays unobserved. Use when the user says: run-efficiency, run efficiency report, local run efficiency, context utilization, tool duration report, 실행 효율 리포트, 컨텍스트 사용량, 도구 지연 시간.
What it loads into context
Frontmatter
154 tokensAlways available to the agent
SKILL.md
1,535 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,274 bytesSKILL.mdcore7,274 bytes
Read SKILL.md
# Run Efficiency
This is a Hermes-native `run-efficiency` workflow skill.
## Why This Exists
`run-efficiency` exists so a question about how a run spent its time, tools, and context gets the supplied timings and context budget, plus what Hermes itself recorded for a named session's tokens and cost, instead of figures a model guesses.
## Do Not Use When
- The user asks only what this Hermes conversation has used or cost so far; Hermes' /usage shows this session's tokens and context, /insights estimates cost across recent sessions, and the omh_run_summary tool relays this conversation's recorded tokens and cost.
- The user wants service latency, uptime, error rates, or supplied metric-provider figures; use `omh-ops-observability-card`.
- The user wants a provider invoice or quota truth; no OMH report observes either, so name the provider's own console as the source.
View the complete source on GitHubomh-running-work-board
When your agent uses it
[omh] Live view of running coding units: showing which coding units are running right now, on which runtime and model, with observed tokens and elapsed time. Use when the user says: running-work-board, running work board, which units are running, what models are running, 지금 뭐 돌고 있어, 뭐가 돌고 있어, 어떤 모델로 돌고 있어, 실행 중인 작업 보여줘.
What it loads into context
Frontmatter
149 tokensAlways available to the agent
SKILL.md
1,450 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,734 bytes
Read SKILL.md
# Running Work Board
This is a Hermes-native `running-work-board` workflow skill.
## Why This Exists
`running-work-board` exists because multi-session coding work was invisible: the runtime was tracked but the model was dropped, token counts had no write site at all, and a blocking dispatch could not report that it was still running. The board answers which model on which runtime, or says unknown.
## Do Not Use When
- The user wants to start, plan, or dispatch coding work rather than observe it.
- The user wants review, CI, or merge evidence, which a status board never provides.
- The user is asking about their own application's runtime status rather than OMH coding units.
View the complete source on GitHubomh-rust
When your agent uses it
[omh] Rust ownership, lifetime, or unsafe trouble: prepare Rust changes with ownership, error, and API discipline, and escalate any unsafe, FFI, or lock-free change to the UB checklist. Use when the user says: rust, rust code, rust skill, rustlang, borrow checker, lifetime error, ownership error, trait bound.
What it loads into context
Frontmatter
160 tokensAlways available to the agent
SKILL.md
2,294 tokensWhen the skill is activated
Reference documents
3,622 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,057 bytesSKILL.mdcore10,057 bytesreferences/rust-discipline.mddoc10,231 bytesreferences/ub-escalation.mddoc5,364 bytes
Read SKILL.md
# Rust
This is a Hermes-native `rust` workflow skill.
## Why This Exists
`rust` closes OMH's zero-coverage Rust domain and makes the escalation from ordinary Rust work to undefined-behavior discipline a deterministic routing rule rather than something a model is trusted to notice.
## Do Not Use When
- The request is a server, API, or schema design that happens to mention a Rust stack; use `omh-backend` for the contract and name Rust as the stack.
- The request is debugging a stripped or source-less native binary; use `omh-native-debugging`.
- The request is a general code review of finished Rust; use `omh-code-review`.
- The request is a Rust vocabulary or concept question with no change to prepare; answer it directly.View the complete source on GitHubomh-sales-development
When your agent uses it
[omh] Prospect or account worth pursuing: turn an account or market opportunity into a focused discovery, qualification, and next-step brief. Use when the user says: sales discovery, account plan, outbound messaging, 영업 발굴, 고객사 계획, 아웃바운드 메시지.
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
1,551 tokensWhen the skill is activated
Reference documents
1,501 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,468 bytesSKILL.mdcore7,468 bytesSKILL.mdcore7,468 bytesreferences/procedure.mddoc6,966 bytes
Read SKILL.md
# Sales Development
This is a Hermes-native `sales-development` workflow skill.
## Why This Exists
`sales-development` prepares evidence-bounded discovery and qualification guidance without claiming sales execution.
## Do Not Use When
- The user needs a company-level positioning, market-entry, or strategic-options decision rather than account-level discovery; use `omh-decide`.
- The user supplies a CRM export or pipeline snapshot and needs portfolio health, aging, slipped deals, forecast calibration, or renewal-risk review; use `omh-sales-pipeline-review`.
- The user only wants a polished social post, newsletter, or one-off outbound-copy rewrite; use `omh-content-operator`.
- The user asks to send outreach, update Salesforce or HubSpot, create an opportunity, or book a meeting; use `omh-apps` with explicit recipient, object, and authority.View the complete source on GitHubomh-sales-pipeline-review
When your agent uses it
[omh] CRM pipeline or sales forecast to review: turn a supplied CRM export or pipeline snapshot into an evidence-bound pipeline health, forecast, and follow-up review. Aliases: pipeline-review, forecast-review, deal-review. Use when the user says: sales-pipeline-review, sales pipeline review, pipeline review, pipeline health, pipeline coverage, deal review, deal health, sales forecast review.
What it loads into context
Frontmatter
189 tokensAlways available to the agent
SKILL.md
607 tokensWhen the skill is activated
Reference documents
3,565 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Completion Checklist
- Recovery Notes
- Workflow Lane
Files
SKILL.mdcore2,871 bytesreferences/full-contract.mddoc7,143 bytesreferences/procedure.mddoc9,910 bytes
Read SKILL.md
# Sales Pipeline Review
Required: supplied snapshot and as-of time, definitions, prior outcomes, and owner. Output: scope, health, forecast, supported annexes, and follow-up handoff.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval. **Completion:** Follow the full-contract checklist.
Shared product, routing, compatibility, and evidence rules: `skill_view(name='omh-routing', file_path='references/skill-common-rail.md')`.
Agent/operator: `omh runtime workflow-artifact sales-pipeline-review prepare --input <json-file-or->` prepares bounded metadata only. Shared operator reference: `skill_view(name='omh-routing', file_path='references/workflow-artifacts.md')`.
Contract: `references/full-contract.md`. Procedure: `references/procedure.md`.
## Completion Checklist
View the complete source on GitHubomh-security-event-response
When your agent uses it
[omh] Security event on the code already shipped -- a CVE in a dependency, a secret committed to the repo, a license question, an advisory: triage reachability and severity, contain in order, and never close a leaked secret before its rotation is observed. Use when the user says: security-event-response, security event response, cve, triage this cve, cve in our dependency, cve in a dependency, security advisory, dependabot alert.
What it loads into context
Frontmatter
208 tokensAlways available to the agent
SKILL.md
2,171 tokensWhen the skill is activated
Reference documents
889 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,129 bytesreferences/event-containment-order.mddoc4,001 bytes
Read SKILL.md
# Security Event Response
This is a Hermes-native `security-event-response` workflow skill.
## Why This Exists
`security-event-response` exists because an event had no owner: `security-safety-review` and `application-threat-model` review a design before it ships, and a CVE, a committed secret, or a license question was answered by onboarding, review, or an achievements lane with no containment order at all.
## First Steps
- Classify the event and state its exposure window before proposing any step.
- For a leaked secret, order the rotation and its observed rejection before any history rewrite.
## Do Not Use WhenView the complete source on GitHubomh-security-safety-review
When your agent uses it
[omh] Agent or automation safety risks: review prompt, tool, secret, dependency, destructive-action, and explicit local plugin risks before agent or code execution. Use when the user says: security-safety-review, security safety review, ai coding safety, agent safety review, prompt injection review, tool permission review, secret exposure review, destructive action review.
What it loads into context
Frontmatter
180 tokensAlways available to the agent
SKILL.md
2,376 tokensWhen the skill is activated
Reference documents
959 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,273 bytesSKILL.mdcore11,273 bytesSKILL.mdcore11,273 bytesSKILL.mdcore11,273 bytesSKILL.mdcore11,273 bytesSKILL.mdcore11,273 bytesreferences/credential-rotation.mddoc4,478 bytes
Read SKILL.md
# Security Safety Review
This is a Hermes-native `security-safety-review` workflow skill.
## Why This Exists
`security-safety-review` adapts ECC's AgentShield and safety-review posture into OMH as a review-first gate for agentic coding and operator workflows without adding hidden scanners or external dependencies.
## Do Not Use When
- The user asks for production readiness across release, rollback, and observability; use `omh-production-audit`.
- The user asks for merge verification commands; use `omh-verification-gate`.
- The user asks for a normal code review focused on bugs; use `omh-code-review`.
- The subject is an application or service rather than the agent's own runtime -- its assets, trust boundaries, attack scenarios, and the controls that defend them; use `omh-application-threat-model`.View the complete source on GitHubomh-show-reel
When your agent uses it
[omh] Video to make from an idea or a product: an explainer, motion graphics, kinetic type, a logo intro, a 3D scene, a data-viz animation, a music visual, a short or a source-grounded product film, authored and rendered to a measured MP4 with locale/export QA and source delivery. Use when the user says: show-reel, show reel, showreel, product showcase video, animated product film, motion showcase, animated portfolio, launch film.
What it loads into context
Frontmatter
219 tokensAlways available to the agent
SKILL.md
2,437 tokensWhen the skill is activated
Reference documents
75,328 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Idea Videos
- Production Method
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/assets/engine/engine.jstoolkit/assets/engine/fx.jstoolkit/assets/engine/scenes.jstoolkit/scripts/codex_ref_image.shtoolkit/scripts/contact_sheet.pytoolkit/scripts/eleven.pytoolkit/scripts/finish.pytoolkit/scripts/font-coverage.mjstoolkit/scripts/mix.pytoolkit/scripts/motion_check.pytoolkit/scripts/music_tools.pytoolkit/scripts/narrate.pytoolkit/scripts/new_project.pytoolkit/scripts/preflight.pytoolkit/scripts/prep_images.pytoolkit/scripts/qa_check.pytoolkit/scripts/render.mjstoolkit/scripts/synth_music.pytoolkit/scripts/timeline.py
Files
SKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesSKILL.mdcore11,307 bytesreferences/art-direction.mddoc7,072 bytesreferences/assets-and-rights.mddoc1,951 bytesreferences/audio-production.mddoc4,148 bytesreferences/brief-and-locales.mddoc4,777 bytesreferences/craft-audio.mddoc19,081 bytesreferences/craft-brief.mddoc11,954 bytesreferences/craft-design.mddoc16,126 bytesreferences/craft-engine.mddoc26,944 bytesreferences/craft-images.mddoc8,927 bytesreferences/craft-qa.mddoc13,246 bytesreferences/craft-story.mddoc20,827 bytesreferences/craft-techniques-2.mddoc15,525 bytesreferences/craft-techniques.mddoc23,127 bytesreferences/craft-workflow.mddoc31,631 bytesreferences/full-contract.mddoc6,187 bytesreferences/game-capture.mddoc1,882 bytesreferences/genres.mddoc4,860 bytesreferences/kinetic-type.mddoc6,861 bytesreferences/launch-film.mddoc5,548 bytesreferences/motion-techniques.mddoc2,797 bytesreferences/procedure.mddoc17,387 bytesreferences/render-qa-delivery.mddoc8,525 bytesreferences/renderer-adapter.mddoc9,675 bytesreferences/source-package.mddoc1,469 bytesreferences/storyboard-and-evidence.mddoc5,451 bytestoolkit/LICENSE.upstreamasset1,081 bytestoolkit/README.mddoc18,809 bytestoolkit/assets/engine/engine.jsruns22,130 bytestoolkit/assets/engine/fx.jsruns21,400 bytestoolkit/assets/engine/index.htmlasset3,042 bytestoolkit/assets/engine/scenes.jsruns12,968 bytestoolkit/assets/sfx_presets.jsonasset3,425 bytestoolkit/examples/README.mddoc744 bytestoolkit/examples/music-spec.jsonasset372 bytestoolkit/examples/timing.jsonasset146 bytestoolkit/scripts/codex_ref_image.shruns2,625 bytestoolkit/scripts/contact_sheet.pyruns8,901 bytestoolkit/scripts/eleven.pyruns19,967 bytestoolkit/scripts/finish.pyruns8,152 bytestoolkit/scripts/font-coverage.mjsruns2,862 bytestoolkit/scripts/mix.pyruns9,761 bytestoolkit/scripts/motion_check.pyruns11,588 bytestoolkit/scripts/music_tools.pyruns30,110 bytestoolkit/scripts/narrate.pyruns12,785 bytestoolkit/scripts/new_project.pyruns10,728 bytestoolkit/scripts/preflight.pyruns5,777 bytestoolkit/scripts/prep_images.pyruns5,902 bytestoolkit/scripts/qa_check.pyruns7,307 bytestoolkit/scripts/render.mjsruns22,638 bytestoolkit/scripts/synth_music.pyruns6,597 bytestoolkit/scripts/timeline.pyruns16,476 bytestoolkit/scripts/tools/cutout.swiftasset1,801 bytestoolkit/upstream-manifest.jsonasset20,711 bytes
Read SKILL.md
# Show Reel
## Why This Exists
`show-reel` owns the motion-production method for every authored video, from a 20-second idea explainer to a product film, so factual claims, visual decisions, locale timing, revision budget, measured exports, and delivery receipts cannot drift apart. It does not render inside OMH core.
## First Steps
- Pick the lane first. A video from an idea with no product claim, real UI or brand asset on screen takes the idea lane in `## Idea Videos` below; a product, launch, brand or work film, or any product fact on screen, takes the full method.
- Read `references/brief-and-locales.md` and `references/storyboard-and-evidence.md` before proposing visuals. Recover objective, audience, channel, duration, aspect ratio, fps, size cap, source/brand permissions, and tool availability from supplied context; honor explicit format and duration, ask only for irretrievable hard facts, and label reversible creative assumptions. A shot of a UI that exists is drawn from that product's own renderer output, never a look-alike, and every product fact on screen is copied from its canonical source and cited.
- Resolve content language from current explicit user/audience/channel instructions, then applicable stable preferences, then user language. Keep reply_language under host persona and separate content_locale, onscreen_text, subtitle_text, pronunciation_text, voice_policy, font_policy, and direction_policy; never replace literal IDs, commands, URLs, or trademarks.
- For a product, brand or work film, compare at least 3 genuinely distinct concept candidates before selection; record the rubric, winner, rejected alternatives, and per-segment art direction. Read `references/craft-workflow.md` (the full upstream production method), `toolkit/README.md` under the loaded skill directory with a file reader, then `references/renderer-adapter.md` before choosing tools; a missing renderer means HOLD on a requested video, not a completed delivery.
- If the reel is captured from a game or simulation instead of authored from static assets, read `references/game-capture.md` before capture and timeline authoring: run the simulate → capture → timeline.json → finish edit pipeline with `timeline.json` as the single source of truth for events, SFX cues and titles, pin and record the source game data version/build, map every gameplay event that needs SFX to a cue in timeline.json (an unmapped event is HOLD), apply the shorts defaults (1080x1920, black letterbox bars, centered white title, fade-in, tuned BGM start offset) only as brief-overridable defaults, and record voice provenance (source clip URL, sha256, excerpt range) for any real voice — never synthesizing an impersonation of a real voice actor or person and labeling timbre-alike or synthetic voice methods honestly in credits, with performer/IP permissions handled in the existing assets-and-rights flow.
- If the selected concept is kinetic typography for a hype launch or teaser, read `references/kinetic-type.md` before beat-sheet and scene authoring; this opt-in lane never applies to explainers or evidence films.View the complete source on GitHubomh-skill
When your agent uses it
[omh] Installing, removing, or editing skills: managing local skills. Use when the user says: skill, skills, manage skills.
What it loads into context
Frontmatter
127 tokensAlways available to the agent
SKILL.md
1,491 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,667 bytesSKILL.mdcore6,667 bytes
Read SKILL.md
# Skill
This is a Hermes-native `skill` workflow skill.
## Why This Exists
`skill` exists to route listing, reading, searching, installing, and editing skills to Hermes' own skill tools and commands, and to keep OMH-managed skills, whose bodies OMH generates, out of hand edits.
## Do Not Use When
- The user wants an OMH capability family turned on or off; use `omh-capability-toggle`.
- The user wants a public skill found and vetted before installing it; use `omh-skill-scout`.
- The user wants skill health checked: stale surfaces, failure patterns, or pending amendments; use `omh-skill-health`.
- The user is writing or editing a skill that ships in the hermes-agent repository itself rather than a local one; load Hermes' bundled `hermes-agent-skill-authoring` skill instead of this one.View the complete source on GitHubomh-skill-health
When your agent uses it
[omh] OMH skill portfolio health overview: prepare a metadata-only OMH skill portfolio dashboard with stale surfaces, observed failure signals, pending amendments, and top actions. Use when the user says: skill-health, skill health, skill portfolio health, skill dashboard, skill health dashboard, skill failure pattern dashboard, skill failure patterns, pending skill amendments.
What it loads into context
Frontmatter
163 tokensAlways available to the agent
SKILL.md
1,790 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,448 bytesSKILL.mdcore8,448 bytesSKILL.mdcore8,448 bytes
Read SKILL.md
# Skill Health
This is a Hermes-native `skill-health` workflow skill.
## Why This Exists
`skill-health` exists because a skill portfolio drifts in ways no single run shows -- a managed skill changed in place, an authoring finding nobody fixed, an update waiting on its hub -- and use counts measure none of that: it gathers the observed signals into one card with an owner lane and a safe next action for each, and changes nothing itself.
## Do Not Use When
- OMH setup, install, or a skill that does not load; use `omh-doctor`.
- One run that missed a route or went wrong; use `omh-workflow-learning`.
- Finding a new skill to adopt; use `omh-skill-scout`.
View the complete source on GitHubomh-skill-scout
When your agent uses it
[omh] Existing skills to reuse before authoring: prepare a metadata-only search-before-creation report for local, marketplace, GitHub, and web skill candidates with risk review and adoption options. Use when the user says: skill-scout, skill scout, skill candidate, skill candidate search, skill discovery, find a skill, find skills, top skills.
What it loads into context
Frontmatter
165 tokensAlways available to the agent
SKILL.md
1,848 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,445 bytesSKILL.mdcore8,445 bytesSKILL.mdcore8,445 bytesSKILL.mdcore8,445 bytesSKILL.mdcore8,445 bytes
Read SKILL.md
# Skill Scout
This is a Hermes-native `skill-scout` workflow skill.
## Why This Exists
`skill-scout` exists because writing a skill that already exists, or adopting a public one on its popularity, both cost more than a search: it compares installed, bundled, and public candidates first, keeps each source's trust level and any scan verdict beside it, and recommends using, extending, or creating one without installing, copying, or trusting anything.
## Do Not Use When
- Repairing an OMH install or a skill that does not load; use `omh-doctor`.
- A health overview of the skills already installed; use `omh-skill-health`.
- Writing or changing a skill once the scout decision is made; use `omh-skill`.
View the complete source on GitHubomh-source-finder
When your agent uses it
[omh] Gathering candidate papers, datasets, or repos: source candidate inventory - prepare typed source candidates and acquisition status before downstream work; use ulw-research to fetch and cite them, or research-brief to turn them into a decision-ready brief. Use when the user says: source-finder, source finder, source acquisition, source intake, find papers and datasets, find datasets and repos, find papers, find arxiv link.
What it loads into context
Frontmatter
208 tokensAlways available to the agent
SKILL.md
2,002 tokensWhen the skill is activated
Reference documents
14,912 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesSKILL.mdcore9,530 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Source Finder
This is a Hermes-native `source-finder` workflow skill.
## Why This Exists
`source-finder` exists so Hermes can turn vague source discovery requests into typed candidates, acquisition status, and downstream workflow choice without pretending OMH searched, downloaded, or verified the material.
## First Steps
- Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubomh-spend-gate
When your agent uses it
[omh] Spending money on the user's behalf -- a card checkout, an HTTP 402 or pay-per-request call, a wallet transfer, a booking, a paid data endpoint: show a pre-spend card (payee, total with fees, cap, refund terms, approver) first, and call it done only on an observed receipt. Use when the user says: spend-gate, spend gate, pre-spend, pre-spend card, spend cap, spending cap, spend limit, spending limit.
What it loads into context
Frontmatter
207 tokensAlways available to the agent
SKILL.md
3,024 tokensWhen the skill is activated
Reference documents
1,142 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,948 bytesSKILL.mdcore12,948 bytesSKILL.mdcore12,948 bytesreferences/spend-rails.mddoc5,101 bytes
Read SKILL.md
# Spend Gate
This is a Hermes-native `spend-gate` workflow skill.
## Why This Exists
`spend-gate` exists because money movement had at most one native guard, on one rail: where Hermes' saved-card fill is present it asks before filling a card and refuses when nobody can confirm, while an HTTP 402 call, a wallet transfer, a booking, or a paid data endpoint had no pre-spend check, no receipt rule, and no cap. `omh-browser` gates payment only inside a page, and `omh-provider-profile-posture` claims no payment at all.
## First Steps
- Check that a person can answer in this session; in a scheduled, webhook, API-server, single-query, background-worker, or subagent run, prepare the card and stop before any payment surface.
- Read the quote from its source and fill the pre-spend card from it, the cap included, before anything is submitted.
## Do Not Use WhenView the complete source on GitHubomh-sprite-forge
When your agent uses it
[omh] Character art to animate in a game: turn image-model sprite sheets into aligned, QC-gated frames with a fail-closed Pillow helper. Use when the user says: sprite-forge, sprite sheet, pixel sprite, pixel art character, game sprite frames, 2d sprite animation, 도트 캐릭터, 스프라이트 시트.
What it loads into context
Frontmatter
169 tokensAlways available to the agent
SKILL.md
1,299 tokensWhen the skill is activated
Reference documents
3,913 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Safety Rules
- When to Use
- Catalog Metadata
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Runtime Evidence
Scripts executed separately
toolkit/scripts/forge.py
Files
SKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesSKILL.mdcore5,895 bytesreferences/character-art-direction.mddoc1,554 bytesreferences/execution-and-qa.mddoc2,293 bytesreferences/full-contract.mddoc3,123 bytesreferences/procedure.mddoc3,867 bytestoolkit/LICENSE.upstreamasset1,316 bytestoolkit/README.mddoc5,698 bytestoolkit/examples/layout.jsonasset357 bytestoolkit/scripts/forge.pyruns18,182 bytestoolkit/upstream-manifest.jsonasset2,559 bytes
Read SKILL.md
# Sprite Forge
Required: grid sheet from the host image tool on flat #FF00FF, declared rows x cols, cell size and feet baseline, new output directory and execution budget. Output: aligned equal-size frames and sheet, sprite_forge_qc/v1 receipt, character art-direction record.
**HOLD:** Missing inputs or failed contract gates. Prepared OMH routing is not execution or approval.
## Why This Exists
Image models return character poses at drifting scales and offsets, so frames cut by hand jitter in play. This skill couples a grid-sheet contract to a fail-closed processor whose numeric QC decides whether to regenerate the source.
## First Steps
- Read `toolkit/README.md` and `references/execution-and-qa.md` before executing `toolkit/scripts/forge.py`; installation and skill discovery never run it.
- Obtain the raw sheet from the host's own image tool as a grid on flat #FF00FF; OMH generates no images, and a 1xN strip is regenerated as a grid, never processed.View the complete source on GitHubomh-support-operations
When your agent uses it
[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
What it loads into context
Frontmatter
176 tokensAlways available to the agent
SKILL.md
1,579 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,456 bytesSKILL.mdcore7,456 bytesSKILL.mdcore7,456 bytes
Read SKILL.md
# Support Operations
This is a Hermes-native `support-operations` workflow skill.
## Why This Exists
`support-operations` turns a bounded customer case into response and escalation guidance without treating drafts or recommendations as helpdesk actions.
## Do Not Use When
- The request clusters a backlog of customer signals to find product patterns or roadmap candidates; use `omh-feedback-triage`.
- The user only needs a generic, non-support marketing or email rewrite with no case, severity, or escalation context; use `omh-content-operator`.
- The request asks to send a reply, change ticket priority or status, issue a refund, modify an account, or update a helpdesk; use `omh-apps` with an explicit target and observed result.
- The request is an incident that is still open, needing severity declared, a commander assigned, and a running timeline rather than a support-case response; use `omh-live-incident-response`.View the complete source on GitHubomh-systematic-review
When your agent uses it
[omh] Literature screening against frozen criteria: two blind reviewers, a deterministic merge, open conflicts and agreement for systematic, scoping or rapid reviews. Use when the user says: systematic-review, systematic review, systematic literature review, scoping review, rapid review, prisma screening, title and abstract screening, inclusion and exclusion criteria screening.
What it loads into context
Frontmatter
159 tokensAlways available to the agent
SKILL.md
1,759 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,288 bytes
Read SKILL.md
# Systematic Review
This is a Hermes-native `systematic-review` workflow skill.
## Why This Exists
Two reviewers screening the same records only count as dual review when neither sees the other's answers and the merge is mechanical. This workflow freezes the criteria first, keeps each reviewer blind, and never turns a missing answer into an exclusion.
## First Steps
- Agree the inclusion and exclusion criteria and the ordered exclusion codes with the person before any record is read; nothing is frozen until they say the criteria are final.
- Call `omh research screening freeze --criteria FILE --codes FILE --out DIR`. The protocol is write-once: a criteria change after freeze means a new DIR, never an edited protocol.json.
- Call `omh research screening prepare --dir DIR --records FILE --seed N`, then read DIR/manifest.json for the batch list.
- When `delegate_task` is in your tool list or tool_search finds it, dispatch two children, A and B: give each only its own `DIR/tasks/<A|B>/` files and tell it to write answer lines to `DIR/answers/<A|B>/`. Never pass one child the other's tasks, answers or name; without the tool, ask the person to run the two reviewers separately.View the complete source on GitHubomh-tech-debt-audit
When your agent uses it
[omh] Accumulated tech debt or architecture deepening to rank: build the severity-by-effort debt ledger from observed repo evidence - orient, audit the named dimensions with file:line citations, rank fixes and quick wins - and reconcile RESOLVED/NEW/CARRIED on rerun. Use when the user says: tech-debt-audit, tech debt, tech debt audit, technical debt, technical debt audit, tech debt ledger, debt ledger, audit our tech debt.
What it loads into context
Frontmatter
203 tokensAlways available to the agent
SKILL.md
2,080 tokensWhen the skill is activated
Reference documents
2,244 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,335 bytesSKILL.mdcore9,335 bytesreferences/architecture-deepening.mddoc5,598 bytesreferences/debt-dimensions.mddoc4,180 bytes
Read SKILL.md
# Tech Debt Audit
This is a Hermes-native `tech-debt-audit` workflow skill.
## Why This Exists
`tech-debt-audit` exists so accumulated debt becomes a ranked, reconcilable ledger instead of a one-off complaint: findings cite file:line, severity and effort make the trade-off explicit, quick wins are separated from big fixes, and reruns mark what was resolved instead of rediscovering it.
## Do Not Use When
- The target is one diff, PR, or claim rather than the codebase's accumulated state; use `omh-code-review`.
- The user wants the debt removed now, behavior preserved; use `omh-ai-slop-cleaner` for deletion-first cleanup.
- A boundary-changing fix from the ledger needs its execution shaped into phases; use `omh-refactor-plan`.
- The question is release risk for a specific deploy rather than source quality; use `omh-production-audit`.View the complete source on GitHubomh-terminal
When your agent uses it
[omh] Shell command or test-suite execution: policy overlay for terminal commands - add cwd, environment, safety, and result-evidence gates after preferring native shell tools for ordinary CLI, package-manager, and test runs. Use when the user says: command-operator, command operator, terminal command, terminal task, shell command, shell task, cli command, command execution.
What it loads into context
Frontmatter
170 tokensAlways available to the agent
SKILL.md
2,303 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,951 bytesSKILL.mdcore10,951 bytes
Read SKILL.md
# Command Operator
This is a Hermes-native `command-operator` workflow skill.
## Why This Exists
`command-operator` exists because a host's own approval gate flags only some commands and can approve one with nobody asked: it fixes the working directory, environment, timeout, and stop condition, confirms every irreversible or externally visible command in chat whether or not the host flags it, records the host's own approval answer beside that confirmation, and reports results only from what the run returned.
## Do Not Use When
- An ordinary read-only or test command with a known working directory and nothing to gate; run it with the native terminal tool.
- The user pasted a failed command's output and asks for the cause; use `omh-build-failure-triage`, or `omh-agent-debug` when the agent itself is stuck.
- The user wants a command blocked for the agent from now on; use `omh-security-safety-review`, which prepares a proposed deny-glob list for the user to apply.
View the complete source on GitHubomh-todo-checklist
When your agent uses it
[omh] Resume or finish the work we agreed on: continue or finish the accepted work from conversation context, preserve rejected ideas, and report evidence-bounded completion. Also declare and advance the metadata-only plan checklist without starting a delivery engine. Use when the user says: todo-checklist, plan checklist, todo checklist, phase checklist, declare a plan checklist, declare the plan todo, show the plan todo, clear the plan todo.
What it loads into context
Frontmatter
176 tokensAlways available to the agent
SKILL.md
1,783 tokensWhen the skill is activated
Reference documents
4,805 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore8,242 bytesSKILL.mdcore8,242 bytesreferences/checklist-discipline.mddoc7,376 bytesreferences/closing-a-story.mddoc9,877 bytesreferences/requirements-quality-checklist.mddoc3,993 bytes
Read SKILL.md
# Todo Checklist
This is a Hermes-native `todo-checklist` workflow skill.
## Why This Exists
`todo-checklist` exists because `omh_todo` is registered on every session while nothing in the skill surface named it: a user who wanted a plan checklist searched for one and found no skill on the subject. The delivery engines declare a checklist as part of starting work, which serves someone running an engine and nobody else.
## Do Not Use When
- The work is one step, already finished, or answerable in this turn; a checklist that never advances is a panel of noise.
- The user wants an accepted implementation plan split into parallel lanes with owners and verification commands; use `ulw-work`.
- The user wants the planning content itself -- options, risks, acceptance criteria before execution; use `ulw-plan`.
- The user is asking what coding work is running right now rather than what the plan says; use `omh-running-work-board`.View the complete source on GitHubomh-toolbelt-readiness
When your agent uses it
[omh] Which tools and credentials a workflow needs: inventory which MCP servers, CLIs, APIs, credentials, and connectors a workflow needs; use external-connector-readiness to assess one named integration and executor-runtime-readiness to choose the coding owner. Use when the user says: toolbelt-readiness, mcp readiness, tool readiness, plugin readiness, connector readiness, needed mcp, api credential, missing cli.
What it loads into context
Frontmatter
178 tokensAlways available to the agent
SKILL.md
1,569 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,357 bytesSKILL.mdcore7,357 bytes
Read SKILL.md
# Toolbelt Readiness
This is a Hermes-native `toolbelt-readiness` workflow skill.
## Why This Exists
`toolbelt-readiness` exists so the tools, CLIs, credentials, and connectors a workflow needs are listed as present, missing, optional, or unsafe before the work starts, instead of failing midway on a tool nobody checked.
## Do Not Use When
- One named integration needs assessing end to end before adoption; use `omh-external-connector-readiness`.
- The question is which coding owner should run the work; use `omh-executor-runtime-readiness`.
- The user wants a tool installed, a credential validated, or a connector called now; the card names that step and who runs it, and performs none of them.
View the complete source on GitHubomh-verification-gate
When your agent uses it
[omh] Proof a change is done before merge: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge. Use when the user says: verification-gate, verification gate, quality gate, release gate, test gate, build lint test, lint typecheck tests, verify before merge.
What it loads into context
Frontmatter
166 tokensAlways available to the agent
SKILL.md
3,000 tokensWhen the skill is activated
Reference documents
4,991 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore13,789 bytesSKILL.mdcore13,789 bytesSKILL.mdcore13,789 bytesSKILL.mdcore13,789 bytesSKILL.mdcore13,789 bytesreferences/adaptation-quality.mddoc6,358 bytesreferences/generated-artifact-provenance.mddoc3,336 bytesreferences/requirement-coverage-map.mddoc5,761 bytesreferences/test-authoring.mddoc7,956 bytes
Read SKILL.md
# Verification Gate
This is a Hermes-native `verification-gate` workflow skill.
## Why This Exists
`verification-gate` gives OMH a deterministic evidence surface before done/merge claims, inspired by ECC-style gates but rebuilt around OMH's prepared-versus-observed contract.
## Do Not Use When
- The user asks for visual render QA; use `omh-visual-qa`.
- The user asks for production release readiness beyond verification commands; use `omh-production-audit`.
- The user wants a bug-first code review of a diff; use `omh-code-review`.
View the complete source on GitHubomh-visual-qa
When your agent uses it
[omh] Rendered UI needing a visual verdict: prepare observed-only rendered QA gates for web, frontend, image, document, and TUI surfaces. Use when the user says: visual-qa, visual qa, visual QA, visual quality assurance, visual check, web qa, web visual qa, screenshot qa.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
4,088 tokensWhen the skill is activated
Reference documents
2,414 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore18,548 bytesSKILL.mdcore18,548 bytesSKILL.mdcore18,548 bytesSKILL.mdcore18,548 bytesSKILL.mdcore18,548 bytesreferences/motion-continuity.mddoc3,138 bytesreferences/playable-check.mddoc2,121 bytesreferences/visual-verdict-contract.mddoc4,898 bytes
Read SKILL.md
# Visual Qa
This is a Hermes-native `visual-qa` workflow skill.
## Why This Exists
`visual-qa` gives OMH a completion gate for rendered surfaces so layout breaks, AI-looking polish gaps, CJK text problems, and mismatched-lineage screenshot claims cannot be mistaken for verified quality.
## Do Not Use When
- The user needs initial frontend design or redesign planning before implementation; use `omh-frontend`.
- The user needs a broad visual quality rubric before generation; use `omh-design-quality-gate`.
- The user needs image-card prompt creation; use `omh-image-cards`.
- The user wants non-visual code tests, CI, or PR review only; use the coding/review workflow.View the complete source on GitHubomh-voice-input
When your agent uses it
[omh] Dictated voice note about project work or status: terse voice and mobile-style requests - turn short spoken-style asks into clarify, plan, status, handoff, or confirmation actions. Use when the user says: voice-operator, voice operator, voice-first, voice command, mobile command, short command, dictated command, dictated request.
What it loads into context
Frontmatter
139 tokensAlways available to the agent
SKILL.md
1,441 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore6,814 bytesSKILL.mdcore6,814 bytes
Read SKILL.md
# Voice Operator
This is a Hermes-native `voice-operator` workflow skill.
## Why This Exists
`voice-operator` exists so Hermes users can ask for this workflow in chat and get a structured, checkable answer instead of an improvised one.
## Do Not Use When
- The request is already handled by a narrower explicit skill with stronger evidence.
- The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents.
- The only safe answer is to ask for missing authority, credentials, target, or observed evidence first.
View the complete source on GitHubomh-web-research
When your agent uses it
[omh] Current technical or business fact to cite from web: web lookup lane - settle a current-facts question in one cited retrieval round with retrieval dates and source-quality notes; for pre-spec grounding across reference implementations use `research`. Use when the user says: web-research, web research, web search, search the web, internet search, look up, look up sources, latest sources.
What it loads into context
Frontmatter
201 tokensAlways available to the agent
SKILL.md
2,682 tokensWhen the skill is activated
Reference documents
14,912 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesSKILL.mdcore12,382 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Web Research
This is a Hermes-native `web-research` workflow skill.
## Why This Exists
`web-research` exists so a current-facts question returns a cited answer in one retrieval round, without the declared depth budget, reference-implementation study, and dossier that `research` requires.
## First Steps
- Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubomh-websearch-setup
When your agent uses it
[omh] Expensive or unconfigured web search: diagnose which search and extract providers, provider tiers, and keyless free tier Hermes reads, guide provider account setup, and apply each change as its own diff approval. Use when the user says: websearch-setup, web search setup, make web search cheaper, set up web search, configure web search, reduce web search cost, connect scraper api key, web search backend.
What it loads into context
Frontmatter
163 tokensAlways available to the agent
SKILL.md
2,291 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore10,636 bytesSKILL.mdcore10,636 bytes
Read SKILL.md
# Websearch Setup
This is a Hermes-native `websearch-setup` workflow skill.
## Why This Exists
`websearch-setup` exists to make web search cost and backend choice configurable through two clearly separated, diff-approved steps against the `web` keys Hermes reads, instead of one opaque edit.
## Do Not Use When
- The user wants Hermes to run a web search now, not configure how web search is set up.
- No provider key, backend, or tier intent has been named yet.
- The request needs a repository code change rather than a local `.env` or Hermes config edit.
View the complete source on GitHubomh-wiki
When your agent uses it
[omh] Scattered knowledge needing a wiki: wiki construction blueprints and retained knowledge capture with destination-aware external knowledge connection guidance. Use when the user says: wiki, project wiki, build a wiki, start a wiki, organize my notes, external knowledge store, knowledge base, Obsidian.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
1,922 tokensWhen the skill is activated
Reference documents
5,447 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Design Interview
- Closing A Long Piece Of Work
- Boundary
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,202 bytesSKILL.mdcore9,202 bytesSKILL.mdcore9,202 bytesSKILL.mdcore9,202 bytesSKILL.mdcore9,202 bytesreferences/handover-artifacts.mddoc10,029 bytesreferences/wiki-blueprint.mddoc2,337 bytesreferences/wiki-ecosystem.mddoc3,695 bytesreferences/wiki-operations.mddoc4,269 bytesreferences/wiki-patterns.mddoc4,056 bytes
Read SKILL.md
# Wiki
This is a Hermes-native `wiki` workflow skill.
## Why This Exists
`wiki` exists to keep `knowledge` 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.
- The user wants the agent to ingest sources into, query, or lint an interlinked markdown knowledge base it maintains itself in the Karpathy LLM Wiki pattern; load Hermes' bundled `llm-wiki` skill instead of this one.
View the complete source on GitHubomh-workflow-learning
When your agent uses it
[omh] Missed route or run lessons to record: classify and review self-improvement store routes as an auxiliary review lane before durable writes, then record workflow attempts as metadata-only traces, evals, review queues, patch proposals, regression cases, audits, indexes, and exports. Use when the user says: workflow-learning, workflow learning, route-signal, self-improvement store routing, store route review, memory skill wiki routing, learning trace, learning audit.
What it loads into context
Frontmatter
186 tokensAlways available to the agent
SKILL.md
2,110 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,713 bytesSKILL.mdcore9,713 bytes
Read SKILL.md
# Workflow Learning
This is a Hermes-native `workflow-learning` workflow skill.
## Why This Exists
`workflow-learning` exists because a lesson from a run can land in the wrong store or in none, and Hermes' own background review can write skills and memory after a turn with no OMH review: it routes each lesson to memory, skill, wiki, failure-retrospective, or automation review as metadata-only records, and checks what Hermes wrote on its own against what was reviewed.
## Do Not Use When
- A lasting fact the user wants kept; capture it with `omh-memory-new`.
- Lessons seen across runs or projects to score and promote; use `omh-instinct-ledger`.
- A run that is stuck or looping right now; use `omh-agent-debug`.
View the complete source on GitHubomh-workspace-audit
When your agent uses it
[omh] Workspace setup inventory and gaps: map repository, skill, prompt, plugin, MCP, hook, config, and runtime surfaces before strengthening or operating OMH. Use when the user says: workspace-audit, workspace audit, repo surface audit, repository surface audit, workspace surface audit, repo inventory, surface inventory, skill inventory.
What it loads into context
Frontmatter
161 tokensAlways available to the agent
SKILL.md
1,690 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore7,945 bytesSKILL.mdcore7,945 bytesSKILL.mdcore7,945 bytes
Read SKILL.md
# Workspace Audit
This is a Hermes-native `workspace-audit` workflow skill.
## Why This Exists
`workspace-audit` gives OMH an ECC-inspired but OMH-native front door for understanding a large agent workspace before strengthening it, without turning inventory into hidden mutation or runtime proof.
## Do Not Use When
- The user already named a concrete implementation task with files and acceptance criteria; use the coding handoff or delivery workflow.
- The request is local OMH installation health only; use `omh-doctor`.
- The request is a source acquisition or current web lookup; use `omh-source-finder` or `ulw-research`.
View the complete source on GitHubulw-context
When your agent uses it
[omh] Repository vocabulary unclear or inconsistent: project terminology alignment workflow: look up, capture, correct, and align the words a repository uses before planning or handoff. Use when the user says: ulw-context, project terminology alignment, review project terms, align project terminology, terminology this project uses.
What it loads into context
Frontmatter
165 tokensAlways available to the agent
SKILL.md
2,735 tokensWhen the skill is activated
Reference documents
1,096 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Workflow Protocol
- Runtime Evidence
Files
SKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesSKILL.mdcore14,125 bytesreferences/decision-frontier.mddoc3,503 bytesreferences/project-terms.mddoc1,925 bytes
Read SKILL.md
# Context
This is a Hermes-native `context` workflow skill.
## Why This Exists
`context` exists to reduce repository terminology drift without creating a second machine store or a vocabulary router: Hermes can answer lookups, facilitate dependency-aware alignment, and project approved results into existing review and handoff boundaries.
## Do Not Use When
- A safe one-term definition or source lookup can be answered directly; use the read-only lookup mode and do not enter the full context interview.
- The request is broad ambiguity with no project-language conflict; use `ulw-interview`.
- The unresolved decision is empirical and a cheap isolated experiment can answer it; use `omh-decision-prototype` and keep the frontier for the rest.
- The terminology is already agreed and the request is to produce an implementation plan; use `ulw-plan`.View the complete source on GitHubulw-interview
When your agent uses it
[omh] Vague, underspecified request: one-question-at-a-time clarification. Use when the user says: deep-interview, interview me, clarify, feature shaping, ambiguous product request, one question, 要件を詰めて, 曖昧な要求.
What it loads into context
Frontmatter
141 tokensAlways available to the agent
SKILL.md
2,711 tokensWhen the skill is activated
Reference documents
1,013 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- Interview Round Protocol
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore12,333 bytesSKILL.mdcore12,333 bytesreferences/ambiguity-taxonomy.mddoc4,860 bytes
Read SKILL.md
# Deep Interview
This is a Hermes-native `deep-interview` workflow skill.
## Why This Exists
`deep-interview` exists to stop Hermes from guessing through ambiguous product, workflow, or implementation intent; it converts uncertainty into a clarified brief before planning or handoff.
## Do Not Use When
- The request already has concrete scope, acceptance criteria, and verification commands.
- The missing information is discoverable from the repository or local artifacts without asking the user.
- The user asked for immediate read-only analysis and the ambiguity does not change the answer.
- The ambiguity is specifically repository terminology or project-language alignment; use `ulw-context` and its direct-lookup/frontier boundary.View the complete source on GitHubulw-loop
When your agent uses it
[omh] Ambitious project goal needing many build cycles: agentic interviewer -> planner -> researcher -> builder -> reviewer cycles until a real gate. Use when the user says: loop, goal loop, long horizon goal, never stop, research plan goal feedback, token exhaustion resume, permission profile, star 10k.
What it loads into context
Frontmatter
152 tokensAlways available to the agent
SKILL.md
4,925 tokensWhen the skill is activated
Reference documents
7,012 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Goal Driver Ownership
- Constraint Discipline
- Measured Loops
- Runtime Evidence
Files
SKILL.mdcore23,735 bytesSKILL.mdcore23,735 bytesreferences/board-iteration.mddoc6,332 bytesreferences/goal-constraint-discipline.mddoc5,024 bytesreferences/loop-design-review.mddoc15,428 bytesreferences/measured-loop-discipline.mddoc5,968 bytes
Read SKILL.md
# Loop
This is a Hermes-native `loop` workflow skill.
## Why This Exists
`loop` exists for goals whose correct implementation cannot be known upfront but can be discovered through bounded cycles of definition, action, verification, and revision without confusing planned cycles with observed progress.
## Do Not Use When
- The user asks for one bounded delivery cycle; use `ulw-work`'s delivery-boundary capability instead.
- Scope and milestones are already known and only durable checkpoint/resume tracking is needed; use `ulw-work`'s durable-checkpoint capability.
- The user gives only a north-star outcome such as revenue, stars, or adoption and has not accepted a bounded first loop goal.
- The goal is too vague to name an observable problem, next artifact, verification signal, or stop condition.View the complete source on GitHubulw-maestro
When your agent uses it
[omh] Coding owner already chosen, handoff pending: prepares the handoff for the coding agent you already chose, composing its prompt from that agent's own installed skills; never selects the owner and never executes the work itself. Use when the user says: ulw-maestro, coding handoff, prepare the handoff, prepare a coding handoff, hand off the coding work, external executor handoff, handoff prompt, delegation prompt.
What it loads into context
Frontmatter
189 tokensAlways available to the agent
SKILL.md
5,042 tokensWhen the skill is activated
Reference documents
1,571 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore23,264 bytesSKILL.mdcore23,264 bytesreferences/executor-prompt-composition.mddoc7,199 bytes
Read SKILL.md
# Maestro
This is a Hermes-native `maestro` workflow skill.
## Why This Exists
`maestro` exists so a handoff to an already-chosen external coding CLI carries that CLI's own installed skills, a stated dispatchability boundary, and a captured session id instead of a guessed prompt; absent an explicit coding-owner choice, work runs inside the Hermes harness and no external coding CLI is selected, and this engine only loads once that explicit choice is already made.
## Do Not Use When
- No coding owner is chosen yet for this run; the Hermes harness stays the default and this engine never picks one.
- The request is a concept question about maestro, prepared handoffs, or a coding-agent name, or a filename that happens to contain one -- answer directly instead.
- The user wants advice on which coding owner to pick -- ask, don't compose.
- The user is asking whether an owner CAN run right now -- use `omh-executor-runtime-readiness` instead.View the complete source on GitHubulw-perf
When your agent uses it
[omh] Software slowness, memory leaks, or cost spikes: find where a system is actually slow, leaking, or expensive across runtime, memory, token cost, storage, rendering, inference, CI, and query domains, then fix one measured hot path at a time behind a regression budget. Use when the user says: ultraperf, ulw-perf, performance audit, performance bottleneck, find the bottleneck, profile the hot path, memory leak investigation, token cost hotspot.
What it loads into context
Frontmatter
187 tokensAlways available to the agent
SKILL.md
2,059 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore9,690 bytesSKILL.mdcore9,690 bytes
Read SKILL.md
# Ultraperf
This is a Hermes-native `ultraperf` workflow skill.
## Why This Exists
`ultraperf` exists because most performance work starts unlocalized: something is slow, leaking, or expensive and nobody knows where. It forces measurement before edits, one hypothesis at a time, executor-owned changes, and a regression budget, so an optimization loop cannot end in unverified claims.
## Do Not Use When
- The ask is to judge code quality, structure, or correctness rather than measured cost; use `omh-code-review`.
- The ask is to score model or agent output quality on a task suite; use `omh-agent-evaluation`.
- The request is a settings-only change, one bounded edit that is explicitly low-risk and has a direct owner and verification path, or one already-identified slow query or hotspot fix; handle it directly instead of opening a performance loop.
View the complete source on GitHubulw-plan
When your agent uses it
[omh] High-stakes technical proposal needing approval: consensus planning with review gates. Use when the user says: ralplan, consensus plan, reviewed plan, issue to PR, acceptance criteria, verification command, reviewable PR, risky planning.
What it loads into context
Frontmatter
157 tokensAlways available to the agent
SKILL.md
3,346 tokensWhen the skill is activated
Reference documents
0 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytesSKILL.mdcore15,819 bytes
Read SKILL.md
# Ralplan
This is a Hermes-native `ralplan` workflow skill.
## Why This Exists
`ralplan` exists to make planning reviewable before execution: Hermes should gather codebase/source facts, compare options, expose risks, define acceptance criteria, and prepare a handoff without pretending implementation already happened.
## First Steps
- Initialize the plan todo before the first planning step: declare the planning stages as `omh_todo` items (todo init), never also in `todo_list` — repo facts and evidence check, options and tradeoffs, risk review, acceptance criteria and verification commands, plan record and acceptance — keep exactly one item active, and when the evidence check reveals a gap rewrite the list (`omh_todo` action=set) to insert the research stage; update the list as stages complete so the HUD todo panel shows plan progress as a bounded checklist, and treat items as declarations, never execution evidence. Phase names and task titles are written in English — short, operator-legible labels — even when the conversation runs in another language, since the HUD todo checklist is an operator surface under the repo's English-by-default output contract.
## Do Not Use When
View the complete source on GitHubulw-qa
When your agent uses it
[omh] Hostile scenario testing: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.
What it loads into context
Frontmatter
142 tokensAlways available to the agent
SKILL.md
2,414 tokensWhen the skill is activated
Reference documents
3,445 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore11,155 bytesSKILL.mdcore11,155 bytesreferences/board-fanin.mddoc7,336 bytesreferences/manual-test-guide.mddoc7,817 bytes
Read SKILL.md
# Ultraqa
This is a Hermes-native `ultraqa` workflow skill.
## Why This Exists
`ultraqa` exists because behavior that passes its own tests can still fail under inputs and conditions nobody wrote down: it turns the changed behavior and known risks into hostile scenarios, records each one's observed pass or fail apart from any proposed fix, and hands fixes to the selected coding executor.
## Do Not Use When
- Exploratory bug-hunting across a web app with no changed behavior to attack; on Hermes, use the bundled `dogfood` skill when it is available, and bring a finding back here as a scenario to reproduce.
- Judging whether a rendered page, image, or terminal frame looks right across viewports and states; use `omh-visual-qa`.
- Confirming that a finished change meets its acceptance criteria with the smallest proving check, when no hostile scenarios are wanted; use `omh-verification-gate`.
View the complete source on GitHubulw-research
When your agent uses it
[omh] Deep dive before a decision: deep research engine - grounding for specs and decisions: study open-source reference implementations with pinned refs, gather live web evidence with citation discipline, verify contested claims, and distill a decision-grounding dossier that planning consumes; for a decision brief use research-brief, for upstream guidance use web-research. Use when the user says: research plan, literature review, research literature, review recent papers, deep research, deep-research, exhaustive research, saturation research.
What it loads into context
Frontmatter
213 tokensAlways available to the agent
SKILL.md
4,284 tokensWhen the skill is activated
Reference documents
18,251 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Runtime Evidence
Files
SKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesSKILL.mdcore20,803 bytesreferences/briefing-format.mddoc6,885 bytesreferences/evidence-records.mddoc8,668 bytesreferences/search-examples.mddoc26,353 bytesreferences/search-fields.mddoc25,430 bytesreferences/search-method.mddoc8,223 bytes
Read SKILL.md
# Research
This is a Hermes-native `research` workflow skill.
## Why This Exists
`research` exists to make Hermes a careful research engine: it routes research demands to source-backed evidence gathering - from live web citations to studied reference implementations - verifies contested claims, and distills decision-grounding output so planning starts from evidence instead of guesses.
## First Steps
- When Hermes' bundled `grounded-citations` skill is available, set the citation ledger up before the first retrieval: choose one run-private file, have the parent reset it once (`sources.py --ledger <path> reset`), and declare parent-only writes in every lane brief. No lane resets it. Discover the current search/read tools and authorized scope, then follow `references/search-method.md`: plan -> actual host search/read -> merge -> assess -> bounded retry. Use `omh_search` only when available; otherwise report the skill-only fallback. Keep direct file lookups direct.
## Do Not Use When
View the complete source on GitHubulw-work
When your agent uses it
[omh] Accepted plan awaiting implementation: split it into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.
What it loads into context
Frontmatter
162 tokensAlways available to the agent
SKILL.md
5,640 tokensWhen the skill is activated
Reference documents
13,192 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Why This Exists
- First Steps
- Do Not Use When
- Examples
- Completion Checklist
- Recovery Notes
- Workflow Lane
- When to Use
- Catalog Metadata
- Tests-First Delivery
- Runtime Evidence
Files
SKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesSKILL.mdcore27,245 bytesreferences/campaign-orchestrator.mddoc10,384 bytesreferences/dependency-topology.mddoc4,474 bytesreferences/execution-rulings.mddoc8,741 bytesreferences/file-ownership-manifest.mddoc5,089 bytesreferences/kanban-lane.mddoc13,517 bytesreferences/native-delegation.mddoc5,453 bytesreferences/tdd-red-green.mddoc6,542 bytesreferences/team-lane.mddoc5,887 bytes
Read SKILL.md
# Ultrawork
This is a Hermes-native `ultrawork` workflow skill.
## Why This Exists
`ultrawork` exists to choose one-owner, ordered-dependency, or independent-frontier execution for an accepted implementation plan without letting concurrency blur ownership, verification, worker protocol, worktree isolation, or observed runtime evidence. It also carries four named internal capabilities absorbed from sibling engines: `coordinated_scope` (coordinated worker lanes), `delivery_boundary` (one bounded plan-to-PR cycle), `single_owner_persistence` (one owner finishes and verifies), and `durable_checkpoint` (durable goal ledger with checkpoints and a final gate).
## First Steps
- Initialize the phase todo before engine work (todo init) in ONE tool, never both: `todo_list` when `todo_list` is in your tool list or tool_search finds it (OMH mirrors it), else `omh_todo`; an accepted plan stays in `omh_todo`. Declare numbered phases in delivery order — bootstrap, one implement/verify/deliver task per lane or work unit, independent review lanes, and an evidence-and-cleanup close, one task per observable outcome — keep exactly one item active, and update states as lanes complete, so the run walks a bounded checklist. Phase names and task titles are written in English as short labels even when the conversation runs in another language, since the HUD checklist is an operator surface.
## Do Not Use When
View the complete source on GitHubSkills included
- omh-accessibility-audit
- omh-adversarial-consensus
- omh-agent-debug
- omh-agent-instructions
- omh-agent-ops-review
- omh-ai-job-search
- omh-ai-slop-cleaner
- omh-app-debugging
- omh-apple-design
- omh-application-threat-model
- omh-apps
- omh-ask
- omh-award-bar-score
- omh-backend
- omh-biomedical-evidence
- omh-build-failure-triage
- omh-cancel
- omh-code-review
- omh-codebase-onboarding
- omh-codebase-uml
- omh-codegraph-refresh
- omh-commit-pr-authoring
- omh-content-operator
- omh-context-budget-review
- omh-cto-loop
- omh-curriculum-design
- omh-data-analysis
- omh-data-pipelines
- omh-data-share-review
- omh-decide
- omh-decision-prototype
- omh-decision-recall
- omh-deliverable-package
- omh-deploy-and-monitor
- omh-design-orchestration
- omh-design-quality-gate
- omh-docs
- omh-external-connector-readiness
- omh-failure-signal-audit
- omh-feedback-triage
- omh-files
- omh-finance-analysis
- omh-frontend
- omh-frontend-refactor
- omh-geospatial-analysis
- omh-git-workflow
- omh-github-event-ops
- omh-github-issue-intake
- omh-harness-session-inventory
- omh-iac-change
- omh-idea-to-deploy
- omh-image-cards
- omh-inference-serving
- omh-instinct-ledger
- omh-internal-audit
- omh-jit-learn
- omh-legal-compliance-review
- omh-lifecycle-growth
- omh-live-incident-response
- omh-live-info
- omh-llm-app-dev
- omh-localization-review
- omh-market-research
- omh-materials-package
- omh-media-input
- omh-meeting-brief
- omh-memory-new
- omh-mobile-release
- omh-model-finetuning
- omh-molecular-docking
- omh-native-debugging
- omh-operating-rhythm
- omh-ops-observability-card
- omh-ops-review
- omh-paper-learning
- omh-people-ops
- omh-physical-device-readiness
- omh-plan
- omh-product-brief
- omh-product-discovery-validation
- omh-production-audit
- omh-provider-profile-posture
- omh-refactor-plan
- omh-relational-db
- omh-release-cut
- omh-reliability-review
- omh-report-package
- omh-repro-audit
- omh-research-brief
- omh-rules-distill
- omh-run-efficiency
- omh-running-work-board
- omh-rust
- omh-sales-development
- omh-sales-pipeline-review
- omh-security-event-response
- omh-security-safety-review
- omh-show-reel
- omh-skill-health
- omh-skill-scout
- omh-source-finder
- omh-spend-gate
- omh-sprite-forge
- omh-support-operations
- omh-systematic-review
- omh-tech-debt-audit
- omh-terminal
- omh-toolbelt-readiness
- omh-verification-gate
- omh-visual-qa
- omh-voice-input
- omh-web-research
- omh-wiki
- omh-workspace-audit
- ulw-context
- ulw-interview
- ulw-loop
- ulw-perf
- ulw-plan
- ulw-qa
- ulw-research
- ulw-work
- dag-ulw
- omh-accessibility-audit
- omh-achievements
- omh-adversarial-consensus
- omh-agent-board
- omh-agent-debug
- omh-agent-evaluation
- omh-agent-instructions
- omh-agent-ops-review
- omh-ai-job-search
- omh-ai-slop-cleaner
- omh-app-debugging
- omh-apple-design
- omh-application-threat-model
- omh-apps
- omh-ask
- omh-automation-blueprint
- omh-award-bar-score
- omh-backend
- omh-biomedical-evidence
- omh-browser
- omh-build-failure-triage
- omh-buzz
- omh-cancel
- omh-capability-toggle
- omh-code-review
- omh-codebase-onboarding
- omh-codebase-uml
- omh-codegraph-refresh
- omh-commit-pr-authoring
- omh-content-operator
- omh-context-budget-review
- omh-cto-loop
- omh-curriculum-design
- omh-data-analysis
- omh-data-pipelines
- omh-data-share-review
- omh-decide
- omh-decision-prototype
- omh-decision-recall
- omh-deliverable-package
- omh-deploy-and-monitor
- omh-design-orchestration
- omh-design-quality-gate
- omh-docs
- omh-doctor
- omh-executor-runtime-readiness
- omh-external-connector-readiness
- omh-failure-signal-audit
- omh-feedback-triage
- omh-files
- omh-finance-analysis
- omh-frontend
- omh-frontend-refactor
- omh-gateway-intent-card
- omh-geospatial-analysis
- omh-git-workflow
- omh-github-event-ops
- omh-github-issue-intake
- omh-harness-session-inventory
- omh-iac-change
- omh-idea-to-deploy
- omh-image-cards
- omh-inference-serving
- omh-instinct-ledger
- omh-internal-audit
- omh-jev-action-check
- omh-jev-ask
- omh-jev-done-check
- omh-jev-failure-triage
- omh-jev-review-gate
- omh-jev-route
- omh-jit-learn
- omh-legal-compliance-review
- omh-lifecycle-growth
- omh-live-incident-response
- omh-live-info
- omh-llm-app-dev
- omh-localization-review
- omh-long-document-reading
- omh-market-research
- omh-materials-package
- omh-media-input
- omh-meeting-brief
- omh-memory-new
- omh-memory-sync
- omh-meta-router
- omh-mobile-release
- omh-model-finetuning
- omh-model-optimization
- omh-model-setup
- omh-molecular-docking
- omh-morning-brief
- omh-native-debugging
- omh-operating-rhythm
- omh-ops-observability-card
- omh-ops-review
- omh-paper-learning
- omh-parallel-tools
- omh-people-ops
- omh-physical-device-readiness
- omh-plan
- omh-product-brief
- omh-product-discovery-validation
- omh-production-audit
- omh-prompt-import-readiness
- omh-provider-profile-posture
- omh-refactor-plan
- omh-relational-db
- omh-release-cut
- omh-reliability-review
- omh-report-package
- omh-repro-audit
- omh-research-brief
- omh-research-department
- omh-routing
- omh-rules-distill
- omh-run-efficiency
- omh-running-work-board
- omh-rust
- omh-sales-development
- omh-sales-pipeline-review
- omh-security-event-response
- omh-security-safety-review
- omh-show-reel
- omh-skill
- omh-skill-health
- omh-skill-scout
- omh-source-finder
- omh-spend-gate
- omh-sprite-forge
- omh-support-operations
- omh-systematic-review
- omh-tech-debt-audit
- omh-terminal
- omh-todo-checklist
- omh-toolbelt-readiness
- omh-verification-gate
- omh-visual-qa
- omh-voice-input
- omh-web-research
- omh-websearch-setup
- omh-wiki
- omh-workflow-learning
- omh-workspace-audit
- ulw-context
- ulw-interview
- ulw-loop
- ulw-maestro
- ulw-perf
- ulw-plan
- ulw-qa
- ulw-research
- ulw-work
Repository facts
- License
- MIT
- Created
- Jun 3, 2026
- Last pushed
- Nov 7, 2026
- Forks
- 414
- Open issues
- 12
- Project activity
- Active
Rank over the last 12 weeks
Now #277 · best #273 · up 45 in 30 days
- #275 on Oct 28
- #273 from Oct 29 to Nov 2
- #274 from Nov 3 to Nov 4
- #278 on Nov 5
- #275 on Nov 6
- #277 since Nov 7
77 earlier periods
- #811 on Aug 2
- #673 on Aug 8
- #641 on Aug 9
- #649 on Aug 10
- #653 on Aug 11
- #623 on Aug 12
- #621 on Aug 13
- #592 on Aug 14
- #575 on Aug 15
- #583 on Aug 16
- #581 on Aug 17
- #591 on Aug 18
- #573 on Aug 19
- #570 on Aug 20
- #566 on Aug 21
- #546 on Aug 22
- #561 on Aug 23
- #558 on Aug 24
- #557 on Aug 25
- #543 on Aug 26
- #531 on Aug 27
- #529 on Aug 28
- #509 on Aug 29
- #498 on Aug 30
- #522 from Aug 31 to Sep 1
- #515 on Sep 2
- #514 on Sep 3
- #489 on Sep 4
- #480 on Sep 5
- #487 on Sep 6
- #482 on Sep 7
- #491 on Sep 8
- #482 on Sep 9
- #478 on Sep 10
- #469 on Sep 11
- #462 on Sep 12
- #452 on Sep 13
- #409 on Sep 14
- #395 on Sep 15
- #370 on Sep 16
- #352 on Sep 17
- #350 on Sep 18
- #341 on Sep 19
- #347 on Sep 20
- #345 on Sep 21
- #347 on Sep 22
- #340 on Sep 23
- #334 on Sep 24
- #330 on Sep 25
- #324 on Sep 26
- #332 on Sep 27
- #333 on Sep 28
- #338 on Sep 29
- #333 on Sep 30
- #331 on Oct 1
- #334 on Oct 2
- #325 on Oct 3
- #319 on Oct 4
- #321 on Oct 5
- #318 on Oct 6
- #321 on Oct 7
- #322 on Oct 8
- #327 on Oct 9
- #320 on Oct 10
- #319 on Oct 11
- #325 on Oct 12
- #326 from Oct 13 to Oct 14
- #324 on Oct 15
- #327 on Oct 16
- #323 on Oct 17
- #327 on Oct 18
- #329 on Oct 19
- #325 on Oct 20
- #324 from Oct 21 to Oct 22
- #322 on Oct 23
- #294 on Oct 24
- #291 on Oct 25
Before you install
Network or broad shellAutomated signals, not a guarantee
Checked Nov 6, 2026
Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.
Show 812 notes
agent-skills/omh-accessibility-audit/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-agent-ops-review/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-ai-job-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-ai-job-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-ai-job-search/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-apple-design/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-apple-design/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-ask/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-ask/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzedagent-skills/omh-biomedical-evidence/SKILL.md:1Analysis incomplete: Referenced executable target unavailable; not analyzed
- No broad tool permissions
- 3 dangerous shell commandsin 3 files: omh-terminal/SKILL.md:38 omh-jev-action-check/references/full-contract.md:21 omh-terminal/SKILL.md:40
- 370 network referencesin 62 files: omh-biomedical-evidence/toolkit/upstream-manifest.json:1 omh-molecular-docking/toolkit/upstream-manifest.json:53 omh-biomedical-evidence/toolkit/upstream-manifest.json:1 and 59 more
- 6 obfuscation signalsin 6 files: omh-show-reel/toolkit/scripts/eleven.py:165 omh-show-reel/toolkit/scripts/new_project.py:54 omh-sprite-forge/toolkit/scripts/forge.py:123 and 3 more
- 6 instruction override signalsin 6 files: omh-ai-slop-cleaner/SKILL.md:108 omh-executor-runtime-readiness/SKILL.md:97 omh-frontend-refactor/SKILL.md:102 and 3 more
- 48 executable scriptsin 48 files: omh-ai-job-search/toolkit/scripts/job_state.py:1 omh-biomedical-evidence/toolkit/scripts/reconcile.py:1 omh-geospatial-analysis/toolkit/scripts/analyze.py:1 and 45 more
- 52 references to secretsin 21 files: omh-show-reel/toolkit/scripts/eleven.py:4 omh-show-reel/toolkit/scripts/eleven.py:4 omh-show-reel/toolkit/scripts/narrate.py:3 and 18 more
- No requests to vote in Hot
Show all 485 signals by file
agent-skills/omh-ai-job-search/toolkit/examples/synthetic-captures.json
- Network accessline 5
"source_namespace": "careers.example.invalid", "posting_id": "REQ-101", "original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", - Network accessline 6
"posting_id": "REQ-101", "original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", "canonical_url": "https://careers.example.invalid/jobs?req=REQ-101#details", - Network accessline 7
"original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", - Network accessline 8
"canonical_url": "https://careers.example.invalid/jobs?req=REQ-101#details", - Network accessline 32
"receipt_id": "synthetic-blocked-1", "kind": "search", "source_url": "https://search.example.invalid/", - Network accessline 33
"kind": "search", "source_url": "https://search.example.invalid/", "retrieved_at": "2026-10-23T02:01:00Z", - Network accessline 34
"source_url": "https://search.example.invalid/",
agent-skills/omh-ai-job-search/toolkit/scripts/job_state.py
- Executable scriptline 1
#!/usr/bin/env python3
agent-skills/omh-ai-job-search/toolkit/upstream-manifest.json
- Network accessline 37
], "relationship": "Conceptual adaptation of shared-contract inspected identity, bounded-state and explicit-outcome methods; original implementation, no executable code port. MIT notice retained. Crawler, numeric ranking, HTML sanitiz - Network accessline 38
"relationship": "Conceptual adaptation of shared-contract inspected identity, bounded-state and explicit-outcome methods; original implementation, no executable code port. MIT notice retained. Crawler, numeric ranking, HTML sanitizer, Claud - Network accessline 39
"repository": "https://github.com/ai-job-search-dev/ai-job-search", - Network accessline 46
], "relationship": "Shared-contract inspected source-aware discovery and qualitative-fit concepts inform the host workflow; no plugin/provider code copied or executed, no dependency.", "repository": "https://github.com/agent-dat - Network accessline 47
"relationship": "Shared-contract inspected source-aware discovery and qualitative-fit concepts inform the host workflow; no plugin/provider code copied or executed, no dependency.", "repository": "https://github.com/agent-data/job-sea - Network accessline 48
"repository": "https://github.com/agent-data/job-search", - Network accessline 54
], "relationship": "Inspected community catalog pointer only; no copied runtime code, installation, mandatory provider or plugin integration claim.", "repository": "https://github.com/NousResearch/hermes-agent", - Network accessline 55
"relationship": "Inspected community catalog pointer only; no copied runtime code, installation, mandatory provider or plugin integration claim.", "repository": "https://github.com/NousResearch/hermes-agent", "revision": "bf0203 - Network accessline 56
"repository": "https://github.com/NousResearch/hermes-agent",
agent-skills/omh-apple-design/references/materials-and-accessibility.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/materials - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/tutorials/data/design/human-interface-guidelines/materials.json - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass.md - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/accessibility - Network accessline 9
- Web standard, accessed 2026-09-05: https://www.w3.org/WAI/standards-guidelines/wcag/
agent-skills/omh-apple-design/references/platform-foundations.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/ - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-ios - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-macos - Network accessline 9
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/tutorials/data/design/human-interface-guidelines/typography.json - Network accessline 10
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/sf-symbols/ - Network accessline 11
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/fonts/
agent-skills/omh-apple-design/references/product-visual-production.md
- Network accessline 8
- Apple MacBook Pro, accessed 2026-09-05: https://www.apple.com/macbook-pro/ - Network accessline 9
— metal edge light, dark studio, and silhouette-led framing. - Apple AirPods Pro, accessed 2026-09-05: https://www.apple.com/airpods-pro/ — macro scale, white ceramic/plastic reading, and restrained negative space. - Network accessline 10
- Apple AirPods Pro, accessed 2026-09-05: https://www.apple.com/airpods-pro/ - Network accessline 11
— macro scale, white ceramic/plastic reading, and restrained negative space. - Apple Vision Pro, accessed 2026-09-05: https://www.apple.com/apple-vision-pro/ — glass, physical depth, and controlled reflection. - Network accessline 12
- Apple Vision Pro, accessed 2026-09-05: https://www.apple.com/apple-vision-pro/ - Network accessline 13
— glass, physical depth, and controlled reflection. - Apple HIG Motion, Materials, and App icons, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/motion, - Network accessline 14
- Apple HIG Motion, Materials, and App icons, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/motion, https://developer.apple.com/design/human-interface-guidelines/materials, and - Network accessline 15
https://developer.apple.com/design/human-interface-guidelines/motion, - Network accessline 16
https://developer.apple.com/design/human-interface-guidelines/materials, and - Network accessline 17
https://developer.apple.com/design/human-interface-guidelines/app-icons - Network accessline 18
- Apple Icon Composer, accessed 2026-09-05: https://developer.apple.com/icon-composer/ — a multilayer native icon-asset pipeline, not a marketing renderer. - Network accessline 19
https://developer.apple.com/icon-composer/ — a multilayer native icon-asset
agent-skills/omh-apple-design/references/review-playbook.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/ - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/color - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/layout - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/typography
agent-skills/omh-apple-design/references/web-production-libraries.md
- Network accessline 13
- GSAP, reviewed at `13e2b790546426a1a2e0e9b409f3f8dc6d6611f2` on 2026-09-05: https://github.com/greensock/gsap — framework-agnostic animation with - Network accessline 14
https://github.com/greensock/gsap — framework-agnostic animation with - Network accessline 17
it an OSI license or assume every plugin has the same distribution posture. - liquid-logo, reviewed at `689bb38a1e0d5a6a8baf2d34847635eefde19994` on 2026-09-05: https://github.com/paper-design/liquid-logo — a private Next - Network accessline 18
- liquid-logo, reviewed at `689bb38a1e0d5a6a8baf2d34847635eefde19994` on 2026-09-05: https://github.com/paper-design/liquid-logo — a private Next application under PolyForm Shield 1.0.0, not an npm package or reusable - Network accessline 19
2026-09-05: https://github.com/paper-design/liquid-logo — a private Next - Network accessline 24
refraction, liquid amount, and speed. - liquid-glass-js, reviewed at `78cb6ccb0b9987bb60a88b14ccbd13a9e6e8ab2a` on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed - Network accessline 25
- liquid-glass-js, reviewed at `78cb6ccb0b9987bb60a88b14ccbd13a9e6e8ab2a` on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed standalone browser files with `Container` and `Button` WebGL classes and an - Network accessline 26
on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed
agent-skills/omh-biomedical-evidence/toolkit/scripts/reconcile.py
- Executable scriptline 1
#!/usr/bin/env python3
agent-skills/omh-biomedical-evidence/toolkit/upstream-manifest.json
- Network accessline 1
{ "schema": "omh_biomedical_evidence_provenance/v1", "repository": "https://github.com/genomoncology/biomcp", - Network accessline 2
"schema": "omh_biomedical_evidence_provenance/v1", "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 3
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 7
"source_audit": [ { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 8
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 9
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 14
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 15
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 16
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 21
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 22
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 23
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 28
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 29
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 30
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 35
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 36
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 37
"repository": "https://github.com/genomoncology/biomcp",
agent-skills/omh-external-connector-readiness/SKILL.md
- Access to secretsline 67
[Credential-related source omitted]
agent-skills/omh-frontend/references/chart-styling.md
- Network accessline 101
- Bklit theming - https://bklit.com/docs/theming - license: check before - Network accessline 102
adopting - shadcn/ui charts and theming - https://ui.shadcn.com/docs/theming - MIT (repository license) - Network accessline 103
- shadcn/ui charts and theming - https://ui.shadcn.com/docs/theming - MIT - Network accessline 104
(repository license) - MUI X Charts styling - https://mui.com/x/react-charts/styling/ - the community `@mui/x-charts` package is MIT (package license file) - Network accessline 105
- MUI X Charts styling - https://mui.com/x/react-charts/styling/ - the
agent-skills/omh-frontend/references/component-registry-adoption.md
- Network accessline 151
- shadcn/ui - https://ui.shadcn.com/docs/theming - MIT (repository license) - Network accessline 152
- Magic UI marquee - https://magicui.design/docs/components/marquee - MIT - Network accessline 153
(repository license) - React Bits SplitText - https://reactbits.dev/text-animations/split-text - MIT with the Commons Clause condition (repository license file); not an OSI - Network accessline 154
- React Bits SplitText - https://reactbits.dev/text-animations/split-text - - Network accessline 155
MIT with the Commons Clause condition (repository license file); not an OSI license - Neobrutalism components - https://www.neobrutalism.com/docs - MIT - Network accessline 156
license - Neobrutalism components - https://www.neobrutalism.com/docs - MIT (repository license) - Network accessline 157
- Neobrutalism components - https://www.neobrutalism.com/docs - MIT - Network accessline 158
(repository license) - Animate UI - https://animate-ui.com/docs - license: check before adopting - SmoothUI - https://smoothui.dev - license: check before adopting - Network accessline 159
- Animate UI - https://animate-ui.com/docs - license: check before adopting - Network accessline 160
- SmoothUI - https://smoothui.dev - license: check before adopting - Network accessline 161
- Aceternity UI - https://ui.aceternity.com - license: check before adopting - Network accessline 162
- Cult UI - https://www.cult-ui.com - MIT as stated on its site - Network accessline 163
- Kokonut UI - https://kokonutui.com - license: check before adopting - Network accessline 164
- Vengeance UI - https://www.vengenceui.com - license: check before adopting - Network accessline 165
- Skiper UI - https://skiper-ui.com - license: check before adopting
agent-skills/omh-frontend/references/scroll-motion-libraries.md
agent-skills/omh-geospatial-analysis/toolkit/scripts/analyze.py
- Executable scriptline 1
#!/usr/bin/env python3
agent-skills/omh-geospatial-analysis/toolkit/upstream-manifest.json
agent-skills/omh-inference-serving/references/serving-runbooks.md
- Access to secretsline 28
[Credential-related source omitted] - Network accessline 43
4. **Verify** with `kubectl rollout status` plus pod readiness - the runbook's only completion evidence. 5. **Summarize**: table of what exists, then a port-forward and one curl smoke - Network accessline 44
only completion evidence. 5. **Summarize**: table of what exists, then a port-forward and one curl smoke request against `/v1/models`. - Network accessline 45
5. **Summarize**: table of what exists, then a port-forward and one curl smoke
agent-skills/omh-molecular-docking/toolkit/scripts/dock.py
- Executable scriptline 1
#!/usr/bin/env python3
agent-skills/omh-molecular-docking/toolkit/upstream-manifest.json
- Network accessline 53
"license": "Apache-2.0", "path": "src/tooluniverse/tools/NvidiaNIM_diffdock.py", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 54
"path": "src/tooluniverse/tools/NvidiaNIM_diffdock.py", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 55
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 61
"license": "Apache-2.0", "path": "src/tooluniverse/tools/ClusPro_submit_peptide_docking.py", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 62
"path": "src/tooluniverse/tools/ClusPro_submit_peptide_docking.py", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 63
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 69
"license": "Apache-2.0", "path": "src/tooluniverse/data/remote_tools/boltz_tools.json", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 70
"path": "src/tooluniverse/data/remote_tools/boltz_tools.json", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 71
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 77
"license": "Apache-2.0", "path": "docs/source/docking_python.rst", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 78
"path": "docs/source/docking_python.rst", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 79
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 85
"license": "Apache-2.0", "path": "example/python_scripting/1iep_receptor.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 86
"path": "example/python_scripting/1iep_receptor.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 87
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 93
"license": "Apache-2.0", "path": "example/python_scripting/1iep_ligand.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 94
"path": "example/python_scripting/1iep_ligand.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 95
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina",
agent-skills/omh-show-reel/references/audio-production.md
- Access to secretsline 7
[Credential-related source omitted]
agent-skills/omh-show-reel/references/craft-audio.md
- Network accessline 19
1. Sign up or log in at https://elevenlabs.io -> bottom left Developers (or the profile) -> API Keys -> Create API Key - Access to secretsline 21
[Credential-related source omitted] - Access to secretsline 49
[Credential-related source omitted] - Network accessline 209
| Symptom | Cause and fix | | --- | --- | | `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl | - Network accessline 210
| --- | --- | | `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl | | The mp3 does not play ("Failed to find two consecutive MPEG audio frames - Network accessline 211
| `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl |
agent-skills/omh-show-reel/references/craft-brief.md
- Network accessline 145
Research <subject> and write it to <project>/research/research.md. Do not rely on memory; write only facts confirmed with WebSearch and WebFetch. (For sites where WebFetch is blocked, fetch with curl -sL -A "Mozilla/5.0" and extract the bod - Network accessline 146
(For sites where WebFetch is blocked, fetch with curl -sL -A "Mozilla/5.0" and extract the body text.) - Network accessline 164
Keep all working files inside the <project> folder. Do not use /tmp. - Priority: official profile, company press releases > press article photos (og:image) > the person's public social media - Fetch the Naver News search result HTML with cu - Network accessline 165
- Priority: official profile, company press releases > press article photos (og:image) > the person's public social media - Fetch the Naver News search result HTML with curl to extract article URLs, then fetch the og:image from the article - Network accessline 166
- Fetch the Naver News search result HTML with curl to extract article URLs, then fetch the og:image from the article HTML (set a browser UA and Referer)
agent-skills/omh-show-reel/references/craft-workflow.md
- Network accessline 79
- **When the codex CLI or the image skills are missing**: the codex-image, photoreal, and codex-cli skills are at https://github.com/revfactory/skills . Guide the user through the printed install command. If they are not installed, build wi
agent-skills/omh-show-reel/references/kinetic-type.md
- Network accessline 107
Method notes informed by Scenario's Kinetic Film exploration (https://www.scenario.com/explorations/kinetic-film/,
agent-skills/omh-show-reel/references/launch-film.md
- Network accessline 86
Method notes informed by a public frame-by-frame study of a 99 s product launch film (DeepSeek Harness Creator Mode, https://x.com/DeepSeekHarness/status/2117256196227019194, - Network accessline 87
film (DeepSeek Harness Creator Mode, https://x.com/DeepSeekHarness/status/2117256196227019194,
agent-skills/omh-show-reel/toolkit/README.md
agent-skills/omh-show-reel/toolkit/assets/engine/engine.js
agent-skills/omh-show-reel/toolkit/assets/engine/fx.js
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/assets/engine/scenes.js
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/codex_ref_image.sh
- Executable scriptline 1
#!/usr/bin/env bash
agent-skills/omh-show-reel/toolkit/scripts/contact_sheet.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/eleven.py
- Executable scriptline 1
Executable file - Network accessline 3
# scripts/eleven.py: OPT-IN provider client, run only by a user who invokes it with their own # key. The key comes from ELEVENLABS_API_KEY in the environment only (no .env, home or config # lookup) and reaches curl on stdin, never argv or l - Network accessline 4
[Credential-related source omitted] - Access to secretsline 4
[Credential-related source omitted] - Network accessline 5
# lookup) and reaches curl on stdin, never argv or logs. No default voice or language: the - Network accessline 6
# caller names both. curl runs with -q (no ~/.curlrc) and --form-string for values. Messages in English; - Access to secretsline 12
[Credential-related source omitted] - Network accessline 14
Why curl: python.org builds of Python often fail TLS verification with urllib because of their certificate store. Verification stays on; curl follows the system certificates and proxy settings. - Network accessline 15
certificate store. Verification stays on; curl follows the system certificates and proxy settings. - Network accessline 41
API = "https://api.elevenlabs.io" - Network accessline 47
KEY_HELP = """This opt-in tool needs your own ElevenLabs API key in the environment: 1) Sign in at https://elevenlabs.io -> Developers (or profile) -> API Keys -> Create API Key. - Network accessline 48
1) Sign in at https://elevenlabs.io -> Developers (or profile) -> API Keys -> Create API Key. - Access to secretsline 51
[Credential-related source omitted] - Access to secretsline 62
[Credential-related source omitted] - Access to secretsline 63
[Credential-related source omitted] - Network accessline 89
"""Never echo the key: a user's curl config or proxy could put headers on stderr.""" - Access to secretsline 95
[Credential-related source omitted] - Access to secretsline 97
[Credential-related source omitted] - Network accessline 101
if body is not None: cmd += ["-H", "Content-Type: application/json", "--data-binary", json.dumps(body, ensure_ascii=False)] for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file - Network accessline 102
cmd += ["-H", "Content-Type: application/json", "--data-binary", json.dumps(body, ensure_ascii=False)] for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file cmd += ["--form-string", - Network accessline 103
for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file - Possible obfuscationline 165
audio = base64.b64decode(d["audio_base64"]) - Access to secretsline 240
[Credential-related source omitted] - Access to secretsline 241
[Credential-related source omitted]
agent-skills/omh-show-reel/toolkit/scripts/finish.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/font-coverage.mjs
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/mix.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/motion_check.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/music_tools.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/narrate.py
agent-skills/omh-show-reel/toolkit/scripts/new_project.py
agent-skills/omh-show-reel/toolkit/scripts/preflight.py
agent-skills/omh-show-reel/toolkit/scripts/prep_images.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/qa_check.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/render.mjs
- Executable scriptline 1
Executable file - Network accessline 158
if(!req.url.startsWith('/'))throw Error('proxy request refused'); if(req.url==='/favicon.ico'){res.writeHead(204);res.end();return;} const pathname=new URL(req.url,'http://127.0.0.1').pathname; - Network accessline 159
if(req.url==='/favicon.ico'){res.writeHead(204);res.end();return;} const pathname=new URL(req.url,'http://127.0.0.1').pathname; const name=pathname==='/'?page:pathname.slice(1); - Network accessline 160
const pathname=new URL(req.url,'http://127.0.0.1').pathname; - Network accessline 171
await new Promise((resolve,reject)=>{server.once('error',reject);server.listen(0,'127.0.0.1',resolve);}); loopbackPort=server.address().port; const origin=`http://127.0.0.1:${loopbackPort}`; - Network accessline 172
loopbackPort=server.address().port; const origin=`http://127.0.0.1:${loopbackPort}`; launching=puppeteer.launch({executablePath:noLinks(options.browser),headless:true,timeout:Math.min(seconds*1000,30000),protocolTimeout:Math.min(sec - Network accessline 173
const origin=`http://127.0.0.1:${loopbackPort}`;
agent-skills/omh-show-reel/toolkit/scripts/synth_music.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/scripts/timeline.py
- Executable scriptline 1
Executable file
agent-skills/omh-show-reel/toolkit/upstream-manifest.json
- Network accessline 130
"license": "MIT", "local_sha256": "85c27191aef2d08135a665d14e0330f30842bbd90d6e1bd89110cd68b8313de7", "modification_notice": "Opt-in provider client run only by the user: key from ELEVENLABS_API_KEY only (no .env/home/config loo - Network accessline 131
"local_sha256": "85c27191aef2d08135a665d14e0330f30842bbd90d6e1bd89110cd68b8313de7", "modification_notice": "Opt-in provider client run only by the user: key from ELEVENLABS_API_KEY only (no .env/home/config lookup), on curl stdin; no - Network accessline 132
[Credential-related source omitted] - Access to secretsline 132
[Credential-related source omitted] - Access to secretsline 199
[Credential-related source omitted] - Network accessline 425
} }, "repository": "https://github.com/revfactory/showreel", - Network accessline 426
}, "repository": "https://github.com/revfactory/showreel", "revision": "64521220a2f8e91cb9894400c48c15b7f45205d6", - Network accessline 427
"repository": "https://github.com/revfactory/showreel",
agent-skills/omh-source-finder/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
agent-skills/omh-source-finder/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
agent-skills/omh-sprite-forge/toolkit/scripts/forge.py
agent-skills/omh-sprite-forge/toolkit/upstream-manifest.json
agent-skills/omh-terminal/SKILL.md
- Dangerous shell operationline 38
- Prompt: command-operator run rm -rf without cwd, confirmation, or observation gates.
agent-skills/omh-web-research/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
agent-skills/omh-web-research/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
agent-skills/ulw-research/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
agent-skills/ulw-research/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
skills/omh-ai-job-search/toolkit/examples/synthetic-captures.json
- Network accessline 5
"source_namespace": "careers.example.invalid", "posting_id": "REQ-101", "original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", - Network accessline 6
"posting_id": "REQ-101", "original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", "canonical_url": "https://careers.example.invalid/jobs?req=REQ-101#details", - Network accessline 7
"original_url": "https://careers.example.invalid/jobs?req=REQ-101&utm_source=demo#details", - Network accessline 8
"canonical_url": "https://careers.example.invalid/jobs?req=REQ-101#details", - Network accessline 32
"receipt_id": "synthetic-blocked-1", "kind": "search", "source_url": "https://search.example.invalid/", - Network accessline 33
"kind": "search", "source_url": "https://search.example.invalid/", "retrieved_at": "2026-10-23T02:01:00Z", - Network accessline 34
"source_url": "https://search.example.invalid/",
skills/omh-ai-job-search/toolkit/scripts/job_state.py
- Executable scriptline 1
#!/usr/bin/env python3
skills/omh-ai-job-search/toolkit/upstream-manifest.json
- Network accessline 37
], "relationship": "Conceptual adaptation of shared-contract inspected identity, bounded-state and explicit-outcome methods; original implementation, no executable code port. MIT notice retained. Crawler, numeric ranking, HTML sanitiz - Network accessline 38
"relationship": "Conceptual adaptation of shared-contract inspected identity, bounded-state and explicit-outcome methods; original implementation, no executable code port. MIT notice retained. Crawler, numeric ranking, HTML sanitizer, Claud - Network accessline 39
"repository": "https://github.com/ai-job-search-dev/ai-job-search", - Network accessline 46
], "relationship": "Shared-contract inspected source-aware discovery and qualitative-fit concepts inform the host workflow; no plugin/provider code copied or executed, no dependency.", "repository": "https://github.com/agent-dat - Network accessline 47
"relationship": "Shared-contract inspected source-aware discovery and qualitative-fit concepts inform the host workflow; no plugin/provider code copied or executed, no dependency.", "repository": "https://github.com/agent-data/job-sea - Network accessline 48
"repository": "https://github.com/agent-data/job-search", - Network accessline 54
], "relationship": "Inspected community catalog pointer only; no copied runtime code, installation, mandatory provider or plugin integration claim.", "repository": "https://github.com/NousResearch/hermes-agent", - Network accessline 55
"relationship": "Inspected community catalog pointer only; no copied runtime code, installation, mandatory provider or plugin integration claim.", "repository": "https://github.com/NousResearch/hermes-agent", "revision": "bf0203 - Network accessline 56
"repository": "https://github.com/NousResearch/hermes-agent",
skills/omh-ai-slop-cleaner/SKILL.md
- Instruction override signalline 108
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
skills/omh-apple-design/references/materials-and-accessibility.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/materials - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/tutorials/data/design/human-interface-guidelines/materials.json - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/documentation/technologyoverviews/adopting-liquid-glass.md - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/accessibility - Network accessline 9
- Web standard, accessed 2026-09-05: https://www.w3.org/WAI/standards-guidelines/wcag/
skills/omh-apple-design/references/platform-foundations.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/ - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-ios - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-ipados - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/designing-for-macos - Network accessline 9
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/tutorials/data/design/human-interface-guidelines/typography.json - Network accessline 10
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/sf-symbols/ - Network accessline 11
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/fonts/
skills/omh-apple-design/references/product-visual-production.md
- Network accessline 8
- Apple MacBook Pro, accessed 2026-09-05: https://www.apple.com/macbook-pro/ - Network accessline 9
— metal edge light, dark studio, and silhouette-led framing. - Apple AirPods Pro, accessed 2026-09-05: https://www.apple.com/airpods-pro/ — macro scale, white ceramic/plastic reading, and restrained negative space. - Network accessline 10
- Apple AirPods Pro, accessed 2026-09-05: https://www.apple.com/airpods-pro/ - Network accessline 11
— macro scale, white ceramic/plastic reading, and restrained negative space. - Apple Vision Pro, accessed 2026-09-05: https://www.apple.com/apple-vision-pro/ — glass, physical depth, and controlled reflection. - Network accessline 12
- Apple Vision Pro, accessed 2026-09-05: https://www.apple.com/apple-vision-pro/ - Network accessline 13
— glass, physical depth, and controlled reflection. - Apple HIG Motion, Materials, and App icons, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/motion, - Network accessline 14
- Apple HIG Motion, Materials, and App icons, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/motion, https://developer.apple.com/design/human-interface-guidelines/materials, and - Network accessline 15
https://developer.apple.com/design/human-interface-guidelines/motion, - Network accessline 16
https://developer.apple.com/design/human-interface-guidelines/materials, and - Network accessline 17
https://developer.apple.com/design/human-interface-guidelines/app-icons - Network accessline 18
- Apple Icon Composer, accessed 2026-09-05: https://developer.apple.com/icon-composer/ — a multilayer native icon-asset pipeline, not a marketing renderer. - Network accessline 19
https://developer.apple.com/icon-composer/ — a multilayer native icon-asset
skills/omh-apple-design/references/review-playbook.md
- Network accessline 5
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/ - Network accessline 6
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/color - Network accessline 7
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/layout - Network accessline 8
- Apple guidance, accessed 2026-09-05: https://developer.apple.com/design/human-interface-guidelines/typography
skills/omh-apple-design/references/web-production-libraries.md
- Network accessline 13
- GSAP, reviewed at `13e2b790546426a1a2e0e9b409f3f8dc6d6611f2` on 2026-09-05: https://github.com/greensock/gsap — framework-agnostic animation with - Network accessline 14
https://github.com/greensock/gsap — framework-agnostic animation with - Network accessline 17
it an OSI license or assume every plugin has the same distribution posture. - liquid-logo, reviewed at `689bb38a1e0d5a6a8baf2d34847635eefde19994` on 2026-09-05: https://github.com/paper-design/liquid-logo — a private Next - Network accessline 18
- liquid-logo, reviewed at `689bb38a1e0d5a6a8baf2d34847635eefde19994` on 2026-09-05: https://github.com/paper-design/liquid-logo — a private Next application under PolyForm Shield 1.0.0, not an npm package or reusable - Network accessline 19
2026-09-05: https://github.com/paper-design/liquid-logo — a private Next - Network accessline 24
refraction, liquid amount, and speed. - liquid-glass-js, reviewed at `78cb6ccb0b9987bb60a88b14ccbd13a9e6e8ab2a` on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed - Network accessline 25
- liquid-glass-js, reviewed at `78cb6ccb0b9987bb60a88b14ccbd13a9e6e8ab2a` on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed standalone browser files with `Container` and `Button` WebGL classes and an - Network accessline 26
on 2026-09-05: https://github.com/dashersw/liquid-glass-js — MIT-licensed
skills/omh-biomedical-evidence/toolkit/scripts/reconcile.py
- Executable scriptline 1
#!/usr/bin/env python3
skills/omh-biomedical-evidence/toolkit/upstream-manifest.json
- Network accessline 1
{ "schema": "omh_biomedical_evidence_provenance/v1", "repository": "https://github.com/genomoncology/biomcp", - Network accessline 2
"schema": "omh_biomedical_evidence_provenance/v1", "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 3
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 7
"source_audit": [ { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 8
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 9
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 14
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 15
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 16
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 21
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 22
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 23
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 28
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 29
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 30
"repository": "https://github.com/genomoncology/biomcp", - Network accessline 35
}, { "repository": "https://github.com/genomoncology/biomcp", - Network accessline 36
{ "repository": "https://github.com/genomoncology/biomcp", "revision": "a843629fb447750418cf746effe94010b1028a28", - Network accessline 37
"repository": "https://github.com/genomoncology/biomcp",
skills/omh-executor-runtime-readiness/SKILL.md
- Instruction override signalline 97
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
skills/omh-external-connector-readiness/SKILL.md
- Access to secretsline 73
[Credential-related source omitted]
skills/omh-frontend-refactor/SKILL.md
- Instruction override signalline 102
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
skills/omh-frontend/references/chart-styling.md
- Network accessline 101
- Bklit theming - https://bklit.com/docs/theming - license: check before - Network accessline 102
adopting - shadcn/ui charts and theming - https://ui.shadcn.com/docs/theming - MIT (repository license) - Network accessline 103
- shadcn/ui charts and theming - https://ui.shadcn.com/docs/theming - MIT - Network accessline 104
(repository license) - MUI X Charts styling - https://mui.com/x/react-charts/styling/ - the community `@mui/x-charts` package is MIT (package license file) - Network accessline 105
- MUI X Charts styling - https://mui.com/x/react-charts/styling/ - the
skills/omh-frontend/references/component-registry-adoption.md
- Network accessline 151
- shadcn/ui - https://ui.shadcn.com/docs/theming - MIT (repository license) - Network accessline 152
- Magic UI marquee - https://magicui.design/docs/components/marquee - MIT - Network accessline 153
(repository license) - React Bits SplitText - https://reactbits.dev/text-animations/split-text - MIT with the Commons Clause condition (repository license file); not an OSI - Network accessline 154
- React Bits SplitText - https://reactbits.dev/text-animations/split-text - - Network accessline 155
MIT with the Commons Clause condition (repository license file); not an OSI license - Neobrutalism components - https://www.neobrutalism.com/docs - MIT - Network accessline 156
license - Neobrutalism components - https://www.neobrutalism.com/docs - MIT (repository license) - Network accessline 157
- Neobrutalism components - https://www.neobrutalism.com/docs - MIT - Network accessline 158
(repository license) - Animate UI - https://animate-ui.com/docs - license: check before adopting - SmoothUI - https://smoothui.dev - license: check before adopting - Network accessline 159
- Animate UI - https://animate-ui.com/docs - license: check before adopting - Network accessline 160
- SmoothUI - https://smoothui.dev - license: check before adopting - Network accessline 161
- Aceternity UI - https://ui.aceternity.com - license: check before adopting - Network accessline 162
- Cult UI - https://www.cult-ui.com - MIT as stated on its site - Network accessline 163
- Kokonut UI - https://kokonutui.com - license: check before adopting - Network accessline 164
- Vengeance UI - https://www.vengenceui.com - license: check before adopting - Network accessline 165
- Skiper UI - https://skiper-ui.com - license: check before adopting
skills/omh-frontend/references/scroll-motion-libraries.md
skills/omh-geospatial-analysis/toolkit/scripts/analyze.py
- Executable scriptline 1
#!/usr/bin/env python3
skills/omh-geospatial-analysis/toolkit/upstream-manifest.json
skills/omh-inference-serving/references/serving-runbooks.md
- Access to secretsline 28
[Credential-related source omitted] - Network accessline 43
4. **Verify** with `kubectl rollout status` plus pod readiness - the runbook's only completion evidence. 5. **Summarize**: table of what exists, then a port-forward and one curl smoke - Network accessline 44
only completion evidence. 5. **Summarize**: table of what exists, then a port-forward and one curl smoke request against `/v1/models`. - Network accessline 45
5. **Summarize**: table of what exists, then a port-forward and one curl smoke
skills/omh-jev-action-check/references/full-contract.md
- Dangerous shell operationline 21
- Prompt: ask jev if this rm -rf command is safe
skills/omh-long-document-reading/SKILL.md
- Access to secretsline 143
[Credential-related source omitted]
skills/omh-long-document-reading/references/hermes-pdf-limits.md
- Access to secretsline 59
[Credential-related source omitted]
skills/omh-molecular-docking/toolkit/scripts/dock.py
- Executable scriptline 1
#!/usr/bin/env python3
skills/omh-molecular-docking/toolkit/upstream-manifest.json
- Network accessline 53
"license": "Apache-2.0", "path": "src/tooluniverse/tools/NvidiaNIM_diffdock.py", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 54
"path": "src/tooluniverse/tools/NvidiaNIM_diffdock.py", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 55
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 61
"license": "Apache-2.0", "path": "src/tooluniverse/tools/ClusPro_submit_peptide_docking.py", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 62
"path": "src/tooluniverse/tools/ClusPro_submit_peptide_docking.py", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 63
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 69
"license": "Apache-2.0", "path": "src/tooluniverse/data/remote_tools/boltz_tools.json", "repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 70
"path": "src/tooluniverse/data/remote_tools/boltz_tools.json", "repository": "https://github.com/mims-harvard/ToolUniverse", "revision": "53b4f8eb48d304f947bab85182b88d7c2a5c6794", - Network accessline 71
"repository": "https://github.com/mims-harvard/ToolUniverse", - Network accessline 77
"license": "Apache-2.0", "path": "docs/source/docking_python.rst", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 78
"path": "docs/source/docking_python.rst", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 79
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 85
"license": "Apache-2.0", "path": "example/python_scripting/1iep_receptor.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 86
"path": "example/python_scripting/1iep_receptor.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 87
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 93
"license": "Apache-2.0", "path": "example/python_scripting/1iep_ligand.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", - Network accessline 94
"path": "example/python_scripting/1iep_ligand.pdbqt", "repository": "https://github.com/ccsb-scripps/AutoDock-Vina", "revision": "bb64e5e26b520569a86360d69248069b5e665b3f", - Network accessline 95
"repository": "https://github.com/ccsb-scripps/AutoDock-Vina",
skills/omh-routing/references/jev-rail.md
skills/omh-routing/references/skill-common-rail.md
- Instruction override signalline 73
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
skills/omh-routing/references/workflow-artifacts.md
- Network accessline 18
Public contract and synthetic command inputs: [`docs/WORKFLOW-ARTIFACTS.md`](https://github.com/rlaope/oh-my-hermes/blob/main/docs/WORKFLOW-ARTIFACTS.md).
skills/omh-show-reel/references/audio-production.md
- Access to secretsline 7
[Credential-related source omitted]
skills/omh-show-reel/references/craft-audio.md
- Network accessline 19
1. Sign up or log in at https://elevenlabs.io -> bottom left Developers (or the profile) -> API Keys -> Create API Key - Access to secretsline 21
[Credential-related source omitted] - Access to secretsline 49
[Credential-related source omitted] - Network accessline 209
| Symptom | Cause and fix | | --- | --- | | `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl | - Network accessline 210
| --- | --- | | `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl | | The mp3 does not play ("Failed to find two consecutive MPEG audio frames - Network accessline 211
| `CERTIFICATE_VERIFY_FAILED` in Python | A certificate problem with the python.org distribution. Do not turn off verification. `eleven.py` uses curl |
skills/omh-show-reel/references/craft-brief.md
- Network accessline 145
Research <subject> and write it to <project>/research/research.md. Do not rely on memory; write only facts confirmed with WebSearch and WebFetch. (For sites where WebFetch is blocked, fetch with curl -sL -A "Mozilla/5.0" and extract the bod - Network accessline 146
(For sites where WebFetch is blocked, fetch with curl -sL -A "Mozilla/5.0" and extract the body text.) - Network accessline 164
Keep all working files inside the <project> folder. Do not use /tmp. - Priority: official profile, company press releases > press article photos (og:image) > the person's public social media - Fetch the Naver News search result HTML with cu - Network accessline 165
- Priority: official profile, company press releases > press article photos (og:image) > the person's public social media - Fetch the Naver News search result HTML with curl to extract article URLs, then fetch the og:image from the article - Network accessline 166
- Fetch the Naver News search result HTML with curl to extract article URLs, then fetch the og:image from the article HTML (set a browser UA and Referer)
skills/omh-show-reel/references/craft-workflow.md
- Network accessline 79
- **When the codex CLI or the image skills are missing**: the codex-image, photoreal, and codex-cli skills are at https://github.com/revfactory/skills . Guide the user through the printed install command. If they are not installed, build wi
skills/omh-show-reel/references/kinetic-type.md
- Network accessline 107
Method notes informed by Scenario's Kinetic Film exploration (https://www.scenario.com/explorations/kinetic-film/,
skills/omh-show-reel/references/launch-film.md
- Network accessline 86
Method notes informed by a public frame-by-frame study of a 99 s product launch film (DeepSeek Harness Creator Mode, https://x.com/DeepSeekHarness/status/2117256196227019194, - Network accessline 87
film (DeepSeek Harness Creator Mode, https://x.com/DeepSeekHarness/status/2117256196227019194,
skills/omh-show-reel/toolkit/README.md
skills/omh-show-reel/toolkit/assets/engine/engine.js
skills/omh-show-reel/toolkit/assets/engine/fx.js
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/assets/engine/scenes.js
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/codex_ref_image.sh
- Executable scriptline 1
#!/usr/bin/env bash
skills/omh-show-reel/toolkit/scripts/contact_sheet.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/eleven.py
- Executable scriptline 1
Executable file - Network accessline 3
# scripts/eleven.py: OPT-IN provider client, run only by a user who invokes it with their own # key. The key comes from ELEVENLABS_API_KEY in the environment only (no .env, home or config # lookup) and reaches curl on stdin, never argv or l - Network accessline 4
[Credential-related source omitted] - Access to secretsline 4
[Credential-related source omitted] - Network accessline 5
# lookup) and reaches curl on stdin, never argv or logs. No default voice or language: the - Network accessline 6
# caller names both. curl runs with -q (no ~/.curlrc) and --form-string for values. Messages in English; - Access to secretsline 12
[Credential-related source omitted] - Network accessline 14
Why curl: python.org builds of Python often fail TLS verification with urllib because of their certificate store. Verification stays on; curl follows the system certificates and proxy settings. - Network accessline 15
certificate store. Verification stays on; curl follows the system certificates and proxy settings. - Network accessline 41
API = "https://api.elevenlabs.io" - Network accessline 47
KEY_HELP = """This opt-in tool needs your own ElevenLabs API key in the environment: 1) Sign in at https://elevenlabs.io -> Developers (or profile) -> API Keys -> Create API Key. - Network accessline 48
1) Sign in at https://elevenlabs.io -> Developers (or profile) -> API Keys -> Create API Key. - Access to secretsline 51
[Credential-related source omitted] - Access to secretsline 62
[Credential-related source omitted] - Access to secretsline 63
[Credential-related source omitted] - Network accessline 89
"""Never echo the key: a user's curl config or proxy could put headers on stderr.""" - Access to secretsline 95
[Credential-related source omitted] - Access to secretsline 97
[Credential-related source omitted] - Network accessline 101
if body is not None: cmd += ["-H", "Content-Type: application/json", "--data-binary", json.dumps(body, ensure_ascii=False)] for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file - Network accessline 102
cmd += ["-H", "Content-Type: application/json", "--data-binary", json.dumps(body, ensure_ascii=False)] for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file cmd += ["--form-string", - Network accessline 103
for k, v in (form or {}).items(): # literal values: a leading @ or < never makes curl read a file - Possible obfuscationline 165
audio = base64.b64decode(d["audio_base64"]) - Access to secretsline 240
[Credential-related source omitted] - Access to secretsline 241
[Credential-related source omitted]
skills/omh-show-reel/toolkit/scripts/finish.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/font-coverage.mjs
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/mix.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/motion_check.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/music_tools.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/narrate.py
skills/omh-show-reel/toolkit/scripts/new_project.py
skills/omh-show-reel/toolkit/scripts/preflight.py
skills/omh-show-reel/toolkit/scripts/prep_images.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/qa_check.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/render.mjs
- Executable scriptline 1
Executable file - Network accessline 158
if(!req.url.startsWith('/'))throw Error('proxy request refused'); if(req.url==='/favicon.ico'){res.writeHead(204);res.end();return;} const pathname=new URL(req.url,'http://127.0.0.1').pathname; - Network accessline 159
if(req.url==='/favicon.ico'){res.writeHead(204);res.end();return;} const pathname=new URL(req.url,'http://127.0.0.1').pathname; const name=pathname==='/'?page:pathname.slice(1); - Network accessline 160
const pathname=new URL(req.url,'http://127.0.0.1').pathname; - Network accessline 171
await new Promise((resolve,reject)=>{server.once('error',reject);server.listen(0,'127.0.0.1',resolve);}); loopbackPort=server.address().port; const origin=`http://127.0.0.1:${loopbackPort}`; - Network accessline 172
loopbackPort=server.address().port; const origin=`http://127.0.0.1:${loopbackPort}`; launching=puppeteer.launch({executablePath:noLinks(options.browser),headless:true,timeout:Math.min(seconds*1000,30000),protocolTimeout:Math.min(sec - Network accessline 173
const origin=`http://127.0.0.1:${loopbackPort}`;
skills/omh-show-reel/toolkit/scripts/synth_music.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/scripts/timeline.py
- Executable scriptline 1
Executable file
skills/omh-show-reel/toolkit/upstream-manifest.json
- Network accessline 130
"license": "MIT", "local_sha256": "85c27191aef2d08135a665d14e0330f30842bbd90d6e1bd89110cd68b8313de7", "modification_notice": "Opt-in provider client run only by the user: key from ELEVENLABS_API_KEY only (no .env/home/config loo - Network accessline 131
"local_sha256": "85c27191aef2d08135a665d14e0330f30842bbd90d6e1bd89110cd68b8313de7", "modification_notice": "Opt-in provider client run only by the user: key from ELEVENLABS_API_KEY only (no .env/home/config lookup), on curl stdin; no - Network accessline 132
[Credential-related source omitted] - Access to secretsline 132
[Credential-related source omitted] - Access to secretsline 199
[Credential-related source omitted] - Network accessline 425
} }, "repository": "https://github.com/revfactory/showreel", - Network accessline 426
}, "repository": "https://github.com/revfactory/showreel", "revision": "64521220a2f8e91cb9894400c48c15b7f45205d6", - Network accessline 427
"repository": "https://github.com/revfactory/showreel",
skills/omh-source-finder/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
skills/omh-source-finder/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
skills/omh-sprite-forge/toolkit/scripts/forge.py
skills/omh-sprite-forge/toolkit/upstream-manifest.json
skills/omh-terminal/SKILL.md
- Dangerous shell operationline 40
- Prompt: command-operator run rm -rf without cwd, confirmation, or observation gates.
skills/omh-web-research/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
skills/omh-web-research/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
skills/omh-wiki/references/wiki-ecosystem.md
- Network accessline 11
- Source: https://github.com/mudrii/hermes-agent-docs - Network accessline 19
- Source: https://github.com/dannyshmueli/obsidian-hermes-console - Network accessline 27
- Source: https://github.com/martymcenroe/HermesWiki - Network accessline 35
- Source: https://github.com/keepnotes-ai/keep - Network accessline 43
- Source: https://github.com/loremaster-ai/loremaster - Network accessline 51
- Source: https://github.com/SkillForge-Labs/obsidian-auto-context - Network accessline 59
- Source: https://github.com/beiyuii/personal-api-skill
skills/ulw-maestro/SKILL.md
- Instruction override signalline 122
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
skills/ulw-research/references/search-examples.md
- Network accessline 139
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 140
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 141
"locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 420
"location": { "kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" - Network accessline 421
"kind": "uri", "locator": "https://example.invalid/?sig=A%2FB&v=01" }, - Network accessline 422
"locator": "https://example.invalid/?sig=A%2FB&v=01"
skills/ulw-research/references/search-fields.md
- Network accessline 38
{"$schema":"https://json-schema.org/draft/2020-12/schema","$defs":{"source_kind":{"enum":["web","local_file","connected_app","context"]},"stamp":{"type":"string","minLength":1,"maxLength":64},"as_of":{"anyOf":[{"type":"object","properties":
skills/ulw-work/SKILL.md
- Instruction override signalline 156
- Before dispatch, grant the executor session every permission the task will need — file write/edit, command/test execution, and the working directory — on the dispatch command itself, not through settings-file guesses: for non-interactive
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
Declared and executed: 6 facts
- Contacts www.w3.org, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/assets/engine/engine.js:239High confidence
- Contacts api.elevenlabs.io, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/scripts/eleven.py:41High confidence
- Contacts elevenlabs.io, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/scripts/eleven.py:48High confidence
- Contacts www.w3.org, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/assets/engine/engine.js:239High confidence
- Contacts api.elevenlabs.io, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/scripts/eleven.py:41High confidence
- Contacts elevenlabs.io, which SKILL.md, the README and the plugin manifest do not mentionomh-show-reel/toolkit/scripts/eleven.py:48High confidence
Signal confidence: 353 facts
- Executable script in code of a file that runsomh-ai-job-search/toolkit/scripts/job_state.py:1High confidence
- Network access in prose of documentationomh-apple-design/references/materials-and-accessibility.md:5Low confidence
- Network access in prose of documentationomh-apple-design/references/materials-and-accessibility.md:6Low confidence
- Network access in prose of documentationomh-apple-design/references/materials-and-accessibility.md:7Low confidence
- Network access in prose of documentationomh-apple-design/references/materials-and-accessibility.md:8Low confidence
- Network access in prose of documentationomh-apple-design/references/materials-and-accessibility.md:9Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:5Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:6Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:7Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:8Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:9Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:10Low confidence
- Network access in prose of documentationomh-apple-design/references/platform-foundations.md:11Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:8Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:9Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:10Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:11Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:12Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:13Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:14Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:15Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:16Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:17Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:18Low confidence
- Network access in prose of documentationomh-apple-design/references/product-visual-production.md:19Low confidence
- Network access in prose of documentationomh-apple-design/references/review-playbook.md:5Low confidence
- Network access in prose of documentationomh-apple-design/references/review-playbook.md:6Low confidence
- Network access in prose of documentationomh-apple-design/references/review-playbook.md:7Low confidence
- Network access in prose of documentationomh-apple-design/references/review-playbook.md:8Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:13Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:14Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:17Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:18Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:19Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:24Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:25Low confidence
- Network access in prose of documentationomh-apple-design/references/web-production-libraries.md:26Low confidence
- Executable script in code of a file that runsomh-biomedical-evidence/toolkit/scripts/reconcile.py:1High confidence
- Access to secrets in prose of the SKILL.mdomh-external-connector-readiness/SKILL.md:67Low confidence
- Network access in prose of documentationomh-frontend/references/chart-styling.md:101Low confidence
- Network access in prose of documentationomh-frontend/references/chart-styling.md:102Low confidence
- Network access in prose of documentationomh-frontend/references/chart-styling.md:103Low confidence
- Network access in prose of documentationomh-frontend/references/chart-styling.md:104Low confidence
- Network access in prose of documentationomh-frontend/references/chart-styling.md:105Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:151Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:152Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:153Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:154Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:155Low confidence
- Network access in prose of documentationomh-frontend/references/component-registry-adoption.md:156Low confidence
and 303 more
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Native | Path .claude/install.ps1 | .claude/skills/<skill-name>/ |
| Codex | Native | Manifest AGENTS.md | .agents/skills/<skill-name>/ |
| Cursor | Native | Path .cursor/install.ps1 | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md agent-skills/omh-accessibility-audit/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md agent-skills/omh-accessibility-audit/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Native | Path .opencode/install.ps1 | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.
Explore alternatives and comparisons
Add this badge to your README
It updates every night and links to this page.
[](https://hotskills.dev/skill/rlaope-oh-my-hermes/)