원클릭으로
researcher
Autonomous deep researcher -- exhaustive investigation, cross-referencing, fact-checking, and structured reports
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Autonomous deep researcher -- exhaustive investigation, cross-referencing, fact-checking, and structured reports
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Author one loop-harness planning ticket in the format the implement-ticket loop consumes. Use when asked to plan a feature, scope a change, draft a ticket, or turn a described problem into a ticket the loop can run. Writes one ticket file to the configured plans directory.
Run one planning ticket through the loop lifecycle - perceive (ledger + git reconcile), implement tests-first, gate via `loopctl stamp`, self-review, adversarial review, commit, close via `loopctl finish`. Use when asked to implement the next ticket, run the loop, or continue autonomous ticket implementation.
Generate static artwork/illustrations for a repo with Nano Banana Pro (aka "nano banana", Gemini 3 Pro Image) via the bundled generate_art.py — craft a detailed prompt, run the script, view the result, iterate. Use this whenever the user wants to create, generate, or regenerate a visual asset for a project: an architecture diagram, portrait, card/illustration, icon, splash, or any image that lands as a PNG in the repo — even if they don't name the tool or just say "make me an image / a picture of X". Do NOT trigger for application runtime image needs, or for editing source code rather than producing an image file.
Remove a solid background from an image and write a transparent PNG, using the bundled remove_background.py. Use this whenever the user wants to knock out, drop, or make transparent the background of a logo, banner, icon, or other static image asset in a repo, or to trim an asset to its content and pad it. Pairs with generate-art: generate a flat asset, then key its background here. Do NOT trigger for photo cutouts needing subject segmentation, for runtime image processing, or for editing source code rather than an image file.
Teach the user a new codebase, technology, framework, or system by walking through it from high-level architecture down to implementation details using a paginated, layered approach. Use this skill whenever the user wants to understand how something works, needs onboarding onto a new technology, asks you to explain a system end-to-end, or says things like "walk me through", "explain how X works", "I need to learn X", "teach me", or "help me understand". Also use when the user shares documentation and asks to be taught from it.
Write or refactor project documentation — tutorials, how-to guides, reference pages, and explanation articles — using the Diátaxis framework. Enforces strict mode purity (a tutorial is not a how-to is not a reference is not an explanation), Orwell's six rules for clear prose, and a ladder-of-abstraction rhythm where concrete examples open and close each piece. Targets HUMAN readers — not agents — so emphasizes plain, everyday English over jargon. Use whenever the user asks to write, draft, refactor, edit, improve, or polish documentation — phrases like "write a tutorial", "draft a how-to", "turn this into a reference", "document this feature", "rewrite this doc", "improve the README", "add user docs", "document the API", "explain how X works for newcomers", or any task that produces user-facing prose for a software project. Triggers even when the user does not say "Diátaxis" explicitly — any doc-writing or doc-refactoring task gets this lens.
| name | researcher |
| description | Autonomous deep researcher -- exhaustive investigation, cross-referencing, fact-checking, and structured reports |
| version | 1.1.0 |
| metadata | {"hermes":{"tags":["productivity","research","fact-checking","reports"],"category":"productivity"}} |
Activate when asked to investigate a topic, answer a complex question, or produce a research report. Supports configurable depth (quick/thorough/exhaustive), output style (brief/detailed/executive), and source verification.
quick (5-10 sources, 1 pass), thorough (20-30 sources, cross-referenced), or exhaustive (50+ sources, multi-pass, fact-checked). Default: thorough.brief (executive summary), detailed (structured report), or executive (findings + recommendations). Default: brief.true.30.inline_url, footnotes, or numbered. Default: inline_url.memex_*). Do not shell out to curl.Use Memex for state and persistence -- not in-memory storage:
app:hermes:researcher:*):memex_kv_get(key="app:hermes:researcher:{key}")
memex_kv_write(key="app:hermes:researcher:{key}", value="...")
memex_memory_search(query="...") # individual facts/observations across notes
memex_note_search(query="...") # whole notes ranked by relevance
memex_list_entities(query="{topic}")
memex_get_entity_cooccurrences(entity_id="...")
memex_get_entity_mentions(entity_id="...")
Before starting research, ALWAYS search Memex first -- the answer may already exist.
When you receive a research question:
research_depth.For each sub-question, construct 3-5 search queries:
For each search query:
web_search to collect results.web_fetch on promising sources to extract key claims, data points, dates, author credentials.Source quality (CRAAP test): Currency, Relevance, Authority, Accuracy, Purpose. Score: A (authoritative), B (reliable), C (useful), D (weak), F (unreliable).
Continue until source count matches research_depth setting.
If source_verification is enabled:
Synthesis: group by sub-question, identify consensus, minority views, and gaps.
For critical claims:
Format based on output_style. Always include:
Save report to Memex with tags researcher, report, plus topic tags. Use vault_id="inbox" -- the sorting-hat will route it to the correct vault:
memex_retain(
title="Research Report: {topic}",
author="researcher",
description="...",
tags=["researcher", "report", ...topic_tags],
markdown_content=$REPORT_MARKDOWN,
vault_id="inbox",
background=True
)
Capture the returned note id into NOTE_ID for reference.
Update KV counters:
memex_kv_write(key="app:hermes:researcher:queries_solved", value="...")
memex_kv_write(key="app:hermes:researcher:sources_cited", value="...")
memex_kv_write(key="app:hermes:researcher:reports_generated", value="...")
app:hermes:researcher: -- do not use the old app:openfang:researcher: prefix.