Review Analysis
liangdabiao/amazon-sorftime-research-MCP-skill
对亚马逊商品评论进行深度分析，自动识别产品痛点、分析退货原因，生成改进建议和客服回复模板。Invoke when user uses /review-analysis command with a product ASIN.
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow.
Install Omh Feedback Triage
$ npx skills add rlaope/oh-my-hermes --skill omh-feedback-triage -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rlaope/oh-my-hermes omh-feedback-triage --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-feedback-triage .claude/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .claude/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triageType 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-feedback-triage -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rlaope/oh-my-hermes omh-feedback-triage --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-feedback-triage .agents/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .agents/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triage -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rlaope/oh-my-hermes omh-feedback-triage --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-feedback-triage .cursor/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .cursor/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triage--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-feedback-triage -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rlaope/oh-my-hermes omh-feedback-triage --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-feedback-triage .gemini/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .gemini/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triageInstalls 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-feedback-triage -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-feedback-triage .github/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .github/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triage -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-feedback-triage --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-feedback-triage .opencode/skills/omh-feedback-triage && 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-feedback-triage" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-feedback-triage into .opencode/skills/omh-feedback-triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-feedback-triage", 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-feedback-triage- GitHub stars
- 3.2k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 729 words
- Files
- 1
- Skills in repo
- 143
- Repo updated
- First seen
- Licence
- MIT
At a glance
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow.
- The user says: feedback-triage
- 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-feedback-triage
What it does
Omh Feedback Triage is an agent skill from rlaope/oh-my-hermes. [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.
Its SKILL.md is about 1.5k 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 feedback analysis and QA and bug reports. 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: feedback-triage
- Customer-feedback-triage
- Feedback triage
- Customer feedback
Example prompts
- “/omh-feedback-triage”
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 Feedback Triage loads about 1.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 729 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). 729 words, ~1,537 tokens.
Download SKILL.mdSave it as
.claude/skills/omh-feedback-triage/SKILL.md (or your agent's skills folder).- name
- omh-feedback-triage
- description
- [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.
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
lifecycle-growth. - The supplied material is opportunity records and the request is portfolio health or forecast review; use
sales-pipeline-review.
Examples
Good example:
- Prompt: Cluster these customer payment failure reports and feature requests before we plan fixes.
- Expected behavior: Cluster bug signals and feature asks, rank severity or opportunity, and recommend research, planning, or coding as a next workflow.
- Why: The input is mixed feedback that needs classification before delivery decisions.
Bad example:
- Prompt: feedback-triage implement the accepted billing fix now.
- Expected behavior: Route to planning or coding handoff instead of re-triaging.
- Why: The decision is already accepted, so triage would add delay without improving evidence.
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 Hermes should classify feedback, bug reports, and feature asks before deciding whether research, planning, or coding handoff is needed.
Strong routing signals: `feedback-triage`, `customer-feedback-triage`, `feedback triage`, `customer feedback`, `feedback cluster`, `bug or feature`, `feature request triage`, `payment failure feedback`, `feedback trends`, `payment failure`, `payment failure issue`, `payment failure reports`, `고객 피드백`, `피드백`, `피드백 분류`, `피드백을 모아서`, `결제 실패`, `결제 실패 이슈`, `결제 실패 피드백`, `결제 오류`, `고객 불만`, `버그 제보`, `버그 기능 요청`, `기능 요청`Show full SKILL.md (343 more words)Show less
Catalog Metadata
Category: triage
Phase: feedback
Hermes role: operator
Quality tier: triage-gated
Reasoning demand: standard
Quality bar:
- Name the source boundary before clustering feedback.
- Classify signals into bug, feature, research, or strategy follow-up without overclaiming evidence.
- Recommend the next workflow instead of jumping straight to coding.
Handoff policy:
Keep feedback triage in Hermes; recommend the next workflow and prepare a selected executor/runtime handoff only after explicit coding intent or accepted plan evidence.
Required inputs:
- feedback items or summary
- source boundary
- product area
Expected outputs:
- clusters
- severity or opportunity ranking
- next workflow recommendation
- product_evidence_loop/v1
Artifact expectations:
- feedback triage record when a wrapper captures it
Safety rules:
- Do not turn feedback into a roadmap, implementation plan, or coding handoff by default.
- Separate bug signal, feature ask, severity, opportunity, and missing evidence.
- Route code changes only after explicit user intent or accepted planning evidence.
- product_evidence_loop/v1 is prepared-only opaque references, not observed evidence or execution.
Runtime Evidence
Preferred harness for this skill: customer-insight-triage.
omh runtime record --skill feedback-triage --harness customer-insight-triage --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-feedback-triage of rlaope/oh-my-hermes.
Open the folder on GitHubat commit 7cd0d02
Compare with similar skills
Omh Feedback Triage 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 Feedback Triage this skillrlaope/oh-my-hermes | 3.2k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Review Analysisliangdabiao/amazon-sorftime-research-MCP-skill | 959 | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| Bggg Data Amazonbinggandata/bggg-skills | 605 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Zsxqunnoo/zsxq-skill | 304 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Roadtrip NavigatorWaybox-AI/roadtrip-skill | 126 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Always Compareai-analyst-lab/ai-analyst | 304 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Bggg Data Amazon
binggandata/bggg-skills
Collect Amazon.com written product reviews at scale through Woot's public review AJAX route, retain every attempt and error log, reconcile partial runs, and normalize exact review text into…
Zsxq
unnoo/zsxq-skill
知识星球 CLI（zsxq-cli）与底层接口完整操作指南，涵盖星球和内容管理、Skill Pay 微信支付场景。当用户提到知识星球、zsxq、小密圈、星球、登录/认证、发帖、评论、回答、编辑、删除主题、定时发布/定时任务/定时回答、投票、问答主题、markdown 正文、AI…
Roadtrip Navigator
Waybox-AI/roadtrip-skill
Generate North American road-trip itineraries as a map-first, offline-friendly single-file HTML page.
Always Compare
ai-analyst-lab/ai-analyst
Never present a metric or number in isolation; anchor every number to a comparison (prior period, benchmark, or another segment) or state that none is available.
Account Deletion
gustavscirulis/snapgrid
Generates an Apple-compliant account deletion flow with multi-step confirmation UI, optional data export, configurable grace period, Keychain cleanup, and server-side deletion request.
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 Debug
rlaope/oh-my-hermes
[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.
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.
Related
Categories
Questions about Omh Feedback Triage
What does Omh Feedback Triage do?
[omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow. Omh Feedback Triage is an agent skill from rlaope/oh-my-hermes. [omh] Unsorted customer feedback and bug reports: cluster customer signals and choose the next workflow.
When should I use Omh Feedback Triage?
Omh Feedback Triage fits situations like: the user says: feedback-triage; customer-feedback-triage; feedback triage; customer feedback.
How do I install Omh Feedback Triage in Claude Code?
Run `npx skills add rlaope/oh-my-hermes --skill omh-feedback-triage -a claude-code`. Or copy the skill folder (skills/omh-feedback-triage in rlaope/oh-my-hermes) into .claude/skills/omh-feedback-triage in your project. Claude Code loads it when a task matches its description.
How do I install Omh Feedback Triage in Codex?
Run `npx skills add rlaope/oh-my-hermes --skill omh-feedback-triage -a codex`. Or copy the skill folder (skills/omh-feedback-triage in rlaope/oh-my-hermes) into .agents/skills/omh-feedback-triage in your project. Codex loads it when a task matches its description.
Can I use Omh Feedback Triage 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-feedback-triage -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-feedback-triage, .gemini/skills/omh-feedback-triage, .github/skills/omh-feedback-triage and .opencode/skills/omh-feedback-triage in your project.
What does Omh Feedback Triage need to run?
SKILL.md names no scripts, command-line tools or credentials: Omh Feedback Triage is instructions for the agent only.
Does Omh Feedback Triage 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 Feedback Triage 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 Feedback Triage use?
Omh Feedback Triage 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 Feedback Triage use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Feedback Triage?
Skills that share tags, products or a category with Omh Feedback Triage: Review Analysis (liangdabiao/amazon-sorftime-research-MCP-skill, 959 stars), Bggg Data Amazon (binggandata/bggg-skills, 605 stars), Zsxq (unnoo/zsxq-skill, 304 stars) and Roadtrip Navigator (Waybox-AI/roadtrip-skill, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Omh Feedback Triage?
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.