dossier-collect

Builds graph-structured dossiers on seed entities via recursive parallel fan-out across web, memory, and codebase sources.

70.1k|8.4k|Updated Jun 2, 2025
One-click install
npx skills add https://github.com/ruvnet/claude-flow --skill dossier-collect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dossier-collect
Source: https://github.com/ruvnet/claude-flow/tree/main/plugins/ruflo-goals/skills/dossier-collect
Command: npx skills add https://github.com/ruvnet/claude-flow --skill dossier-collect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigating an entity (a username, file, symbol, ADR, URL, or concept) usually means manually querying many sources and stitching results together. This Skill automates recursive, multi-source entity expansion and produces a provenance-tracked graph dossier instead of a one-off answer.

Core Features & Use Cases

  • Parallel fan-out investigation: Issues all source queries (WebSearch, WebFetch, Grep, Glob, memory search, embeddings search) in a single round, then recurses breadth-first up to a configurable depth and breadth.
  • Graph output with provenance: Aggregates results into a nodes/edges graph where every node and edge records its source and confidence, rendered as both a Markdown report with a mermaid diagram and a machine-readable JSON file.
  • Budget and dedup discipline: Supports cost budgets with explicit truncation marking, plus exact and embedding-similarity-based entity deduplication.
  • Use Case: Run it on a GitHub username to map owned repositories, related contributors, and linked concepts, or on an ADR identifier to trace every file and decision referencing it.

Quick Start

Ask the agent to build a dossier on the seed 'ruvnet' with a maximum depth of 2 and a budget of one dollar.

Frequently Asked Questions about dossier-collect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a dossier on a username or entity?

Invoke the skill with the seed value, for example a GitHub username, and it auto-detects the seed type, fans out queries across web, memory, and code sources, then recurses on discovered entities. The result is a Markdown report and JSON graph saved under the dossiers output directory.

What sources does recursive entity investigation search?

It queries web search and fetch, unified memory search, embeddings search, AgentDB pattern search, codebase Grep and Glob, ADR indexes, and git intelligence. The source set is matched to the seed type, and you can restrict it with the --sources flag.

When should I use dossier collection instead of deep research?

Use dossier collection when you want to expand outward from a seed entity and discover every connected entity with provenance. Use a deep-research skill when you have a specific question to answer rather than an entity to map.

Can I limit the cost or depth of an investigation?

Yes, use --max-depth and --max-breadth to bound recursion, and --budget-usd to cap approximate spend. When the budget is exhausted, the skill emits a partial dossier marked truncated with the entities still queued.

How does entity deduplication work during expansion?

Entities already present in the dossier are dropped, and unless --exact is set, entities with embedding cosine similarity of 0.92 or higher to an existing node are also merged. This prevents near-duplicate nodes from inflating the graph.