Agent skill

Behive Research

by qa10devteam in qa10devteam/behive

A skill your agent uses when the user asks to research a topic deeply, gather intelligence, or build a knowledge base.

MITAuto-check passedKnowledge Management

Install Behive Research

skills CLI
$ npx skills add qa10devteam/behive --skill behive-research -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install qa10devteam/behive behive-research --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/qa10devteam/behive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/integrations/hermes .claude/skills/behive-research && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
behive-research
GitHub stars
146
Token cost
~1.4k tokens
SKILL.md length
510 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when the user asks to research a topic deeply, gather intelligence, or build a knowledge base.

  • Works in 5 steps: Decomposes topics into research axes → Fetches 1000+ sources via 8-layer… → Extracts typed claims with per-claim… → …
  • The user asks to research a topic deeply
  • SKILL.md covers Overview, When to Use, Don't Use For and Prerequisites, plus 8 more sections
  • Calls curl and jq

What it does

Behive Research is an agent skill from qa10devteam/behive. Use when the user asks to research a topic deeply, gather intelligence, or build a knowledge base. Connects to BeHive API (self-hosted or cloud) to run multi-source research missions with structured claim extraction, quality scoring, and knowledge graph construction.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Knowledge Management, covering Deep research, Knowledge graphs and Knowledge bases. It works with Model Context Protocol. The repository describes itself as: Open-source deep research engine that builds structured knowledge graphs. MCP-native. avg 0.82+ quality. The licence is MIT.

When your agent uses it

  • The user asks to research a topic deeply
  • Gather intelligence
  • Build a knowledge base

Example prompts

  • “/behive-research”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Decomposes topics into research axes
  2. Fetches 1000+ sources via 8-layer stealth drones (70+ APIs)
  3. Extracts typed claims with per-claim quality scores (0.0–1.0)
  4. Builds entity relationship graphs (Neo4j)
  5. Produces synthesized reports with inline citations

What it can do on your machine

Read from SKILL.md and the folder at commit 91e9a64. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use curl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Behive Research loads about 1.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 510 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qa10devteam/behive at commit 91e9a64, republished under its MIT licence (© qa10devteam). 510 words, ~1,434 tokens.

Download SKILL.mdSave it as .claude/skills/behive-research/SKILL.md (or your agent's skills folder).
name
behive-research
description
Use when the user asks to research a topic deeply, gather intelligence, or build a knowledge base. Connects to BeHive API (self-hosted or cloud) to run multi-source research missions with structured claim extraction, quality scoring, and knowledge graph construction.
version
1.0.0
author
QA10
license
MIT

BeHive Deep Research

Overview

BeHive is a deep research engine that extracts structured, scored claims from any topic. Unlike simple web search, it:

  1. Decomposes topics into research axes
  2. Fetches 1000+ sources via 8-layer stealth drones (70+ APIs)
  3. Extracts typed claims with per-claim quality scores (0.0–1.0)
  4. Builds entity relationship graphs (Neo4j)
  5. Produces synthesized reports with inline citations

This skill connects Hermes Agent to a running BeHive instance.

When to Use

  • User says "research X deeply", "gather intelligence on Y", "find everything about Z"
  • User needs verified facts with sources, not LLM-generated summaries
  • User wants claims they can cite, filter by quality, or query later
  • User asks to build a knowledge base on a topic over time
  • User says "run a mission on X", "scale 100", "deep dive"

Don't Use For

  • Simple factual lookups (use web_search)
  • Single-page content extraction (use web_extract)
  • Real-time news (BeHive takes 5-15 min per mission)

Prerequisites

BeHive API running at http://localhost:8091 or configured endpoint.

Verify:

bash
curl -s http://localhost:8091/health | jq .

If using MCP (recommended), configure in ~/.hermes/config.yaml:

yaml
mcp_servers:
  behive:
    url: http://localhost:8090/mcp
    transport: streamable-http

Quick Research (MCP)

If BeHive MCP is configured, use MCP tools directly:

mcp_behive_research_topic(request={"query": "NVIDIA GPU market 2025-2026", "depth": 3, "force": true})

Then poll:

mcp_behive_mission_status(job_id="<returned_id>")

Get report:

mcp_behive_get_report(job_id="<id>", format="markdown")

Search past knowledge:

mcp_behive_search_knowledge(query="NVIDIA revenue", limit=20)

Research via REST API (terminal)

Start a Mission
bash
curl -s -X POST http://localhost:8091/research \
  -H "Content-Type: application/json" \
  -d '{"topic": "EU AI Act enforcement mechanisms 2026", "scale": 30, "depth": 3}' | jq .

Scale guide:

  • 15 — quick scout (2-3 min, ~50 claims)
  • 30 — standard (5-10 min, ~200-500 claims)
  • 100 — deep (15-30 min, ~800+ claims)
  • 300 — exhaustive (45-90 min, ~2000+ claims)
Poll Status
bash
curl -s http://localhost:8091/research/<mission_id> | jq .status,.phase,.progress

Phases: scout → harvest → process → synth → done

Get Report
bash
curl -s http://localhost:8091/research/<mission_id>/report | jq .
Search Claims
bash
curl -s "http://localhost:8091/search?q=NVIDIA+revenue&limit=20" | jq .
List Missions
bash
curl -s http://localhost:8091/missions | jq '.[] | {id, topic, status, avg_quality, total_claims}'
SSE Streaming (real-time progress)
bash
curl -N http://localhost:8091/research/<mission_id>/events

Returns Server-Sent Events with phase transitions, progress %, and claim counts.

Quality Interpretation

Score RangeMeaningAction
0.85–1.00Excellent — specific, verified, multi-dimensionalTrust directly
0.75–0.84Good — solid claim with evidenceUse with confidence
0.65–0.74Acceptable — valid but may lack specificsVerify key details
0.55–0.64Marginal — passed quality gate barelyCross-reference
< 0.55Rejected — never enters databaseN/A

Knowledge Graph Queries

bash
# Get entities
curl -s "http://localhost:8091/graph/entities?limit=50" | jq .

# Get relationships for an entity
curl -s "http://localhost:8091/graph/entity/NVIDIA/relationships" | jq .

# Network stats
curl -s http://localhost:8091/intelligence/stats | jq .
Show full SKILL.md (211 more words)Show less

Workflow: Research → Report → Deliver

  1. Start mission with appropriate scale
  2. Monitor via SSE or polling (every 30s)
  3. On completion, fetch report
  4. Format key findings for user
  5. Offer to search specific claims or explore the knowledge graph

Common Pitfalls

  1. Using web_extract on localhost — Hermes blocks private IPs via web_extract. Always use terminal() + curl for BeHive API calls.
  2. Scale too high for simple topics — Scale 30 is sufficient for most queries. Scale 300 takes 45+ minutes and may hit rate limits.
  3. Not waiting for completion — Missions are async. Always poll or stream until status=done.
  4. Confusing mission_id formats — IDs look like hive_1785227949_815112. Copy exactly from the start response.
  5. Expecting real-time results — Even scale 15 takes 2-3 minutes. Set user expectations.

Benchmarks (real, honest)

TopicClaimsAvg QualityDurationSources
NVIDIA GPU market 20252900.7978 min234
OpenAI GPT-5 capabilities5740.78912 min174
EU AI Act enforcement2670.7596 min130
Meta Llama 45680.82111 min198

Hardware: EC2 g6.24xlarge, 4× NVIDIA L4, Bedrock Claude Haiku + Sonnet.

Verification Checklist

  • curl http://localhost:8091/health returns 200
  • MCP configured in config.yaml (if using MCP path)
  • Mission started and job_id captured
  • Status polled until done or error
  • Report delivered to user in readable format

© qa10devteam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in integrations/hermes of qa10devteam/behive.

Open the folder on GitHubat commit 91e9a64

Compare with similar skills

Behive Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Behive Research compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Behive Research this skillqa10devteam/behive146—~1.4kAutomated safety check: PassMIT
Askagenticnotetaking/arscontexta3.5k1 repos~5.7kAutomated safety check: PassMIT
Engraphdevwhodevs/engraph171—~792Automated safety check: PassMIT
LLM Wiki Knowledge GraphEgonex-AI/Understand-Anything85k1 repos~1.5kAutomated safety check: PassMIT
Learnagenticnotetaking/arscontexta3.5k1 repos~1.9kAutomated safety check: NotesMIT
NotebookLM Research Workflowclaude-world/notebooklm-skill463—~1.8kAutomated safety check: PassMIT

Similar skills

  • Ask

    agenticnotetaking/arscontexta

    Query the bundled research knowledge graph for methodology guidance.

    3.5k GitHub starsUsed in 1 repo~5.7k tokens
    Knowledge ManagementAuto-check passed
  • Engraph

    devwhodevs/engraph

    Index and search document collections using hybrid semantic + graph + full-text search.

    171 GitHub stars~792 tokensUpdated 4 mo ago
    Knowledge ManagementAuto-check passed
  • LLM Wiki Knowledge Graph

    Egonex-AI/Understand-Anything

    Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.

    85k GitHub starsUsed in 1 repo~1.5k tokens
    Knowledge ManagementAuto-check passed
  • Learn

    agenticnotetaking/arscontexta

    Research a topic and grow your knowledge graph. An agent skill from agenticnotetaking/arscontexta.

    3.5k GitHub starsUsed in 1 repo~1.9k tokens
    Knowledge ManagementAuto-check: notes
  • NotebookLM Research Workflow

    claude-world/notebooklm-skill

    Creates NotebookLM notebooks from URLs, text and files, asks cited questions, runs web research and generates audio, slides, quizzes and other artifacts.

    463 GitHub stars~1.8k tokensUpdated 2 mo ago
    Knowledge ManagementAuto-check passed
  • Arkon Edit

    nduckmink/arkon

    Propose or directly apply edits to Arkon wiki pages, including proposing brand new pages.

    1.5k GitHub stars~1.6k tokensUpdated 4 mo ago
    Knowledge ManagementAuto-check passed

More from qa10devteam/behive

  • Behive Research

    qa10devteam/behive

    Deep research missions with structured claim extraction, quality scoring, and knowledge graphs.

    146 GitHub stars~838 tokensUpdated 2 days ago
    Auto-check: notes

Questions about Behive Research

What does Behive Research do?

A skill your agent uses when the user asks to research a topic deeply, gather intelligence, or build a knowledge base. Behive Research is an agent skill from qa10devteam/behive. Use when the user asks to research a topic deeply, gather intelligence, or build a knowledge base.

When should I use Behive Research?

Behive Research fits situations like: the user asks to research a topic deeply; gather intelligence; build a knowledge base.

How do I install Behive Research in Claude Code?

Run `npx skills add qa10devteam/behive --skill behive-research -a claude-code`. Or copy the skill folder (integrations/hermes in qa10devteam/behive) into .claude/skills/behive-research in your project. Claude Code loads it when a task matches its description.

How do I install Behive Research in Codex?

Run `npx skills add qa10devteam/behive --skill behive-research -a codex`. Or copy the skill folder (integrations/hermes in qa10devteam/behive) into .agents/skills/behive-research in your project. Codex loads it when a task matches its description.

Can I use Behive Research in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qa10devteam/behive --skill behive-research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/behive-research, .gemini/skills/behive-research, .github/skills/behive-research and .opencode/skills/behive-research in your project.

What does Behive Research need to run?

Going by SKILL.md and its folder, Behive Research needs the command-line tools its instructions call (curl and jq).

Does Behive Research access the network?

SKILL.md contains no URLs. Its commands use curl, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Behive Research safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Behive Research use?

Behive Research is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Behive Research use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Behive Research?

Skills that share tags, products or a category with Behive Research: Ask (agenticnotetaking/arscontexta, 3.5k stars), Engraph (devwhodevs/engraph, 171 stars), LLM Wiki Knowledge Graph (Egonex-AI/Understand-Anything, 85k stars) and Learn (agenticnotetaking/arscontexta, 3.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Behive Research?

qa10devteam (a GitHub user) maintains it in qa10devteam/behive, which has 146 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.

Source: qa10devteam/behive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.