Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rlaope/ulw-research
[omh] Web research with citation discipline on top of native search - every claim carries a live URL and unfetched claims stay not observed; for a decision-ready brief use research-brief, and for ongoing Scout/Analyst/Briefer coordination use research-department.
Passed 8 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
5 fixed6 passed either way11 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before drafting our system spec, I need a deep research breakdown comparing open-source queue engines like Celery, BullMQ, and Temporal. Please examine their internal mechanisms, tradeoffs, and licenses, referencing specific commits or version tags where relevant. Give me a decision-oriented dossier listing key evaluation criteria, recommended versus rejected options with rationales, potential risks, and a clear distinction between confirmed facts and open uncertainties.
| Checked | Without skill | With skill |
|---|---|---|
| Includes pinned version tag or commit references for each studied queue engine. | Missed | Passed |
| Contains a verified-claims ledger with an annex for unresolved claims. | Missed | Passed |
| Includes a plan-feed block listing decision drivers, viable options, and rejected candidates. | Missed | Passed |
The instructions your model reads when the skill loads.
This is a Hermes-native research workflow skill.
research exists to make Hermes a careful research engine: it routes research demands to source-backed evidence gathering - from live web citations to studied reference implementations - verifies contested claims, and distills decision-grounding output so planning starts from evidence instead of guesses.
ultrawork (its delivery_boundary capability) or a planning workflow after research instead.codebase-onboarding.source-finder.research-brief.research-department.best-practice-research.Good example:
Bad example:
codebase-onboarding because the study target is this repository, not external sources or reference implementations.test cases passed, vs 4 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.