Siftrank
noperator/siftrank
Find needles in haystacks with SiftRank. An agent skill from noperator/siftrank.
[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step.
Install Omh Support Operations
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rlaope/oh-my-hermes omh-support-operations --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-support-operations .claude/skills/omh-support-operations && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .claude/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rlaope/oh-my-hermes omh-support-operations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omh-support-operations .agents/skills/omh-support-operations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .agents/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rlaope/oh-my-hermes omh-support-operations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omh-support-operations .cursor/skills/omh-support-operations && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .cursor/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rlaope/oh-my-hermes.git --path skills/omh-support-operations--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rlaope/oh-my-hermes omh-support-operations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omh-support-operations .gemini/skills/omh-support-operations && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .gemini/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rlaope/oh-my-hermes omh-support-operationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omh-support-operations .github/skills/omh-support-operations && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .github/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rlaope/oh-my-hermes omh-support-operations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omh-support-operations .opencode/skills/omh-support-operations && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "omh-support-operations" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-support-operations into .opencode/skills/omh-support-operations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-support-operations", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
omh-support-operations- GitHub stars
- 3.2k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 817 words
- Files
- 1
- Skills in repo
- 143
- Repo updated
- First seen
- Licence
- MIT
At a glance
[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step.
- The user says: support escalation
- SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Customer support reply
What it does
Omh Support Operations is an agent skill from rlaope/oh-my-hermes. [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, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Customer support. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.
When your agent uses it
- The user says: support escalation
- Customer support reply
Example prompts
- “/omh-support-operations”
What it can do on your machine
Read from SKILL.md and the folder at commit 7cd0d02. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Omh Support Operations loads about 1.7k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 817 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rlaope/oh-my-hermes at commit 7cd0d02, republished under its MIT licence (© rlaope). 817 words, ~1,697 tokens.
Download SKILL.mdSave it as
.claude/skills/omh-support-operations/SKILL.md (or your agent's skills folder).- name
- omh-support-operations
- description
- [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, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
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
feedback-triage. - The user only needs a generic, non-support marketing or email rewrite with no case, severity, or escalation context; use
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
connector-operatorwith 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
live-incident-response. - The request is a closed incident's postmortem or reliability evidence rather than a support-case response; use
reliability-review.
Examples
Good example:
- Prompt: Draft a calm reply for this login-outage customer and tell me whether it needs an engineering escalation.
- Expected behavior: Prepare a customer-safe reply, severity matrix, engineering escalation recommendation, and owner handoff.
- Why: The request is one support case with reply and escalation decisions, not a feedback backlog or ticket mutation.
Bad example:
- Prompt: Cluster last quarter's support feedback into roadmap opportunities.
- Expected behavior: Route to
feedback-triage, notsupport-operations. - Why: A historical signal backlog needs product-pattern triage rather than case-level support guidance.
Completion Checklist
- The source boundary, signal clusters, severity, and follow-up lane are named.
- Bug, feature, research, strategy, and coding handoff outcomes stay separate.
- The next workflow is recommended before any implementation claim.
Recovery Notes
- If feedback lacks source or severity, ask for the missing signal before coding handoff.
- If the item is actually a plan or research request, route to that workflow instead of triage.
Workflow Lane
- Current lane: Research and company ops (
product-docs,source-finder,web-research,research,model-optimization,inference-serving,model-finetuning,research-brief,+20 more) - research, signals, ops, and briefings. - If intent belongs to another lane, hand back to
oh-my-hermesor name the adjacent workflow. - Shared product, routing, compatibility, and evidence rules:
omh-routing/references/skill-common-rail.md.
Use When
Use when one or a bounded set of support contacts needs response drafting, urgency classification, incident/escalation routing, and follow-up ownership.
Strong routing signals: `support escalation`, `customer support reply`, `ticket triage`, `고객 지원 에스컬레이션`, `고객 답변 초안`, `지원 티켓 분류`Show full SKILL.md (434 more words)Show less
Catalog Metadata
Category: triage
Phase: support-operations
Hermes role: operator
Quality tier: triage-gated
Reasoning demand: standard
Quality bar:
- State issue, severity, impact, evidence gaps, owner, and next route.
- Draft a reply without treating it as a sent customer communication.
Handoff policy:
Keep domain framing, clarification, source/evidence synthesis, draft outputs, and next-work routing in Hermes. A prepared brief, review, reply, or plan is not an external action, approval, filing, send, publish, data mutation, implementation, review, CI, or merge claim. Prepare a connector, file, coding, or human-review handoff only when the user explicitly accepts that next step; report it only from observed evidence. Reply text is a draft, escalation is a recommendation, and no ticket state, message send, refund, account action, or customer outcome is claimed.
Required inputs:
- support case
- known facts
- customer impact
- available ownership or escalation path
Expert clarification questions:
support case- English: Which support case should we examine first?
- Korean: 어떤 지원 사례를 먼저 살펴봐야 하나요?
Expected outputs:
- customer-safe reply draft with stated facts, unknowns, and tone
- issue/severity/impact/escalation matrix
- internal next-step and owner handoff brief
- missing repro, account, entitlement, or approval evidence list
Artifact expectations:
- prepared support case brief when a wrapper captures it
Artifact contracts:
This label denotes the machine-enforcement level, not a skill quality score and not an observed evidence state.
- contract_id:
support-operations; enforcement_level:guidance_only; consumer_id:none
Safety rules:
- Keep customer-safe facts, unknowns, and escalation recommendations distinct.
- Do not claim ticket mutation, message send, refund, account action, or case outcome.
Runtime Evidence
Preferred harness for this skill: ops-review.
omh runtime record --skill support-operations --harness ops-review --status startedRecord observed delegation results; otherwise return not_available or not_observed.
Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.
Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
© rlaope, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/omh-support-operations of rlaope/oh-my-hermes.
Open the folder on GitHubat commit 7cd0d02
Compare with similar skills
Omh Support Operations next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Omh Support Operations this skillrlaope/oh-my-hermes | 3.2k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Siftranknoperator/siftrank | 225 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Supporthaacked/dotfiles | 134 | — | ~2.9k | Automated safety check: Pass | None | |
| Customer Support Agentmastra-ai/mastra | 29k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Add Agent Adaptersafedep/gryph | 172 | — | ~679 | Automated safety check: Pass | Apache-2.0 | |
| Agent Support Matrixjazzyalex/agent-sessions | 895 | — | ~587 | Automated safety check: Pass | MIT |
Similar skills
Support
haacked/dotfiles
Support hero workflow — start a ticket investigation with auto-organized notes, find existing notes, or generate the weekly highlights log.
Customer Support Agent
mastra-ai/mastra
Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues.
Add Agent Adapter
safedep/gryph
A skill your agent uses when adding support for a new AI coding agent to Gryph, or when changing how an existing agent adapter is wired.
Agent Support Matrix
jazzyalex/agent-sessions
Maintain Agent Sessions agent support matrix and JSON/JSONL parsing compatibility.
Company Brain Company QA
topoteretes/cognee
Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together.
More from rlaope/oh-my-hermes
All 143 skills in this repoOmh Accessibility Audit
rlaope/oh-my-hermes
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
Omh Agent Evaluation
rlaope/oh-my-hermes
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.
Omh Agent Instructions
rlaope/oh-my-hermes
[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…
Omh Agent Ops Review
rlaope/oh-my-hermes
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
Omh AI Slop Cleaner
rlaope/oh-my-hermes
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.
Omh App Debugging
rlaope/oh-my-hermes
[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…
Related
Categories
Questions about Omh Support Operations
What does Omh Support Operations do?
[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step. Omh Support Operations is an agent skill from rlaope/oh-my-hermes. [omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step.
When should I use Omh Support Operations?
Omh Support Operations fits situations like: the user says: support escalation; customer support reply.
How do I install Omh Support Operations in Claude Code?
Run `npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a claude-code`. Or copy the skill folder (skills/omh-support-operations in rlaope/oh-my-hermes) into .claude/skills/omh-support-operations in your project. Claude Code loads it when a task matches its description.
How do I install Omh Support Operations in Codex?
Run `npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a codex`. Or copy the skill folder (skills/omh-support-operations in rlaope/oh-my-hermes) into .agents/skills/omh-support-operations in your project. Codex loads it when a task matches its description.
Can I use Omh Support Operations in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-support-operations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-support-operations, .gemini/skills/omh-support-operations, .github/skills/omh-support-operations and .opencode/skills/omh-support-operations in your project.
What does Omh Support Operations need to run?
SKILL.md names no scripts, command-line tools or credentials: Omh Support Operations is instructions for the agent only.
Does Omh Support Operations access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Omh Support Operations safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Omh Support Operations use?
Omh Support Operations is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Omh Support Operations use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Omh Support Operations?
Skills that share tags, products or a category with Omh Support Operations: Siftrank (noperator/siftrank, 225 stars), Support (haacked/dotfiles, 134 stars), Customer Support Agent (mastra-ai/mastra, 29k stars) and Add Agent Adapter (safedep/gryph, 172 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Omh Support Operations?
rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,243 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 10, 2026.
Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.