Source Finder
This is a Hermes-native source-finder workflow skill.
Why This Exists
source-finder exists so Hermes can turn vague source discovery requests into typed candidates, acquisition status, and downstream workflow choice without pretending OMH searched, downloaded, or verified the material.
Do Not Use When
- The requested output is factual findings, comparison, or a summary rather than a typed candidate inventory and acquisition status; use
research.
- The user needs a business decision brief with evidence-versus-inference treatment; use
research-brief.
- The user asks for current citations, fact-finding, or source-backed synthesis; use
research.
- The user supplies a paper/PDF/arXiv/DOI/excerpt and wants explanation; use
paper-learning.
- The user asks for recurring monitoring, source inbox, or Scout/Analyst/Briefer operations; use
research-department.
- The user asks to export, convert, render, package, or attach a file; use
materials-package or deliverable-package.
- The user asks for an image card or visual summary; use
img-summary.
Examples
Good example:
- Prompt: source-finder find papers, datasets, and GitHub repos for evaluating browser agent benchmarks.
- Expected behavior: Prepare source_finder_plan/v1 with typed candidates, acquisition states, missing observed evidence, and downstream choices.
- Why: The user needs source candidates before deciding whether to learn, research, package, or implement.
Bad example:
- Prompt: source-finder find current citations and summarize what the sources say.
- Expected behavior: Route to
research because the user asks for current evidence and synthesis, not candidate acquisition status.
- Why: Source-finder prepares acquisition lifecycle metadata; research owns current evidence synthesis.
Completion Checklist
- Source kinds, source boundaries, and downstream intent are named.
- Each candidate has a source_candidate/v1 shape and acquisition state.
- Observed states include provenance before being treated as evidence.
- The next downstream workflow is recommended without claiming it ran.
- Search, download, clone, extraction, hash, license, verification, and downstream processing gaps are explicit.
Recovery Notes
- If the user asks for facts or citations, route to
research.
- If a candidate lacks a link or file reference, keep it candidate_prepared and ask for the next observable source step.
- If the user wants to process a selected source, route to the downstream workflow instead of continuing source acquisition.
Workflow Lane
- Current lane: Research and company ops (
product-docs, source-finder, web-research, research, best-practice-research, autoresearch-goal, model-optimization, inference-serving, +19 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:
omh-routing/references/skill-common-rail.md.
Use When
Use when the requested output is a typed source candidate inventory and acquisition status across papers, web links, datasets, GitHub repositories, public presentations, docs/specs, or unknown source material before choosing paper-learning, research, research-brief, research-department, materials-package, or an ultrawork delivery cycle.
Strong routing signals: `source-finder`, `source finder`, `source acquisition`, `source intake`, `find papers and datasets`, `find datasets and repos`, `find papers`, `find arxiv link`, `find arxiv paper`, `find datasets`, `find github repos`, `find oss repos`, `find presentations`, `find public slides`, `find docs and specs`, `find source candidates`, `download candidate`, `source candidate`, `acquisition status`, `자료 후보`, `출처 후보`, `arxiv 링크`, `arxiv 링크 찾아`, `논문 데이터셋 찾아`, `깃허브 저장소 찾아`, `공개 발표자료 찾아`, `문서 스펙 찾아`
Catalog Metadata
Category: research
Phase: source-acquisition
Hermes role: researcher
Quality tier: source-acquisition-gated
Reasoning demand: standard
Quality bar:
- Name source kinds from: paper, web_link, dataset, github_repo, presentation, docs_spec, unknown.
- Record acquisition state from: candidate_prepared, link_observed, download_link_prepared, download_observed, file_hash_recorded, text_extraction_observed, license_checked, verification_observed, downstream_selected.
- Separate candidate preparation, observed link, observed download, file hash, text extraction, license check, verification, and downstream selection.
- Attach observation provenance before treating any acquisition state as evidence.
- Vary search angles across official docs, academic work, implementations, datasets, and criticism until each requested source kind has candidates or another angle change adds nothing new.
- Recommend the next downstream workflow without pretending that downstream work already ran.
Handoff policy:
Keep source acquisition planning in Hermes. Do not claim search, download, clone, extraction, license check, verification, or downstream processing unless a wrapper or user records observed evidence.
Required inputs:
- source target or topic
- desired source kinds
- source boundaries or exclusion criteria
- downstream intent when known
Expected outputs:
- source_finder_plan/v1
- source_candidate/v1
- source_candidate_set/v1
- source_acquisition_status/v1
- downstream workflow recommendation
- not-evidence boundary
Artifact expectations:
- source_finder_plan/v1 under .omh/source-finder when a wrapper or CLI records it
Safety rules:
- Do not claim web search, download, repository clone, file extraction, file hash verification, license verification, or source correctness from a prepared candidate.
- Do not redefine research-department's source_inbox/v1; source-finder owns source_candidate_set/v1 and source_acquisition_status/v1 only.
- Route current citations and source-backed synthesis to
research, supplied-paper explanation to paper-learning, recurring monitoring to research-department, file export to materials-package, and image cards to img-summary.
Runtime Evidence
Preferred harness for this skill: source-finder.
omh runtime record --skill source-finder --harness source-finder --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.
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: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.
1---2name: omh-source-finder3description: [omh] Source candidate inventory - prepare typed source candidates and acquisition status before downstream work; use ulw-research to fetch and cite them, or research-brief to turn them into a decision-ready brief. Use when the user says: source-finder, source finder, source acquisition, source intake, find papers and datasets, find datasets and repos, find papers, find arxiv link.4---5
6# Source Finder
7
8This is a Hermes-native `source-finder` workflow skill.
9
10## Why This Exists
11
12`source-finder` exists so Hermes can turn vague source discovery requests into typed candidates, acquisition status, and downstream workflow choice without pretending OMH searched, downloaded, or verified the material.
13
14## Do Not Use When
15
16- The requested output is factual findings, comparison, or a summary rather than a typed candidate inventory and acquisition status; use `research`.
17- The user needs a business decision brief with evidence-versus-inference treatment; use `research-brief`.
18- The user asks for current citations, fact-finding, or source-backed synthesis; use `research`.
19- The user supplies a paper/PDF/arXiv/DOI/excerpt and wants explanation; use `paper-learning`.
20- The user asks for recurring monitoring, source inbox, or Scout/Analyst/Briefer operations; use `research-department`.
21- The user asks to export, convert, render, package, or attach a file; use `materials-package` or `deliverable-package`.
22- The user asks for an image card or visual summary; use `img-summary`.
23
24## Examples
25
26Good example:
27
28- Prompt: source-finder find papers, datasets, and GitHub repos for evaluating browser agent benchmarks.
29- Expected behavior: Prepare source_finder_plan/v1 with typed candidates, acquisition states, missing observed evidence, and downstream choices.
30- Why: The user needs source candidates before deciding whether to learn, research, package, or implement.
31
32Bad example:
33
34- Prompt: source-finder find current citations and summarize what the sources say.
35- Expected behavior: Route to `research` because the user asks for current evidence and synthesis, not candidate acquisition status.
36- Why: Source-finder prepares acquisition lifecycle metadata; research owns current evidence synthesis.
37
38## Completion Checklist
39
40- Source kinds, source boundaries, and downstream intent are named.
41- Each candidate has a source_candidate/v1 shape and acquisition state.
42- Observed states include provenance before being treated as evidence.
43- The next downstream workflow is recommended without claiming it ran.
44- Search, download, clone, extraction, hash, license, verification, and downstream processing gaps are explicit.
45
46## Recovery Notes
47
48- If the user asks for facts or citations, route to `research`.
49- If a candidate lacks a link or file reference, keep it candidate_prepared and ask for the next observable source step.
50- If the user wants to process a selected source, route to the downstream workflow instead of continuing source acquisition.
51
52## Workflow Lane
53
54- Current lane: **Research and company ops** (`product-docs`, `source-finder`, `web-research`, `research`, `best-practice-research`, `autoresearch-goal`, `model-optimization`, `inference-serving`, `+19 more`) - research, signals, ops, and briefings.
55- If intent belongs to another lane, hand back to `oh-my-hermes` or name the adjacent workflow.
56- Shared product, routing, compatibility, and evidence rules: `omh-routing/references/skill-common-rail.md`.
57
58## Use When
59
60Use when the requested output is a typed source candidate inventory and acquisition status across papers, web links, datasets, GitHub repositories, public presentations, docs/specs, or unknown source material before choosing paper-learning, research, research-brief, research-department, materials-package, or an ultrawork delivery cycle.
61
62 Strong routing signals: `source-finder`, `source finder`, `source acquisition`, `source intake`, `find papers and datasets`, `find datasets and repos`, `find papers`, `find arxiv link`, `find arxiv paper`, `find datasets`, `find github repos`, `find oss repos`, `find presentations`, `find public slides`, `find docs and specs`, `find source candidates`, `download candidate`, `source candidate`, `acquisition status`, `자료 후보`, `출처 후보`, `arxiv 링크`, `arxiv 링크 찾아`, `논문 데이터셋 찾아`, `깃허브 저장소 찾아`, `공개 발표자료 찾아`, `문서 스펙 찾아`
63
64## Catalog Metadata
65
66Category: `research`
67Phase: `source-acquisition`
68Hermes role: `researcher`
69Quality tier: `source-acquisition-gated`
70Reasoning demand: `standard`
71
72Quality bar:
73
74- Name source kinds from: paper, web_link, dataset, github_repo, presentation, docs_spec, unknown.
75- Record acquisition state from: candidate_prepared, link_observed, download_link_prepared, download_observed, file_hash_recorded, text_extraction_observed, license_checked, verification_observed, downstream_selected.
76- Separate candidate preparation, observed link, observed download, file hash, text extraction, license check, verification, and downstream selection.
77- Attach observation provenance before treating any acquisition state as evidence.
78- Vary search angles across official docs, academic work, implementations, datasets, and criticism until each requested source kind has candidates or another angle change adds nothing new.
79- Recommend the next downstream workflow without pretending that downstream work already ran.
80
81Handoff policy:
82
83Keep source acquisition planning in Hermes. Do not claim search, download, clone, extraction, license check, verification, or downstream processing unless a wrapper or user records observed evidence.
84
85Required inputs:
86
87- source target or topic
88- desired source kinds
89- source boundaries or exclusion criteria
90- downstream intent when known
91
92Expected outputs:
93
94- source_finder_plan/v1
95- source_candidate/v1
96- source_candidate_set/v1
97- source_acquisition_status/v1
98- downstream workflow recommendation
99- not-evidence boundary
100
101Artifact expectations:
102
103- source_finder_plan/v1 under .omh/source-finder when a wrapper or CLI records it
104
105Safety rules:
106
107- Do not claim web search, download, repository clone, file extraction, file hash verification, license verification, or source correctness from a prepared candidate.
108- Do not redefine research-department's source_inbox/v1; source-finder owns source_candidate_set/v1 and source_acquisition_status/v1 only.
109- Route current citations and source-backed synthesis to `research`, supplied-paper explanation to `paper-learning`, recurring monitoring to `research-department`, file export to `materials-package`, and image cards to `img-summary`.
110
111## Runtime Evidence
112
113Preferred harness for this skill: `source-finder`.
114
115```sh
116omh runtime record --skill source-finder --harness source-finder --status started
117```
118
119Record observed delegation results; otherwise return `not_available` or `not_observed`.
120Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.
121- Treat wrapper memory/context summaries as advisory local context, not proof of opaque Hermes memory reads or changes.
122Preserve workflow intent and stop conditions; verify before claiming completion.
123
124Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.
125
126Shared product, compatibility, topology, memory, harness, and execution rules: `omh-routing/references/skill-common-rail.md`. Load it when applicable; otherwise name an unavailable capability.
rlaope