rlaope
UserAll in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages
Categories
Indexed Skills (63)
model-onboarding
Onboard a new model generation or sibling into oh-my-hermes: probe router recognition, research the official contract, write trait-to-counter calibration, place routing in both lanes, price from documented list only, gate machine config on a served route, prove with the gates, close with a benchmark pair. Use when a model family ships a new generation (for example "Fable 5.1 is out", "GLM 5.4 shipped", "onboard new model", "add model to chains").
review-sweep
Review oh-my-hermes pull requests that have not been reviewed at their current head commit. Run manually to sweep the open backlog, or pass a number to review one PR. Applies the repository's REVIEW.md policy and posts findings as a GitHub review with inline comments.
triage-sweep
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by area.
omh-legal-compliance-review
omh
omh-live-info
omh
omh-image-cards
omh
omh-localization-review
omh
omh-media-input
omh
omh-accessibility-audit
omh
omh-achievements
omh
omh-agent-board
omh
omh-agent-debug
omh
omh-agent-evaluation
omh
omh-agent-ops-review
omh
omh-ai-slop-cleaner
omh
omh-automation-blueprint
omh
omh-browser-operator
omh
omh-build-failure-triage
omh
omh-code-review
omh
omh-codebase-onboarding
omh
omh-codegraph-refresh
omh
omh-command-operator
omh
omh-connector-operator
omh
omh-content-operator
omh
omh-context-budget-review
omh
omh-cto-loop
omh
omh-data-analysis
omh
omh-deep-interview
omh
omh-deliverable-package
omh
omh-deploy-and-monitor
omh
omh-design-orchestration
omh
omh-design-quality-gate
omh
omh-executor-runtime-readiness
omh
omh-external-connector-readiness
omh
omh-failure-signal-audit
omh
omh-feedback-triage
omh
omh-frontend
omh
omh-gateway-intent-card
omh
omh-github-event-ops
omh
omh-harness-session-inventory
omh
omh-idea-to-deploy
omh
omh-img-summary
omh
omh-instinct-ledger
omh
omh-live-info-operator
omh
omh-loop
omh
omh-materials-package
omh
omh-media-input-operator
omh
omh-meeting-brief
omh
omh-memory-new
omh
omh-memory-sync
omh
omh-meta-router
omh
omh-model-setup
omh
context-memory-hygiene
Invoke when deciding what to load into context, what to persist across turns or sessions, and what to drop — reads only what the task needs, writes durable handoffs, avoids context pollution, and chooses when to re-derive versus recall.
delegation-parallelism
Invoke when deciding whether to split work across parallel agents/sessions or do it inline — tests scope independence, weighs coordination cost against the parallelism win, and sets an observation cadence for delegated work.
exploration-strategy
Build an accurate mental model of an unfamiliar codebase or problem before making any edit — structural scan, entry-point location, one end-to-end trace, and an explicit known-vs-assumed ledger.
failure-mode-enumeration
Systematically enumerate how code can break — boundaries, concurrency, partial failure, malicious input, time, resource exhaustion — before writing defenses, then convert the list into tests and guards while pruning paranoia that does not pay rent.
honest-reporting
Invoke when writing any status, completion, or result report — calibrates claims to the evidence actually gathered, marks the unmeasured as open, reports failures plainly, and distinguishes "verified at layer X" from "should work".
incremental-safety
Decompose a large or risky change into a sequence of independently safe intermediate states, so the system stays green at every step and any step can be reverted alone.
self-correction-loop
Invoke when an implementation attempt produces a failure signal (test failure, compile error, wrong output, crash, perf regression) and you must decide whether to retry, rethink, or back out — instead of hammering the same fix.
spec-to-code-fidelity
Invoke when implementing from an authoritative written source — an RFC, academic paper, binary format spec, protocol document, or mathematical derivation — where correctness means matching the document, not just passing ad-hoc tests.
state-probing
Invoke before acting on any assumption about the runtime or environment — versions, running processes, file/disk reality, git state, network reachability. Grounds claims about the world in a cheap probe instead of a guess, and re-probes when state may have gone stale.
tradeoff-articulation
Invoke when a design decision has multiple viable implementations and the choice affects performance, memory, complexity, or blast radius — forces enumerating real alternatives, quantifying the axes that matter, and recording what would reverse the decision.
verification-discipline
Invoke before claiming any task is done — defines what counts as evidence of completion (execution, not inspection) and how to verify at the layer the requirement actually lives at.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.