best-practice-research
starsforks
How to install best-practice-research?
rlaope/oh-my-hermes/best-practice-research
$npx -y skills add rlaope/oh-my-hermes --skill best-practice-research[omh] Hermes adaptation for bounded official/upstream best-practice research.
SKILL.md
| 1 | # Best Practice Research |
| 2 | |
| 3 | This is a Hermes-native `best-practice-research` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `best-practice-research` exists to keep `research` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence. |
| 12 | - The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed. |
| 13 | |
| 14 | ## Examples |
| 15 | |
| 16 | Good example: |
| 17 | |
| 18 | - Prompt: best-practice-research: check official docs and upstream examples before we choose the plugin packaging pattern. |
| 19 | - Expected behavior: Gather primary-source guidance, compare options, and separate evidence from recommendation. |
| 20 | - Why: The request needs citation-backed best-practice research before implementation. |
| 21 | |
| 22 | Bad example: |
| 23 | |
| 24 | - Prompt: best-practice-research: treat casual chat or unaccepted work as if this workflow already produced verified results. |
| 25 | - Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `best-practice-research`. |
| 26 | - Why: The request lacks the required inputs or would overclaim work that Hermes did not observe. |
| 27 | |
| 28 | ## Completion Checklist |
| 29 | |
| 30 | - The research question, source boundaries, recency assumptions, and confidence level are named. |
| 31 | - Observed sources, inference, synthesis, and unresolved retrieval gaps are separated. |
| 32 | - Follow-up planning or handoff uses the research summary without calling it execution evidence. |
| 33 | |
| 34 | ## Recovery Notes |
| 35 | |
| 36 | - If sources cannot be accessed, state the retrieval gap and use only observed local context. |
| 37 | - If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary. |
| 38 | |
| 39 | ## OMH Context Rail |
| 40 | |
| 41 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 42 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 43 | - Current lane: **Research and company ops** (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings. |
| 44 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 45 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 46 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 47 | - Coverage: Every generated workflow skill carries this rail. |
| 48 | - Normal users talk to Hermes; OMH CLI is infra. |
| 49 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 50 | |
| 51 | ## Use When |
| 52 | |
| 53 | Use when correctness depends on current official or upstream guidance. |
| 54 | |
| 55 | Strong routing signals: `best-practice-research`, `best practice`, `official docs`, `upstream guidance` |
| 56 | |
| 57 | ## Catalog Metadata |
| 58 | |
| 59 | Category: `research` |
| 60 | Phase: `evidence` |
| 61 | Hermes role: `researcher` |
| 62 | Quality tier: `source-gated` |
| 63 | |
| 64 | Quality bar: |
| 65 | |
| 66 | - Use official or upstream sources first and name the version/environment assumptions. |
| 67 | - Map applicability to the user's local context before recommending action. |
| 68 | - Preserve residual uncertainty instead of overstating best practice. |
| 69 | |
| 70 | Handoff policy: |
| 71 | |
| 72 | Run as Hermes-side evidence gathering; hand coding to the selected executor/runtime only after source-backed guidance is summarized. |
| 73 | |
| 74 | Required inputs: |
| 75 | |
| 76 | - chosen technology |
| 77 | - question |
| 78 | - version or environment constraints |
| 79 | |
| 80 | Expected outputs: |
| 81 | |
| 82 | - source-backed guidance |
| 83 | - applicability notes |
| 84 | - residual uncertainty |
| 85 | |
| 86 | Artifact expectations: |
| 87 | |
| 88 | - research notes or citations when the wrapper captures them |
| 89 | |
| 90 | Safety rules: |
| 91 | |
| 92 | - Do not imply hidden Hermes runtime behavior. |
| 93 | - Use the smallest verification that can prove the claim. |
| 94 | |
| 95 | ## Harness Discipline |
| 96 | |
| 97 | - Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes. |
| 98 | - Prefer richer evidence and clearer stop conditions over adding more workflow names. |
| 99 | - Use specialist lanes only when they change the quality of the answer or verification. |
| 100 | |
| 101 | ## Runtime Evidence |
| 102 | |
| 103 | Preferred harness for this skill: `research`. |
| 104 | |
| 105 | When |
People who liked this also viewed
6 picksType
- azure-kustoQuery and analyze data in Azure Data Explorer (Kusto/ADX) using KQL for log analytics, telemetry, and time series analysis. WHEN: KQL queries, Kusto database queries, Azure Data Explorer, ADX clustersSkillsJul 2026
- lark-base飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。SkillsJul 2026
- lark-calendar飞书日历：管理日历日程和会议室。查看/搜索日程、创建/更新日程、管理参会人、查询忙闲和推荐时段、预定会议室。当用户需要查看日程安排、创建/修改会议、查询/预定会议室时使用。不负责：查询过去的视频会议记录（走 lark-vc）、待办任务（走 lark-task）。SkillsJul 2026
- shadcnManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. AppliSkillsJul 2026
- xlsxUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.SkillsJul 2026
- firebase-data-connectAgent Skills for FirebaseSkillsJul 2026
