跳到正文
cccskills
免费在 GitHub 公开

omh-jit-learn

Choose what to learn to address a current project blocker, then prepare a source-backed brief covering books, podcasts, creators, and courses. Recommendations reflect current knowledge, deadlines, and immediate application, with one concrete starting action.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

[omh] Blocked on a project by a knowledge gap: just-in-time learning workflow: select and confirm an immediate learning target, research credible sources, and prepare an application-first brief without popularity ranking. Use when the user says: jit-learn, learn next, learn now, blocker-specific learning target, highest-leverage learning target, immediate learning payoff, immediately applicable learning brief, source-backed learning brief.

查看安装方法

适用场景

  • Choose a learning target for a current work blocker
  • Find resources to apply within the coming week
  • Compare learning materials by fit and time to practical value
  • Turn resource recommendations into a first application step

包含的文件(1)

  • SKILL.md13.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Jit Learn

This is a Hermes-native jit-learn workflow skill.

Why This Exists

jit-learn exists to choose what is worth learning for the user's present problem and convert credible sources into an immediate application path, instead of returning a generic self-help shelf or a popularity list.

Do Not Use When

  • The user asks OMH to learn from workflow outcomes, missed routes, or evaluation traces; use omh-workflow-learning.
  • The learning goal is already chosen and the user wants a multi-week syllabus, instructional sequence, or assessment plan; use omh-curriculum-design.
  • The user supplied a paper, PDF, arXiv entry, or excerpt and wants it explained; use omh-paper-learning.
  • The requested output is a typed source candidate inventory or acquisition status rather than a fitted learning brief; use omh-source-finder.
  • The research question and target are already scoped and the user wants current facts, citations, or source synthesis rather than choosing what to learn; use ulw-research.

Examples

Good example:

  • Prompt: What should I learn next to solve my current onboarding blocker? Recommend books, podcasts, creators, and courses I can apply this week.
  • Expected behavior: Ask one confirmation question, confirm the immediate target, then prepare a source-backed four-section learning brief ranked by fit and time-to-first-value.
  • Why: The user needs target selection and immediate transfer, not a generic curriculum or popularity-ranked resource list.

Bad example:

  • Prompt: Design a six-week Python syllabus with weekly assessments.
  • Expected behavior: Route to curriculum-design because the target is already chosen and the requested output is a sequenced curriculum.
  • Why: Just-in-time target selection should not displace an explicit curriculum-design request.

Completion Checklist

  • At least one confirmation question was answered, no turn contained more than one question, and the shared interview ceiling was respected.
  • Urgency/trigger, current level, application window, and the target statement are explicit before research.
  • Every admitted recommendation is source-gated and popularity signals did not influence admission or rank.
  • Books, Podcasts, Creators, and Courses are present with complete fields or an honest empty-section reason.
  • Competing targets, filtered-out defaults, unresolved gaps, and one starting action are visible.
  • The final status says the brief is prepared and does not claim consumption, learning, application, progress, or blocker resolution.

Recovery Notes

  • If a required readiness dimension remains unclear, ask the one answer that most changes the target while the shared round budget remains.
  • If the shared interview ceiling is reached, proceed with explicit assumptions and gaps rather than asking another question.
  • If sources or links cannot be checked, leave the affected section empty with the retrieval reason instead of adding a generic recommendation.
  • If the target becomes a syllabus, supplied-paper explanation, source inventory, already-scoped research question, or OMH self-improvement request, preserve the sibling boundary and route accordingly.

Workflow Lane

  • Current lane: Research and company ops (product-docs, source-finder, web-research, research, model-optimization, inference-serving, model-finetuning, research-brief, +26 more) - research, signals, ops, and briefings.
  • If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
  • Shared product, routing, compatibility, and evidence rules: skill_view(name='omh-routing', file_path='references/skill-common-rail.md').

When to Use

Use when selecting the highest-leverage immediate learning target for an active blocker before preparing a source-backed Markdown brief for direct application.

Strong routing signals: `jit-learn`, `learn next`, `learn now`, `blocker-specific learning target`, `highest-leverage learning target`, `immediate learning payoff`, `immediately applicable learning brief`, `source-backed learning brief`, `학습 주제`, `도움 되는 학습 주제`, `당장 적용할 학습 목표`, `책 팟캐스트 크리에이터 강의 학습 브리프`

Catalog Metadata

Category: research Phase: learning-target Hermes role: researcher Quality tier: source-gated Reasoning demand: standard

Quality bar:

  • Resolve urgency/trigger, current level, and application window with one question per turn, while stopping early once all three are clear after the mandatory first answer.
  • Confirm one target in the form Learn X now so I can do/decide Y in context Z by T. before source research.
  • Prefer primary, institutional, and credible practitioner sources; rank by specific fit, authority, currency, time-to-first-value, and direct transfer rather than popularity.
  • Keep Books, Podcasts, Creators, and Courses visible even when no candidate passes, and explain every empty section instead of padding it.
  • For each admitted resource, state title, format, creator/publisher, link, source class, time to first value, specific fit, first application, and applicable link/access/currency caveats.
  • Close with competing targets considered, filtered-out defaults, unresolved gaps, and exactly one recommended starting action.

Handoff policy:

Keep reviewed-context interpretation, the bounded one-question-at-a-time interview, target selection, source research, and Markdown brief preparation in Hermes. Do not create a learner profile, take an external action, or claim that a recommendation was consumed, learned, applied, or resolved the blocker.

Required inputs:

  • reviewed context
  • urgency
  • current level
  • application window
  • time/format constraints

Expected outputs:

  • confirmed target statement: Learn X now so I can do/decide Y in context Z by T.
  • source-backed Markdown learning brief
  • Books section, including an explicit no-qualifying-candidate reason when empty
  • Podcasts section, including an explicit no-qualifying-candidate reason when empty
  • Creators section, including an explicit no-qualifying-candidate reason when empty
  • Courses section, including an explicit no-qualifying-candidate reason when empty
  • for every recommendation: title, format, creator/publisher, link, source class, time to first value, specific fit now, first application, and caveats
  • competing learning targets, filtered-out defaults, unresolved gaps, and one recommended next action

Artifact expectations:

  • prepared Markdown learning brief with observed source links and explicit retrieval gaps when a wrapper captures it

Safety rules:

  • Always ask at least one confirmation question before research, exactly one question per turn, even when the initial request appears complete.
  • Use the shared deep-interview ceiling of 6 rounds and its early-stop discipline; do not create a second interview budget.
  • Use only the current conversation and reviewed or explicitly approved OMH context; never claim hidden Hermes memory or create a persistent learner profile.
  • Admit recommendations only from primary, institutional, or credible practitioner evidence whose authority, currency, availability, and link can be checked; report retrieval gaps instead of inventing support.
  • Never use bestseller status, ratings, follower counts, charts, generic popularity, or unsupported reputation as admission or ranking evidence.
  • Do not purchase, download, enroll, subscribe, contact a creator, bypass a paywall, write to an external system, or imply any external action occurred.
  • A prepared brief is not evidence that the user consumed a resource, learned, made progress, applied the advice, or resolved the original blocker.

Just-in-Time Learning Protocol

  1. Review only the current conversation and reviewed or explicitly approved OMH context. Never claim access to hidden Hermes memory and never create a learner profile.
  2. Always ask at least one confirmation question before research, including when the request appears complete. Ask exactly one question per turn. Resolve three readiness dimensions: urgency/trigger (why now), current level (what the user already knows or can do), and application window (where and by when this will be used), plus only practical constraints that change the recommendation. Record this evidence step as confirmation_asked.
  3. Reuse the deep-interview early-stop discipline and its shared ceiling of 6 rounds. After the mandatory first answer, stop asking as soon as the three readiness dimensions are clear. If the ceiling is reached, state assumptions and gaps instead of asking again.
  4. Confirm one target before research in exactly this semantic form: Learn X now so I can do/decide Y in context Z by T. Here T means the application deadline. When the initial request already supplies all readiness dimensions, use the mandatory first question to confirm this target so research can begin after one answer.
  5. Scope research around that target. Prefer primary, institutional, and credible practitioner sources; check authority, currency, availability, and links. Admit and rank by specific fit, authority, currency, time-to-first-value, and direct transfer. Never admit or rank from bestseller status, ratings, followers, charts, generic popularity, or unsupported reputation.
  6. Prepare the Markdown brief, then stop. Do not buy, download, enroll, subscribe, contact creators, bypass access controls, write externally, or imply those actions happened.

Learning Brief Contract

Start with the confirmed target statement and a short source-boundary note. Then render all four headings, even when empty:

  • ## Books
  • ## Podcasts
  • ## Creators
  • ## Courses

Under every heading, list only candidates that passed the source gate. If none passed, say why - for example, insufficient authority, stale or unavailable evidence, poor immediate fit, or an unresolved retrieval gap - rather than padding the section.

For every recommendation include:

  • Title
  • Format
  • Creator/Publisher
  • Link
  • Source class - primary, institutional, or credible practitioner
  • Time to first value
  • Why it fits - why it fits this user, target, level, and application window
  • First immediate application - the first concrete use in the user's present context
  • Link/currency caveat - link, availability, access, or currency limits when applicable

Close with ## Competing Targets Considered, ## Filtered Out, ## Gaps, and ## Next Action. Name the competing learning targets, generic defaults or resources rejected and why, unresolved evidence/context gaps, and exactly one recommended starting action.

The terminal state is learning_brief_prepared: the brief is prepared, not observed learning. Preparation does not prove source consumption, learning, progress, application, effectiveness, or resolution of the original blocker.

Runtime Evidence

Preferred harness for this skill: jit-learn.

omh runtime record --skill jit-learn --harness jit-learn --status started

Record 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 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.

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: skill_view(name='omh-routing', file_path='references/skill-common-rail.md'). Load it when applicable; otherwise name an unavailable capability.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

dag-ulw

免费

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-hermes35752026年10月23日 更新

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-hermes35752026年10月23日 更新

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-hermes35752026年10月23日 更新

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-hermes35752026年10月23日 更新

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-hermes35752026年10月23日 更新

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-hermes35752026年10月23日 更新

查看 rlaope 的全部技能

报告此技能的问题