oss-forensics-orchestration

Orchestrate multi-agent OSS forensics investigations on public GitHub repositories.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/roberttmadsen13-del/TOURney --skill oss-forensics-orchestration-roberttmadsen13-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics-orchestration
Source: https://github.com/roberttmadsen13-del/TOURney/tree/main/SKILLS/raptor-main/.claude/skills/oss-forensics/orchestration
Command: npx skills add https://github.com/roberttmadsen13-del/TOURney --skill oss-forensics-orchestration-roberttmadsen13-del

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multi-agent forensics investigations on public GitHub repositories, coordinating parallel evidence collection, hypothesis formation, verification, and final reporting.

Core Features & Use Cases

  • Orchestrates a centralized control flow that spawns specialized agents to collect evidence from multiple sources, while keeping all work in a dedicated working directory.
  • Supports parallel evidence collection, hypothesis formation, verification, and automatic report generation to deliver a cohesive forensic narrative.
  • Uses phase-driven workflow to manage prerequisites, error handling, and iterative hypothesis refinement.

Quick Start

Initiate an investigation by providing the repository, actors, and date range to begin orchestration.

Frequently Asked Questions about oss-forensics-orchestration

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

FAQPage Schema
How do I automate forensics investigations across multiple GitHub repositories?

Automate forensics investigations by orchestrating multi-agent workflows that coordinate parallel evidence collection, hypothesis formation, verification, and final reporting across multiple public GitHub repositories, actors, and date ranges.

What is multi-agent orchestration for open source forensics?

Multi-agent orchestration for forensics uses a centralized control flow to spawn specialized agents that collect evidence from multiple sources, keeping all work in an isolated directory to deliver a cohesive forensic narrative.

Can I use parallel evidence collection for GitHub actors and specific date ranges?

Yes, parallel evidence collection supports investigations across multiple GitHub repositories, actors, and date ranges, enabling phase-based workflows that manage prerequisites and iterative hypothesis refinement simultaneously.

How do I start a phase-driven forensic investigation on public GitHub repositories?

Start a phase-driven forensic investigation by providing the target repository, actors, and date range to initiate the orchestration, which then manages automatic report generation and error handling.

Does the forensics workflow handle hypothesis verification and automatic report generation?

Yes, the forensics workflow handles automatic report generation by using phase-driven agents to draft hypotheses, verify findings, and refine them iteratively before producing the final output.

What are the limitations of automated GitHub forensics orchestration?

Automated GitHub forensics orchestration is limited to public repositories and requires an isolated working directory with safeguards for prerequisites, parallel execution, and error handling to manage phase-driven workflows properly.