AGENT SKILL

deep-research

Use when the user asks for thorough research, source-backed synthesis, market or technical landscape analysis, or an evidence-based brief.

License 许可
MIT
所属仓库
TehutiRaEl/THEHIVE
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
deep-research
description
Use when the user asks for thorough research, source-backed synthesis, market or technical landscape analysis, or an evidence-based brief.

03 SKILL.md 正文

Deep Research

Use this Skill to perform a thorough, source-backed investigation with the tools and files available in the current harness. Work directly with the current tools, Skills, and filesystem.

When to use

Activate for requests that need sustained investigation, source comparison, market or technical landscape analysis, evidence-backed recommendations, or a polished research brief. For quick factual lookups, answer with normal search instead.

Workflow

  1. Clarify the research question, scope, time horizon, geography, audience, and decision to support only when those are missing and materially affect the work.
  2. For broad or high-stakes requests, write a short research plan before executing. Include the main search angles, likely source types, and how you will handle internal vs. public information.
  3. Route sources deliberately:
    • Public or current information: use web search; use news search for recent news or media coverage; open strong results to read the source more deeply.
    • Internal, private, company, project, or workspace-specific information: load internal-search if available, inspect the relevant tool definitions, and use connected integrations or document-library sources instead of public web.
    • User-provided files or canvases: read the relevant files directly before searching elsewhere.
  4. Search iteratively. Start broad to map the topic, then run targeted searches for primary sources, conflicting perspectives, recent developments, and gaps. Do not stop at snippets when the source matters.
  5. Keep evidence organized as you work: source title, URL or internal reference, date when relevant, source type, key claims, and reliability notes.
  6. Cross-check important claims across multiple sources. Prefer primary sources, official documentation, research papers, standards, regulatory text, company filings, and original datasets over summaries.
  7. Synthesize by theme and decision relevance, not by search order. Separate verified facts, estimates, opinions, and your own inference.

Source Standards

  • Cite claims that carry the answer.
  • Note source dates for fast-moving topics.
  • Name conflicts, uncertainty, stale evidence, and missing access.
  • Do not cite a source you have not actually inspected when the claim depends on details beyond the snippet.
  • For internal sources, preserve confidentiality and cite only in the format supported by the available tool results.

Output

Finish by creating a canvas with the research report. Use the canvas Skill to choose the right canvas type; default to a text/markdown report unless the user asked for slides, a dashboard, a table, or another format. The canvas should be self-contained and polished enough for the user to inspect, edit, or share.

Recommended report structure:

  • Question: the interpreted research goal.
  • Executive Summary: 3-7 ranked takeaways.
  • Methodology: search angles, source types, and important limitations.
  • Findings: evidence-backed sections organized by theme.
  • Source Notes: source quality, conflicts, and caveats.
  • Open Questions: uncertainties, gaps, or disputed claims.
  • Recommendations / Next Steps: what to decide, test, read, or do next.

After creating the canvas, send only a brief chat message that summarizes the top finding and points the user to the canvas. Do not paste the full report into chat.

04 同仓库更多 Skills

TehutiRaEl
TehutiRaEl/THEHIVE

preamble-gate

Use BEFORE doing any work in this repo — before the first file edit, commit, push, PR, branch operation, workflow dispatch, scheduled trigger or timer, agent/subagent spawn, dependency install, or message sent to an outside service. Forces a plain-language preamble to the founder first: WHAT you are about to do, WHY, HOW, why it is NECESSARY, the PROJECTED IMPROVEMENT, and the COST and RISK — then, for consequential work (governance, security, money, CI/triggers, rewriting history, multi-agent fan-out), waits for an explicit go-ahead. Read-only investigation (reading files, grep, git log/diff, answering questions) is exempt. Applies to every AI that works in this repo, not just Claude. Founder rule, 2026-11-10, written after an unattended automation ran up cost and froze the hive. Not a substitute for wired-or-not (which governs how completion is CLAIMED); this governs what happens BEFORE work starts.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

visionary-recommender

暂无简介

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

syllabus

Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

research

Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., "research [topic]", "look into [topic]", "what do we know about [topic]", "investigate [topic]", "find me information on [topic]", "do some research on [topic]", "I need to understand [topic]"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

pulse

Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.

★ 0
TehutiRaEl
TehutiRaEl/THEHIVE

patent

Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.

★ 0