live-info-operator
starsforks
How to install live-info-operator?
rlaope/oh-my-hermes/live-info-operator
$npx -y skills add rlaope/oh-my-hermes --skill live-info-operator[omh] Hermes live information workflow: scope read-only weather, finance, sports, map, place, exchange-rate, and time-zone lookups with provider, freshness, units, source-quality, and result-evidence gates.
SKILL.md
| 1 | # Live Info Operator |
| 2 | |
| 3 | This is a Hermes-native `live-info-operator` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `live-info-operator` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: live-info-operator check today's Seoul weather with freshness, units, and provider boundaries before answering. |
| 20 | - Expected behavior: Produce `prepare_live_info_operator_card` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: live-info-operator invent the latest stock price without provider evidence or timestamp. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - Domain, location or symbol, time window, provider preference, freshness, units, and stop condition are explicit. |
| 32 | - Provider setup, API access, source quality, stale data, and missing location/symbol decisions are gated or marked missing. |
| 33 | - Weather, price, score, exchange-rate, time-zone, map, place, and traffic facts are reported only from observed provider evidence. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If the provider, plugin, API key, or connector is missing, route to toolbelt-readiness before preparing result claims. |
| 38 | - If the request asks for citations, best practices, docs, or broad current-source synthesis, route to web-research instead. |
| 39 | - If the request would create, update, invite, send, or mutate external provider state, route to connector-operator instead. |
| 40 | |
| 41 | ## OMH Context Rail |
| 42 | |
| 43 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 44 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 45 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 46 | - 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. |
| 47 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 48 | - 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. |
| 49 | - Coverage: Every generated workflow skill carries this rail. |
| 50 | - Normal users talk to Hermes; OMH CLI is infra. |
| 51 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 52 | |
| 53 | ## Use When |
| 54 | |
| 55 | Use when Hermes should prepare or supervise read-only live information lookups without claiming provider availability, API access, freshness, retrieval, or result correctness. |
| 56 | |
| 57 | Strong routing signals: `live-info-operator`, `live info operator`, `live information`, `real time information`, `real-time information`, `weather today`, `current weather`, `weather forecast`, `stock price`, `crypto price`, `btc price`, `exchange rate`, `sports score`, `game score`, `time zone`, `timezone`, `time in`, `map directions`, `directions to`, `near me`, `nearby restaurants`, `traffic now`, `오늘 날씨`, `현재 날씨`, `날씨 예보`, `주가`, `코인 가격`, `환율`, `스포츠 점수`, `경기 결과`, `시간대`, `현재 시간`, `지도`, `길찾기`, `주변 식당` |
| 58 | |
| 59 | ## Catalog Metadata |
| 60 | |
| 61 | Category: `live-info` |
| 62 | Phase: `live-info-task` |
| 63 | Hermes role: `guide` |
| 64 | Quality tier: `workflow-surface-gated` |
| 65 | |
| 66 | Quality bar: |
| 67 | |
| 68 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 69 | - Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence. |
| 70 | - Expose missing tools, c |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
