autoresearch-goal

Name: autoresearch-goal
Author: rlaope

61stars2forks

How to install autoresearch-goal?

rlaope/oh-my-hermes/autoresearch-goal

$npx -y skills add rlaope/oh-my-hermes --skill autoresearch-goal

Installs into the current project.

Summary

[omh] Hermes adaptation for durable research-goal execution.

Files · 1

View on GitHub

SKILL.md

1	# Autoresearch Goal
2
3	This is a Hermes-native `autoresearch-goal` workflow skill.
4
5	## Why This Exists
6
7	`autoresearch-goal` exists to keep `research` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
8
9	## Do Not Use When
10
11	- The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
12	- The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
13
14	## Examples
15
16	Good example:
17
18	- Prompt: autoresearch-goal: keep researching AI agent memory practices until the evidence gaps are closed or logged.
19	- Expected behavior: Run a durable research loop with critic checks, source gaps, and a stop or checkpoint condition.
20	- Why: The request is research that needs persistence and review, not a one-shot brief.
21
22	Bad example:
23
24	- Prompt: autoresearch-goal: treat casual chat or unaccepted work as if this workflow already produced verified results.
25	- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `autoresearch-goal`.
26	- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
27
28	## Completion Checklist
29
30	- The research question, source boundaries, recency assumptions, and confidence level are named.
31	- Observed sources, inference, synthesis, and unresolved retrieval gaps are separated.
32	- Follow-up planning or handoff uses the research summary without calling it execution evidence.
33
34	## Recovery Notes
35
36	- If sources cannot be accessed, state the retrieval gap and use only observed local context.
37	- If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary.
38
39	## OMH Context Rail
40
41	- This skill is part of OMH's Hermes workflow layer, not a standalone executor.
42	- Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries.
43	- Current lane: Research and company ops (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings.
44	- 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.
45	- Cross-skill context: every OMH skill: match lane; generic tool can render or execute.
46	- 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.
47	- Coverage: Every generated workflow skill carries this rail.
48	- Normal users talk to Hermes; OMH CLI is infra.
49	- Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence.
50
51	## Use When
52
53	Use for validator-gated research that needs durable artifacts.
54
55	Strong routing signals: `autoresearch-goal`, `research goal`, `durable research`, `critic research`
56
57	## Catalog Metadata
58
59	Category: `research`
60	Phase: `durable-research`
61	Hermes role: `researcher`
62	Quality tier: `validator-gated`
63
64	Quality bar:
65
66	- Define validator criteria before gathering evidence.
67	- Keep durable research artifacts separate from coding execution evidence.
68	- Stop with next questions or a source-backed synthesis when validation is incomplete.
69
70	Handoff policy:
71
72	Keep durable research in Hermes-managed artifacts; do not convert to executor handoff unless the research produces an accepted coding task.
73
74	Required inputs:
75
76	- research objective
77	- validator criteria
78	- source boundaries
79
80	Expected outputs:
81
82	- research artifact
83	- validator result
84	- next questions
85
86	Artifact expectations:
87
88	- durable research ledger or checklist
89
90	Safety rules:
91
92	- Do not imply hidden Hermes runtime behavior.
93	- Use the smallest verification that can prove the claim.
94
95	## Harness Discipline
96
97	- Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes.
98	- Prefer richer evidence and clearer stop conditions over adding more workflow names.
99	- Use specialist lanes only when they change the quality of the answer or verification.
100
101	## Runtime Evidence
102
103	Preferred harness for this skill: `research`.
104
105	When local shell access or a bot wrapper is available, record metadata-only evidence:
106
107	```s

People who liked this also viewed

6 picks

Type

autoresearch-goal

61stars2forks

View on GitHub

How to install autoresearch-goal?

rlaope/oh-my-hermes/autoresearch-goal

$npx -y skills add rlaope/oh-my-hermes --skill autoresearch-goal

Installs into the current project.

Summary

[omh] Hermes adaptation for durable research-goal execution.

Files · 1

View on GitHub

SKILL.md

1	# Autoresearch Goal
2
3	This is a Hermes-native `autoresearch-goal` workflow skill.
4
5	## Why This Exists
6
7	`autoresearch-goal` exists to keep `research` work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.
8
9	## Do Not Use When
10
11	- The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
12	- The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.
13
14	## Examples
15
16	Good example:
17
18	- Prompt: autoresearch-goal: keep researching AI agent memory practices until the evidence gaps are closed or logged.
19	- Expected behavior: Run a durable research loop with critic checks, source gaps, and a stop or checkpoint condition.
20	- Why: The request is research that needs persistence and review, not a one-shot brief.
21
22	Bad example:
23
24	- Prompt: autoresearch-goal: treat casual chat or unaccepted work as if this workflow already produced verified results.
25	- Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing `autoresearch-goal`.
26	- Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.
27
28	## Completion Checklist
29
30	- The research question, source boundaries, recency assumptions, and confidence level are named.
31	- Observed sources, inference, synthesis, and unresolved retrieval gaps are separated.
32	- Follow-up planning or handoff uses the research summary without calling it execution evidence.
33
34	## Recovery Notes
35
36	- If sources cannot be accessed, state the retrieval gap and use only observed local context.
37	- If evidence is thin or one-sided, lower confidence and ask for a narrower source boundary.
38
39	## OMH Context Rail
40
41	- This skill is part of OMH's Hermes workflow layer, not a standalone executor.
42	- Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries.
43	- Current lane: Research and company ops (`source-finder`, `web-research`, `best-practice-research`, `autoresearch-goal`, `research-brief`, `strategy-brief`, `feedback-triage`, `research-department`, `+6 more`) - research, signals, ops, and briefings.
44	- 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.
45	- Cross-skill context: every OMH skill: match lane; generic tool can render or execute.
46	- 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.
47	- Coverage: Every generated workflow skill carries this rail.
48	- Normal users talk to Hermes; OMH CLI is infra.
49	- Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence.
50
51	## Use When
52
53	Use for validator-gated research that needs durable artifacts.
54
55	Strong routing signals: `autoresearch-goal`, `research goal`, `durable research`, `critic research`
56
57	## Catalog Metadata
58
59	Category: `research`
60	Phase: `durable-research`
61	Hermes role: `researcher`
62	Quality tier: `validator-gated`
63
64	Quality bar:
65
66	- Define validator criteria before gathering evidence.
67	- Keep durable research artifacts separate from coding execution evidence.
68	- Stop with next questions or a source-backed synthesis when validation is incomplete.
69
70	Handoff policy:
71
72	Keep durable research in Hermes-managed artifacts; do not convert to executor handoff unless the research produces an accepted coding task.
73
74	Required inputs:
75
76	- research objective
77	- validator criteria
78	- source boundaries
79
80	Expected outputs:
81
82	- research artifact
83	- validator result
84	- next questions
85
86	Artifact expectations:
87
88	- durable research ledger or checklist
89
90	Safety rules:
91
92	- Do not imply hidden Hermes runtime behavior.
93	- Use the smallest verification that can prove the claim.
94
95	## Harness Discipline
96
97	- Start from the representative harness registry in `oh-my-hermes` when the workflow needs coding, research, planning, goal execution, architecture, critique, QA, or documentation lanes.
98	- Prefer richer evidence and clearer stop conditions over adding more workflow names.
99	- Use specialist lanes only when they change the quality of the answer or verification.
100
101	## Runtime Evidence
102
103	Preferred harness for this skill: `research`.
104
105	When local shell access or a bot wrapper is available, record metadata-only evidence:
106
107	```s

People who liked this also viewed

6 picks

Type