Skip to content
cccskills
FreePublished on GitHub

omh-jev-ask

Submit text and independent yes-or-no, multiple-choice, or rating questions to Jev using your own key. Receive probabilities rather than prose, along with the served model, request status, and cost information, including cases where no answer is returned.

OriginalShow the original description

[omh] User named Jev for yes/no or pick-one probabilities: Jev ask: typed yes/no, pick-one, or scored questions to Jev with your own key; returns probabilities, never prose. Use when the user says: jev-ask, ask jev, jev question, jev score.

rlaope/oh-my-hermes

Run score Not tested

See how to install

Good for

  • Check the probability that text meets a stated criterion
  • Compare probabilities across predefined choices
  • Evaluate text using ordered rating levels
  • Review model and cost details for Jev results

Files included (2)

  • SKILL.md2.9 KB
  • references/full-contract.md4.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Jev Ask

Required: text to judge and independent typed questions. Output: Jev's probabilities, served model, and cost, or a non-answer status.

Read skill_view(name='omh-routing', file_path='references/jev-rail.md') before the first ask: consent, what leaves the machine, limits, and non-answer statuses. Prepared OMH routing is not execution or approval. Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

Contract: references/full-contract.md.

Procedure

  1. Check the rail: the user asked for Jev in this turn, and say in one line what state will carry.
  2. Write independent, self-contained questions over one state: Noul with criteria.true/criteria.false, Choice with an unknown option, Score with ordered levels.
  3. Call omh_jev_ask with questions (default model jev-latest; pin jev-1.13.0 when a threshold was tuned).
  4. Report each number verbatim with the served model, attempts, and cost_usd plus cost_source; 0.4 to 0.6 is uncertain.

Completion Checklist

  • Preserve workflow intent and stop conditions; load the full contract 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 real unresolved user decision or a useful briefing discussion remains, offer one specific, content-linked question. Completed work needs no question; omit unrelated non-action footers and generic offers to continue.
  • Report the tool's status, ask_id, served model, and cost source; a non-answer is reported as its status and is never an answer.
  • Record observed delegation results; use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Recovery Notes

  • Tool missing, consent_not_observed, or refused: follow the rail's recovery section; never simulate an answer.

Workflow Lane

advisory local context

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

dag-ulw

FreeSummary

Coordinate a large job by splitting it into small tasks with explicit dependencies. Run ready tasks in parallel through Hermes, verify the combined result separately, and repair failures within defined limits before reporting completed work and remaining gaps.

  • Delivering a feature across multiple modules
  • Coordinating a migration with ordered steps
  • Managing a broad cleanup across separate work areas
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

model-onboarding

FreeSummary

Guide the addition of a new model generation to oh-my-hermes. The workflow checks model recognition, official specifications, routing rules that select models for tasks, documented pricing, and live access, then validates changes with tests and comparative benchmarks.

  • Add a new model generation to oh-my-hermes
  • Check API model IDs and dated snapshot recognition
  • Update model selection chains and related documentation
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-accessibility-audit

FreeSummary

Prepare an accessibility audit for an interface using WCAG 2.2 AA, an accessibility standard. Organize evidence for keyboard use, screen readers, contrast, target size, and zoom behavior, then document findings, missing checks, and remediation handoffs.

  • Reviewing checkout accessibility against WCAG 2.2 AA
  • Checking keyboard access and focus order
  • Organizing screen-reader labels and announcement evidence
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-achievements

FreeSummary

Summarize earned badges, recent unlocks, achievement tiers, and progress using local files from the hermes-achievements plugin. Prepare a badge list or report section while making missing information and the limits of the recorded snapshot clear.

  • Checking earned badges
  • Reviewing recently unlocked achievements
  • Finding progress toward the next achievement tier
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-adversarial-consensus

FreeSummary

Examine a technical proposal through independent perspectives, challenge their findings, and resolve objections. The result is a structured set of constraints, decisions, risks, and open questions for a separate planning workflow.

  • Reviewing a technical proposal before planning
  • Challenging assumptions behind a migration
  • Organizing risks and unresolved questions
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

omh-agent-board

FreeSummary

Coordinate multiple Hermes agents or profiles through a shared task board. Organize assignments, handoffs, activity updates, blockers, and completion states, while distinguishing planned actions from work supported by observed results.

  • Coordinate agent roles for a launch checklist
  • Track task handoffs and blockers
  • Prepare work for pickup across profiles or after a restart
rlaope/oh-my-hermes3.6KUpdated Oct 23, 2026

See all skills by rlaope

Report a problem with this skill